The live call and what you capture

Most reps get this wrong by making it either too small (mumbled, apologetic, half a sentence) or too big (a paragraph that sounds like it was read off a compliance card and makes the buyer wonder what she has walked into). Say this, at normal speed, before anything else:

Thirty-two words. Roughly eight seconds. Three things are doing work in it:

• You said what it does. Records and transcribes. Not "I have an assistant on the call", which is how a buyer ends up surprised later.
• You gave the reason, and the reason is about her. So you can listen. That is true, and it is the whole argument of Part 2.
• You asked a question and then you stopped talking. A consent line that runs straight into your first agenda item is not consent, it is an announcement.

Then wait. The pause is two seconds and it feels like ten. Let it happen.

Some buyers will decline, and a few will decline in a way that sounds like suspicion. This is not a problem to negotiate. It is a one-line answer you should have ready so the silence does not become awkward:

• Turn the bot off in front of her. Do not just say you will. Remove it from the meeting so she can see it leave the participant list.
• Do not argue the policy. "Most of my customers are fine with it" is pressure, and it lands as exactly that. If a regulated buyer says no, the no is often not even hers.
• Write less, not more. Without a recording, the temptation is to transcribe by hand and stop listening. Capture five things: her words for the pain, the numbers she cites, the names she mentions, the objection she raises twice, and the next step.
• The recap still goes out inside the hour. Your hand-written recap will be shorter and often better, because you were forced to decide what mattered while she was still talking.

Reps overestimate how often this happens and underestimate how badly it goes when they have no answer prepared. Have the line. Use it twice a quarter. Move on.

None of these are exotic. All three are common, and all three depend on the fact that a buyer usually will not challenge you in the first minute of a first call:

• Footer consent. A line in the calendar invite saying meetings may be recorded. Nobody read it, and in an all-party consent jurisdiction it is not obviously worth anything. It also fails the human test: if you would not be comfortable pointing at it mid-call, it is not consent.
• Bot-joined-so-it-is-fine. The note-taker appears in the participant list with a name, and the reasoning is that the buyer saw it. She saw a participant. She did not agree to a recording, and she certainly did not agree to it being searchable by your whole revenue org next quarter.
• The late joiner. Jonas from IT drops in at minute twelve because Mira pulled him in. He was not there for your consent line. He starts talking about their security review. Tell him before he speaks, every time, in one sentence: "quick note, I have a note-taker recording."

Requirements genuinely differ by country and by one-party versus all-party rules, and this course does not give legal advice. Take your actual list of jurisdictions to counsel once, write down the answer, and stop improvising it per call. Leader session a5 is the org version of that conversation.

Nobody decides to half-listen. It arrives as relief: the pressure to capture is gone, so the attention drifts to the next question on your list, to the tab behind the call, to what you will say next. The tells are visible on the recording afterwards, which is the one genuinely good use of listening back to yourself:

• You asked something she already answered. The most reliable signal, and the most expensive one - it tells the buyer directly that you were not there.
• You never followed a thread. Every question came off your prep list in order. b4's question bank is a bank, not a script. If Mira says "the DC ramp is three weeks behind", the next question is about that, not about question four.
• You have no idea what she said the number was. If a buyer cites a figure and you cannot repeat it back within thirty seconds, you were transcribing in your head instead of listening.
• You talked more than she did. On a discovery call this is close to fatal and it is trivially measurable on any recording.

The rule that fixes all four: spend the attention out loud. Reflect back. "So the ramp is three weeks behind and the action items from the Monday ops call are the part that keeps slipping. Have I got that right?" You cannot say that sentence while half-listening, which is exactly why it works as a check.

The recap window is not a productivity nicety. Three things decay fast after a call, and all three decay in the first few hours:

• Your memory of the shape. The transcript keeps her words. It does not keep what she paused before saying, what she said flatly, or which of the three problems she came back to twice. That is the part that tells you what the deal actually is, and it is gone by tomorrow.
• Her willingness to correct you. A recap that arrives while the call is still fresh gets read and edited. One that arrives on Thursday gets archived unread, and every wrong assumption in it silently becomes the record.
• The next step's momentum. A next step with a date, agreed in writing on the same day, holds. The same next step raised three days later has to be re-sold.

Four sections. Same four, every time, in this order. Under 200 words total, and it goes in the body of the email, never as an attachment.

Then one closing line, which is the only sentence in the recap doing emotional work: "Correct anything I got wrong - I would rather fix it now than build on it." That line is what turns a summary into a shared record, because it invites the edit that makes it hers too.

• No product paragraph. Not one sentence. The recap is a record of her situation, not a second pitch.
• No adjectives about the call. "Great conversation" is filler and it flags the whole email as generated.
• Every line is a fact she said or a commitment you made. If a line is neither, cut it. That single test is tonight's build-along.

The trust line from b1 lands directly on this page. The read, the promise, the price stay human. A recap contains all three in miniature:

• AI may draft "what I heard". It has the transcript and it is good at extraction. You then check every line against what she actually said, because a confident summary of something she did not say is worse than no summary.
• AI may draft "what we agreed" - and you will cut half of it. Models are generous about agreement. They turn "that could be interesting" into "agreed to explore". That drift is how a deal ends up in your forecast on the strength of politeness.
• You write "what I owe you". This is the promise, and it is the sentence she will hold you to. Never auto-generated, never once, not even the dates.
• You write anything about price. If the call touched commercials, the recap either says the number you actually said or says nothing at all.

The failure mode is not that the model lies. It is that it smooths. Every rounded-off qualifier makes the deal sound one notch further along than it is, and by b9 you are forecasting on a stack of smoothed recaps.

The bot is not the only thing capturing. You are in the room too, and how you behave with the capture is part of what she is evaluating:

• Announce it once, then stop referring to it. Repeatedly mentioning the recording makes people careful, and careful buyers tell you less.
• Do not read from a script. b4's question bank stays out of frame. The moment your eyes are visibly scanning a list, the conversation becomes an interview.
• Say it when you type. "Give me one second, I want to get that number down." That is not an interruption, it is a signal that what she said mattered enough to stop for.
• Never take a note during the hard part. When a buyer says something uncomfortable - budget frozen, a bad experience with a previous vendor - the typing sound is what stops her. Look at her. Write it after.
• If a colleague is on the call, agree the roles first. One person leads, the other captures and asks the follow-ups the leader misses. Two people both half-leading is worse than one person alone.

Mira brings Jonas Weber from IT to the second call, and Priya Raman the CFO joins for the last fifteen minutes. A single-voice recap now actively damages you, because it flattens three different positions into one imaginary consensus. Attribute everything:

• Name the speaker on every heard-line. "Mira: the Jurong ramp is three weeks behind. Jonas: any tool needs to clear the security review, roughly four weeks. Priya: nothing new gets signed before the Q3 close."
• Attribution is not bureaucracy, it is a map. Read those three lines back and the deal shape is obvious: your timeline is set by Jonas, your budget window by Priya, and your champion is Mira, who controls neither.
• Disagreement in the room is the most valuable thing you captured. If Jonas and Mira disagreed about the rollout order, write it down as a disagreement. Do not resolve it in the recap on their behalf. That is not your call to make, and making it is how you lose Jonas.
• Send the recap to everyone who was on the call. Including the person who said nothing. Silence in a meeting is not agreement, and a recap is the cheapest way to find that out early.
• A note-taker's speaker labels are not reliable enough to trust unchecked on a room with a shared microphone or two people with similar voices. If you are attributing a commitment to a named person, verify it.

You told Mira you were recording. You almost certainly did not tell her the two things she would actually care about, because most reps do not know the answers. Find them out this week:

• How long is it kept? Default retention on meeting-intelligence tools is often indefinite. A call from a deal you lost eighteen months ago may still be sitting there, fully transcribed and searchable, along with everything Mira said about her own leadership.
• Who can search it? In most deployments the answer is "everyone in the workspace", which means a rep who has never met Mira can search her name and read a candid forty-five minutes. That is usually fine and occasionally very much not.
• What happens when you leave? The record outlives you, which is the argument for it (b8 is about writing for your successor) and also the reason to be careful about what you type into a call summary.
• Does the buyer get a copy on request? Under PDPA in Singapore and comparable regimes elsewhere, personal data brings access and correction rights. If Mira asks for what you hold on her, "I do not know" is not an answer you want to give.

Write down your org's actual answers, once, and keep them in the same note as your consent line. Then when a buyer asks the follow-up question - and a security-minded one like Jonas will - you answer in a sentence instead of promising to check. Leader session a5 covers setting these policies rather than just knowing them.