The meeting copilot playbook: briefs, live suggestions and playbooks with Cypher M

Open Copilot in your dashboard and pick a contact, or let Cypher M prefill one from the Contacts drawer or your calendar. The brief it builds is not limited to one call: it draws on everything that caller has done across your AI agents, your website chat, and their bookings, and condenses it into a handful of short sections so you can read it in under a minute before you ever pick up the phone.

What the brief contains

• What they want — a plain-language line describing the goal behind their contact, written from their own words where possible.
• So far — a short history of the relationship, in case this is not the first time they have reached out.
• Open items — questions nobody has answered yet.
• Concerns — objections or hesitations they have already raised, so you do not repeat a pitch they have already rejected.
• Promises made — anything your agent, a past call, or a teammate committed to, so you never contradict your own business.
• Suggested opening — one line you can say or adapt in the first ten seconds of the call.
• Next steps — what was supposed to happen after the last contact, if anything.

Each of these only appears when there is something to show; an empty section is left out rather than padded with filler. If the contact has never spoken to your AI agent, Cypher M says plainly that there is nothing to brief on yet, and that suggestions during the call will still use your playbooks and business details, just not call history.

Reading the brief in under a minute

Read bottom to top the first time: start with Next steps, because that tells you why this call exists, then Promises made, because breaking one is the fastest way to lose trust, then Concerns, then the rest. The Suggested opening is meant to be adapted, not read verbatim — swap in the caller's name and drop any phrase that does not sound like you. Treat it the way you would treat a colleague's handover note before covering their desk for the day: useful context, not a transcript to perform.

Onboarding Cypher M from your calendar

If a meeting is already on your Cypher LM dashboard calendar, open the event and use Onboard Cypher M. It builds the same brief from that contact's calls, and when your Google account is connected with read access to Gmail, it also reads your recent email exchange with them and folds relevant context in. The finished brief is emailed to you as well as shown in the dashboard, so it is in your inbox even if you open the invite from your phone on the way into the meeting.

This matters most for meetings booked days or weeks in advance, where the call history has moved on since the appointment was set. A prospect who booked a demo two weeks ago may have emailed twice since then with new questions; onboarding Cypher M from the calendar catches that instead of leaving you to brief yourself from a two-week-old memory of the original booking call.

Calls with no history yet

Starting a session with someone new — a contact your AI agent has never spoken with — is still worthwhile. There is no brief to read, but suggestions on the call still draw on your playbooks and business details, so a brand-new conversation still gets the benefit of your team's accumulated guidance on how to handle common questions and objections, even with no personal history behind it.

A brief is only as useful as the habit of reading it. Teams that treat Start session as a reflex before every callback see fewer repeated questions and fewer broken promises within the first few weeks, because the person on the call is no longer relying on memory for details that were written down somewhere else. It is a small habit with an outsized return: the five minutes it takes to read a brief is almost always less than the cost of re-asking a customer something they already told your business once.

Cypher M needs to hear the call to suggest anything, and it offers more than one way to do that because meetings happen in more than one shape. When you press Start session, the dialog asks How should Cypher M listen? and remembers whichever option you pick most often if you tick the box for it.

Share this tab

Share your Google Meet tab with the browser's screen-sharing picker and keep tab audio switched on. Cypher M hears both sides: your microphone and the shared tab's audio become two channels, so it can tell your side from the caller's side without guessing. Nobody else in the meeting sees anything join; from their perspective the call looks exactly as it always has. This is the default option and works for any Google Meet call from a desktop browser, and it needs nothing from the other participants at all.

Invite Cypher M to the meeting

Where this option is turned on for your workspace, Cypher M joins the Google Meet itself as a guest, using Meet's own live captions to produce an exact, speaker-labelled transcript — no one has to share a tab, and the hints can show up inside Meet with the companion browser extension. Someone in the meeting has to let it in from the waiting room (the extension can do this automatically). If this option is not yet available on your workspace, the dialog says so and keeps you on Share this tab until it is.

This option is worth the extra setup for meetings with several attendees, where sharing a single tab from one laptop is awkward, or for anyone who would rather not have a screen-sharing prompt interrupt the start of a call.

Microphone only

For an in-person meeting, a phone call on speaker, or any call that is not happening in a browser tab, use your device's microphone. Speech is turned into text by your browser's built-in speech service (Chrome, Edge and Safari on a computer all support this; Firefox does not, and the dialog tells you so up front). If your browser cannot do this, you can still type what the customer says into a box and get suggestions from that — useful as a fallback rather than a first choice, and it means a session is never a dead end even on an unsupported browser.

Before you choose

• Pick Share this tab or Invite Cypher M for anything on Google Meet; pick the microphone for everything else.
• Tick Remember my choice once you know which option your team actually uses, so the dialog defaults to it next time.
• Choose the call's language — English, Urdu, or a mixed mode that listens in English while still catching Roman-Urdu words typed or spoken in Latin letters.

Common setup mistakes

The most common reason a session reports no sound is sharing the wrong thing: a browser window or the whole screen instead of the specific Meet tab, or forgetting to switch on "also share tab audio" in the sharing prompt. If a session says it is not hearing anything, stop sharing and start again, this time double-checking that the Meet tab itself is selected and tab audio is switched on. A denied microphone permission shows its own clear message rather than failing silently — if it happens, allow the microphone for the site from your browser's address bar and start listening again.

Whichever option you pick, the choice only affects how Cypher M hears the call. Your team still decides what to say; nothing is said on your behalf, and the person on the other end of the call never hears Cypher M at all, no matter which listening method is in use.

A playbook is a short, reusable piece of guidance that tells Cypher M what to suggest in a specific, recurring situation. Open Copilot → Playbooks to see what is on, what is off, and to add your own. Each playbook has three parts: a name, When to use it (the situation, described in plain language, like "the caller says it's too expensive"), and What to suggest (your actual instructions — what to say, what to ask, and what never to promise, including real prices or policies if you want Cypher M to use them accurately).

Only playbooks that are switched on are used during a call, so turning one off is a safe way to retire guidance that stopped being relevant without deleting it outright. A handful of starter playbooks are included to get you going; everything else is written by your team as you learn what actually comes up.

Writing guidance that actually helps

The best playbooks are specific about the situation and specific about the response. "Be helpful about pricing" tells Cypher M almost nothing useful; "If the caller says the price is too high, ask what budget they had in mind before offering any discount, and never go below the published rate without manager approval" gives it something concrete to draw from. Include exact numbers, policy wording and anything your team would otherwise have to look up, because a playbook with real figures produces a more useful suggestion than one that gestures vaguely at "our pricing."

A playbook template

Four playbooks worth writing early

Who should write playbooks

In most small teams, whoever has taken the most calls of a given type should write that playbook, because they already know the real objections and the real answers — writing it down is the only step left. In a larger team, a manager reviewing the Suggestions library (below) is often better placed to spot patterns across many calls that any single rep would not see on their own. Either way, a playbook written by someone who has actually handled the situation reads more naturally than one written in the abstract.

Editing a playbook over time

Playbooks are not meant to be written once and left alone. As your pricing changes, your policies update, or you learn a better way to handle a common objection, go back into Copilot → Playbooks and edit the existing entry rather than creating a near-duplicate — a workspace with five playbooks that each cover "pricing objections" slightly differently produces inconsistent suggestions and is harder for a new hire to learn from than one well-maintained playbook per situation.

Keeping playbooks current

Open Copilot → Suggestions library regularly. It groups every suggestion your team has actually used by playbook, shows how often each one was accepted versus shown, and surfaces guidance your team leans on the most. A playbook whose suggestions are rarely used is either badly worded or addressing a situation that does not come up — either way, it is worth revisiting. A playbook whose suggestions are used constantly is a strong candidate for turning into a written answer in your knowledge base too, so your AI agent gives the same answer when a human is not on the call.

What happens when you end the session

Pressing End session stops the microphone and asks Cypher M to write a summary with action items, saved against the contact automatically. If Google Docs or Sheets is connected with the right access, the meeting's full notes are filed as their own Google Doc and the call is logged to your workspace spreadsheet; if Google is not connected yet, the dialog you used to start the session will have reminded you that notes cannot be filed until it is. If the summary cannot be written the moment you end — a temporary hiccup — ending the session again retries it, so you are never left with a session stuck half-finished.

Where action items go next

Action items flow straight into Automations → Follow-ups, where they sit until marked done or sent as a reminder to the customer, labelled by who owns them: items your team promised, and items the customer promised. For the deeper mechanics of what a good set of notes contains, how the two are kept in step, and how follow-ups actually get sent, see Meeting notes and follow-ups with Cypher N — Cypher M and Cypher N share the same transcript and notes pipeline, so nothing has to be copied between them by hand.

Reviewing your own sessions

Copilot → Sessions lists every call, live or ended, with how many suggestions were shown and how many your team actually used. This is worth a periodic look on its own, separate from the Suggestions library: a session with suggestions shown but none used is worth re-reading, since it might mean the playbook guiding that call needs a rewrite, or it might simply mean the call went in a direction nothing had prepared for yet.

A short worked example

Coaching new team members

The Suggestions library doubles as a training tool. A new hire can read what the rest of the team actually said and had accepted on real calls, grouped by situation, which teaches your business's real answers faster than a written manual ever will. Pair this with a short shadowing period: have the new hire sit in on a few calls where an experienced teammate uses suggestions visibly, then switch roles once they are comfortable reading a brief and choosing how to listen.

Why this beats a static training manual

A manual goes stale the moment your pricing or policies change; the Suggestions library updates itself with every call, because it is built from what your own team actually said and what actually got used. A new hire reading it six months from now sees current answers, not whatever was true when the manual was last edited. That alone is reason enough to treat the library as a living reference rather than a one-time onboarding step.

Privacy and consent etiquette

Any time Cypher M is listening to a call — through a shared tab, a joined meeting, or a microphone — someone other than the person on the other end of the line knows the conversation is being transcribed. Treat telling them as a basic courtesy, not a legal footnote to bury in fine print. A short, direct line at the start of the call takes five seconds and avoids an awkward conversation later if someone notices a name has joined the meeting or wonders why you seem to be reading something.

If Cypher M joins a Google Meet as a guest, its name is visible in the participant list, which is itself a form of disclosure — but say something anyway, since not everyone reads a participant list closely during a conversation. If you are only using the microphone on an in-person meeting or phone call, where nothing visibly joins, saying so out loud matters more, not less, because there is no visual cue at all.

Setting expectations as a manager

Make the consent line part of your team's standard opening, the same way you would standardise a greeting or a sign-off, rather than leaving it to each person's judgment call by call. Consistency here protects the business as much as it reassures the caller: a team that always discloses never has to explain, after the fact, why one particular call did not.

Recap and what to do next

Cypher M works in three stages: a brief built from everything a contact has done with your business, live suggestions you choose to use or skip, and a summary with action items once you end the session. None of it replaces your team's judgment — it removes the parts of a call that depend on memory, so judgment is all that is left to apply.

1. Start a session before your next callback and read the brief before you dial.
2. Pick how Cypher M should listen based on where the meeting is happening.
3. Write one playbook this week for the objection or question your team hears most often.
4. Tell people a note-taking assistant is present before the next call you take.
5. Check the Suggestions library at the end of the month and revise whichever playbook is used the least.

Once notes and follow-ups are flowing out of every ended session, the next place to look is scheduling on the call with Cypher S, so a callback that ends in "let's book a time" does not need a second tool to finish the job.