# Meeting notetaker

> Capture a discovery conversation, from a remote call or a meeting in the room, and feed the transcript straight into your project's discovery.

_CommerceCopilot documentation · Integrations_

Discovery calls are where requirements get decided and then half-forgotten. The meeting notetaker captures the conversation for you and delivers the transcript directly into the project's discovery model, where the Business Analyst treats it like any other signal: extracting decisions, surfacing open questions, and updating the backlog picture.

It works two ways, both from the input rail on the project's ticket board:

- **A bot that joins a remote call.** Send it into a Zoom, Google Meet, or Teams meeting and it records with the host's permission.
- **An in-person recorder.** For a meeting in the room, capture the conversation through your own device's microphone. No bot, no link, and no admin setup.

There is nothing to connect at the organization level.

## Send a bot to a remote call

### Supported platforms

| Platform | Notes |
| --- | --- |
| Zoom | Standard meeting links |
| Google Meet | `meet.google.com` links |
| Microsoft Teams | Teams meeting links |
| Webex | Standard meeting links |
| GoToMeeting | Standard meeting links |

### Enable the bot on a project

The bot is off by default, and only an organization admin can switch it on:

1. Open the project, go to **Settings**, and pick the **Discovery** section.
2. Turn on the **Meeting notetaker** toggle, after accepting the recording-consent acknowledgement.

### Send the bot to a call

1. Open the project's ticket board and open the **Meeting notetaker** panel in the input rail on the left edge.
2. Paste the meeting link and click **Send notetaker**.

![The meeting notetaker panel with a meeting URL field and a Send notetaker button](/docs/notetaker-form.png)

The bot that joins is clearly labelled as a notetaker: participants can see what it is, and it records only with the host's permission. Make sure everyone on the call knows it is being recorded; in many jurisdictions that is a legal requirement, not a courtesy.

Follow the bot's status from the same panel: joining, waiting to be admitted, recording, done. If the host declines the recording permission prompt, the bot reports that and leaves; nothing is recorded without an explicit yes in the meeting. You can pull the bot out at any time with **Recall bot**: if it had already joined, the recording ends there and the transcript still processes, exactly as if the call had ended on its own.

### During the call

The bot does not sit on the recording until the meeting ends. It streams the conversation as it happens, and about every five minutes the Business Analyst folds the new discussion into discovery and re-synthesizes, so ticket proposals and open questions update on the board while the call is still running, the same way the in-person recorder works.

### Live feedback during meetings

By default the notetaker listens silently. You can also let the Business Analyst speak up in the moment: when the conversation leaves a concrete, delivery-relevant detail ambiguous, it asks one short question about it right away, so the gap gets answered live instead of filed as an open question after the call.

On projects whose output language is English (the default, picked when the project is created), the notetaker transcribes in a low-latency mode: the Business Analyst hears each utterance within a few seconds of it being spoken, so its question lands while the topic is still on the table. Low-latency transcription is English-only, so projects in other languages transcribe in a mode that favors accuracy instead, and live questions can run 3 to 10 minutes behind the conversation. This only affects timing during the call; the transcript and the after-call synthesis work the same in both modes.

Choose how questions are delivered under **Live feedback during meetings** in the project's **Settings**, in the **Discovery** section. Unlike the notetaker toggle, this setting does not need an organization admin.

| Mode | What happens |
| --- | --- |
| Off | No live feedback. The default. |
| Meeting chat | The Business Analyst posts the question into the call's chat. |
| Voice | The Business Analyst speaks the question aloud through the notetaker. If speech generation fails, the question falls back to the meeting chat. |
| Slack thread | Questions go into a live commentary thread in the project's bound Slack channel, one thread per meeting, so the call itself is never interrupted. Available once a [Slack channel is bound](/docs/slack). |

The Business Analyst is deliberately sparing with these. It only asks about the most recent exchange, skips anything already tracked as an open question or covered by the ticket breakdown, and never repeats a question within the same meeting. Most passes stay silent; expect a good question every few minutes at most, not a running commentary. You can switch the mode while a meeting is in progress and it applies from the next pass.

## Record an in-person meeting

For a meeting happening in the room, use the **In-person notetaker** panel in the same input rail. It records through the device's microphone, so there is no bot to dispatch and no link to paste, and it does not need an organization admin to enable anything.

1. Open the **In-person notetaker** panel from the input rail.
2. Tick the box confirming everyone in the room consents to being recorded.
3. Click **Start recording**, and **Stop recording** when the meeting ends.

![The in-person notetaker panel with a recording-consent checkbox and a Start recording button, open beside the ticket board](/docs/notetaker-in-person.png)

While it records, the Business Analyst transcribes the conversation and refines the model about every five minutes, so ticket proposals update on the board while you talk. The raw audio is deleted once it has been transcribed.

## After the call

Most of the meeting is already in the model by the time you hang up. When the call ends, the Business Analyst folds in the final minutes and runs one more synthesis pass, typically within minutes: decisions become decisions, unknowns become open questions, and scope discussed on the call shows up in the next ticket proposals. The discovery dashboard updates on its own when it lands.

## Cost

Both notetakers are metered against your credit balance by the duration recorded; the included 135 monthly credits covers about 33 hours of meetings. The balance in the header updates as transcripts process.

## Troubleshooting

- **The bot never joined.** Check the meeting URL is a direct link on a supported platform, and that the meeting had started. Locked meetings need the host to admit the bot from the lobby.
- **The bot joined but reported a permission problem.** The host declined the platform's recording prompt. Dispatch again once the host is ready to approve it.
- **In-person recording will not start.** The browser needs microphone access. Allow the microphone for the site, then click **Start recording** again.
- **The transcript has not appeared.** Transcription of long calls can lag the meeting end by several minutes. The discovery dashboard updates automatically when it lands.

## Next steps

- [Your first discovery project](/docs/your-first-discovery-project)
- [Slack](/docs/slack) for the conversation between the calls

---
Canonical page: https://www.commercecopilot.ai/fr/docs/meeting-notetaker