Skip to main content

On a call

  • Session, or call. A single recorded call. The two words mean the same thing.
  • Overlay. The small in-call window the copilot runs in. Only the rep sees it, and nothing joins the meeting.
  • Answer card. A grounded answer the copilot gives, either when you ask or when it catches a prospect question, with a link to the source it came from.
  • Assist. In-call coaching. Press it when you are not sure what to do next, and the copilot reads the moment against your playbook.
  • Detection mode. How answers appear on a call: Auto shows them automatically, Suggest asks you first, and Manual stays quiet until you ask.
  • Stealth mode. Hides the overlay from screen shares, recordings, and screenshots.

Knowledge

  • Knowledge base. Everything the copilot can draw on for answers: your uploaded documents, connected sources, and battle cards.
  • Document. A file you upload, like a pricing sheet, a one-pager, or an FAQ, for the copilot to reference.
  • Connector. A live link to an outside source such as Google Drive, Notion, or Confluence that syncs into the knowledge base and stays current on its own.
  • Battle card. A short, canonical answer you want delivered the same way every time, like a competitor comparison. Cards take priority over your other documents.
  • Knowledge gap. A real question your knowledge base could not answer. The running list of gaps is your to-do list for making the copilot better.

Playbooks

  • Playbook. Your call framework: the stages of a good call and what a rep should cover in each. Tracked live and scored afterward.
  • Stage. A phase of the call, like Discovery or Next Steps.
  • Item. Something to cover in a stage, like confirming the economic buyer.
  • Coverage criteria. Plain-language rules for what counts as covering an item, so the live tracking is accurate.
  • Default playbook. The playbook that runs automatically on every call. Admins set it.
  • Adherence. How closely a call followed its playbook.

Products

  • Product. What your team sells, described once so the copilot understands your calls. Admins create products; the default attaches to every call automatically.
  • Product description. The plain description of what you sell that the copilot uses to keep live answers accurate.
  • Auto-detection triggers. The question types, such as pricing or security, the copilot may answer on its own. Set per product, on or off.

After the call

  • Call analysis. The post-call pass that finds every question the prospect asked and classifies how the rep handled it.
  • Call notes. The auto-written summary, topic sections, and action items from a call.
  • Coaching queue. The incorrect, deferred, and unguarded answers from recent calls, gathered for coaching.

How each question is classified

Team

  • Owner. Runs billing and the plan, manages roles, and can delete the workspace. There is one per workspace.
  • Admin. Manages knowledge, playbooks, connectors, members, and org settings.
  • Member. A rep. Runs the copilot and sees their own calls.
  • Viewer. Read-only access, for someone who needs to see analytics but does not run calls.