Most sales calls happen in Zoom, Google Meet or Microsoft Teams. Some AI assistants join those meetings as a bot participant. Sales Copilot takes a different route: it runs as a desktop app on your computer and listens through your microphone and system audio. This guide explains what that means in practice and what to check before you rely on it with a buyer.
Bot participants and desktop audio
A meeting bot joins the call as an extra attendee, usually visible in the participant list, and records or transcribes from inside the meeting. A desktop assistant stays on your computer: it hears your microphone and the audio your computer plays, which includes the other people on the call.
Sales Copilot uses the desktop approach. No bot joins the meeting. It is not a native integration with Zoom, Google Meet or Microsoft Teams, so it does not read the meeting's chat, participant list or calendar invite. It works from the audio on your computer and the context you prepare.
| Meeting bot | Desktop audio (Sales Copilot) | |
|---|---|---|
| Shows up in the meeting | Usually, as a participant | No |
| Where it runs | In the meeting service | On your computer |
| What it hears | The meeting it joined | Your microphone and system audio |
| Live help on your screen | Depends on the product | Yes, from your conversation, materials and Playbook |
Set up permissions once
The app needs microphone access and, on macOS, permission to capture system audio. macOS may list this under Screen Recording; Sales Copilot does not read screen content or store screen pixels, screenshots or video. Check that Microphone and System audio both show Ready before you start a live session.
- Grant microphone access to Sales Copilot.
- On macOS, grant the screen and system audio permission when prompted.
- Start a test session and confirm both sides of a call appear in the transcript.
- If your company manages your computer, ask IT whether a policy blocks either permission.
Check your meeting app before a buyer call
Capture depends on your operating system, its permissions and how your meeting app plays audio. Zoom, Google Meet and Microsoft Teams are the apps we design for, but your setup decides what the assistant hears. A five-minute test call with a colleague is the reliable check.
If you share your screen, check what the other participants will see. The app can protect its windows from screen sharing, but the result depends on your operating system and sharing app, so use the sharing preview before the call.
- Use the same headset and meeting app you will use with the buyer.
- Confirm your colleague's voice appears in the live transcript.
- Ask a question your materials cover and check the suggestion that appears.
- Share your screen and look at the preview.
Notice and consent are yours to handle
Live audio is sent to the backend and speech-recognition provider to produce the transcript and suggestions. The product does not store raw audio or recordings. Transcripts, debriefs and derived memory are stored in your workspace with no automatic expiry by default.
You and your organisation are responsible for the notice and consent rules that apply to each call. The product does not collect participant consent for you. Read the Privacy Policy before using it with buyers.