Call notes to next steps

The gap between a good call and a closed deal is usually a follow-up nobody wrote down. Extraction is the whole job here, and the discipline is refusing to produce a commitment the transcript does not contain.

The job on one screen

Runs whenA call recording finishes processing.
ReadsThe transcript, the attendee list, the deal stage.
DecidesWhat was actually agreed, by whom, and by when.
ProducesA list of commitments and proposed CRM field updates, for approval.
Stops whenExtraction complete, or the transcript has no commitments, which it says plainly.
Tools it needsTranscript store, CRM API, calendar.
Autonomy to start atApprove. It does the work and stops before the irreversible step.

Optional: load a real model

Run it

The fields it pulls

Required fields are never guessed. If one is missing the run stops and a person gets the document, which is the difference between an extraction agent and a wrong database row.

FieldRequiredHow it is found
Budget statedoptional(\d+\s*k|\$\s?\d[\d,]*)
Blocker before signatureyes(?:wants|needs|requires) ([^.]+?) before
Deliverable promisedyes(?:asked for|send|provide) ([^.]+)
Due dateoptional(\d{4}-\d{2}-\d{2})
New contactoptional[\w.+-]+@[\w-]+\.[\w.]+

Where this one goes wrong

Politeness as agreement

That sounds great is not a commitment. Require an explicit verb and an owner or do not record it.

Attribution errors

In a four person call, models mix up who said what. Use speaker labels or record commitments as unassigned.

Silent overwrite of deal fields

Never let a transcript overwrite a stage or amount without a human. Transcripts are noisy.

How you would know it is working

MeasureWhy that one
Commitments captured against a human passSample ten calls and compare. Below 80% is not usable yet.
False commitmentsThe dangerous number. One invented promise costs more than ten missed ones.
Follow-up completion rateThe outcome. Recorded commitments should be finished more often than remembered ones.

Earning more rope

AssistPost the extracted list into the rep's notes for editing.
ApproveStage CRM updates and follow-up tasks, rep approves. Correct home for this one.
AutoAuto-create internal tasks only, never customer-facing sends or deal field changes.
The transcript is evidence, not truth. People misspeak, agree to be polite, and change their minds in the last minute of a call. Extract conservatively and let the rep add what they know.

Related: Meeting prep · Pipeline nudge · Memory · all agent jobs · Agent Lab home

Free from AI School - no signup, everything runs in your browser.