Run a discovery call and leave the record correct

The situation

You have a discovery call at two. You will learn six things on it, three of which change how the deal should be run. In every CRM you have used, somewhere between one and all six of those things ended up only in your head, because logging them properly meant a form with eleven fields and you had another call at half past.

This is not a discipline problem. It is a friction problem, and it is the single largest reason CRM data is unreliable everywhere.

What must be true when you are done

• You walked in knowing what was already known.
• What you learned is on the record in sentences, within two minutes of hanging up.
• Everything you committed to is a task with a date.
• The deal's number and date reflect what you now believe, not what you guessed a fortnight ago.
• Somebody else could run the next call from the record alone.

Sixty seconds before

The last line is the one that matters. It is not a list of every email ever exchanged; it is the thing you would have wanted somebody to tell you in the corridor. And notice the open task is visible: walking into a call having not done the thing you promised is worse than not having promised.

Ninety seconds after, in one breath

Do not open a form. Say what happened, the way you would tell a colleague, and let the record follow.

One paragraph, six records. Nothing was a field you had to find, and nothing depended on you coming back to it later, which is the step that never happens.

When something else was listening

The ninety seconds above assumes you are the one who remembers the call. Often you are not the only one who heard it: there is a recorder on the account, a notetaker in the meeting, or the meeting platform itself kept a summary. Gong and Zoom are the two people ask about most.

Your agent can hold both connections at once, and that is the whole point. It reads the call from wherever the call lives, and writes the record here.

Notice what did not have to happen for that to work. Indraft has no integration with your recorder, has never heard of it, and does not need to. The connection is at the agent, which already has both open in the same conversation, so the two do not have to know about each other for you to use them together.

That is worth saying plainly because it is usually the first thing a team asks about and it sounds like a roadmap answer. It is not one. A CRM that builds its own connector to each recording tool is a CRM you wait on. This arrangement is why you do not have to.

Two ways your agent gets there

• The tool speaks the same protocol Indraft does. More of them do every month, and the ones built for revenue teams are the quickest to add it. Connect it the way you connected Indraft and your agent simply has both. Check your own tool's documentation rather than any list, including this one: this is moving fast enough that a page naming who supports it is out of date before it is useful.
• An automation bridges it. If yours has no server, it almost certainly has a webhook for "the recording is ready" and an API holding the transcript. That is the same shape as the form recipe: a trigger, then an HTTP call, built once in the tool you already run.

Read it before you accept it

More important here than anywhere else in this cookbook. A summary drawn from a recording is a machine's reading of a machine's transcription of a conversation, and both steps make confident mistakes: a name misheard, a maybe recorded as a yes, the crucial qualifier in the sentence nobody transcribed cleanly.

So the ninety seconds does not disappear, it changes job. You are no longer remembering the call, you are checking a draft of it, which is faster and catches the thing that matters. And when you correct it, that correction is yours: it outranks what the agent wrote and it stays corrected.

The part that makes it worth doing

Read what the agent wrote before you move on. Not because it is likely to be wrong, but because reading it is what makes it yours.

When you correct something, that correction is a person's assertion and it outranks anything an agent writes later. So a fact you have checked stays checked: a subsequent enrichment or import will hold rather than overwrite it, and the result says which fields it held and why.

This is also why it is worth saying "budget sits with Marek, not procurement" out loud rather than leaving it implied. The next person to open this account has no idea, and the sentence costs you four words.

What not to record

There is no transcript here, no recording, and no attachment, by design. What lands is the reading of what happened.

That division matters more once a recorder is in the picture, because then a transcript definitely exists. It should stay in the tool built to hold it, which has the retention controls, the access rules and the compliance posture that a recording needs. Indraft holds the two sentences that change how the deal is run.

That is a smaller thing to keep and a more useful one. A year of transcripts is not history, it is a search problem, and nobody has ever opened one to prepare for a call. A year of one-paragraph readings is the account's actual story, and you can read a whole relationship in two minutes.

It also means the sensitive parts of a conversation stay where they were said. What goes in is what you would say in standup.

Verify it

• Read the account as a stranger. The test for the whole recipe. Could somebody who has never spoken to Halden run the next call? If the answer is no, the summaries are recording that a call happened rather than what was said.
• Check every commitment became a task. Two things you said you would do, two tasks with dates. Commitments that live only in the note are commitments you will miss.
• Check the deal still says what you believe. If your confidence changed on the call and the record did not, the forecast is now wrong and nobody knows it.
• If a recording wrote it, check one against the call. Once, properly, early on. You are calibrating how much of the draft you can take on trust, and the answer is usually "most of it, except the numbers and the names".

Run it again

Every call, and the ninety seconds after is the habit to protect. The brief before is easy to keep because it obviously helps you. The record after helps somebody else, later, which is precisely why it is the one that gets skipped and precisely why it is the one worth the discipline.