Skip to main content

Asking Questions About Meetings

Companion's most powerful use case is asking questions across your meeting history — summaries, action items, decisions, customer feedback, competitor mentions, anything that was said. You don't have to remember the date or the title; you just ask.

How to query your meetings​

In a Companion thread, ask the question the way you would ask a colleague. Companion has access to the conversations you have read permission on (see Roles and Permissions) and uses tools like search conversations, get conversation, and list meetings to find what you need.

A few examples:

  • "Summarise my last meeting with [Client Name]."
  • "What action items were assigned to me yesterday?"
  • "Did API rate limits come up in any engineering sync this month?"
  • "List all feature requests customers mentioned in Q4."

Phrase questions naturally — Companion picks the right tool, runs the search, and replies with a summary plus links to the source meetings.

Citations and sources​

When Companion answers a question that draws on meetings, the answer includes citations to the source conversations. Click a citation to open the source meeting (and, in many cases, jump to the relevant turn in the transcript). Always rely on the citation to verify a Companion answer — every claim should trace back to a real meeting.

Narrow the answer to specific entities​

Companion's composer includes a Sources picker that lets you scope a single thread to specific entities — a conversation, a contact, an account, a project, a goal — so Companion answers from those rather than the whole workspace. This is useful when you want to focus a thread on, for example, a single account or a particular meeting.

To attach sources:

  1. Open or start a Companion thread.
  2. Use the source picker on the composer (the entity / sources control).
  3. Select the entities you want this thread to be grounded in.

For more on what "sources" mean and how Companion threads behave, see Companion context and Handbook and Companion overview.

What Companion can and can't see​

  • Can see: any conversation, contact, account, project, or other workspace data the current user has read permission on. Companion enforces permissions at every step.
  • Can also see: anything published in the workspace Handbook (under Settings → General), and Project Knowledge for projects the user can access.
  • Cannot see: conversations or workspace data the user is not allowed to read. Companion's read scope is bounded by the user's role.

If you expect Companion to find a meeting and it doesn't, check whether your role's conversations:read:* scope is broad enough — own is restrictive; you may need team or all. See Roles and Permissions.

Tips​

  • Be specific. Naming a contact, account, or date range narrows the search and produces faster, sharper answers.
  • Add Handbook context. If Companion misinterprets jargon or product names, add the definitions to the workspace Handbook (Settings → General) — see Companion context and Handbook.
  • Use Web Search for outside-data questions. When you need information that isn't in your workspace, enable Web Search on the composer — see Chatting with Companion.