Draft follow-ups and update the CRM after sales calls
After each call, the transcript becomes a follow-up email draft and a set of proposed CRM updates: next step, close date, stakeholders and qualification fields. The rep approves both. For sales teams whose CRM is accurate only on the day of the forecast call.
Function: Sales · Industry: Any industry
Draft follow-ups and update the CRM after sales calls
6 steps
At a glance
- Trigger
- A recorded call or meeting ends and the transcript is ready.
- Typical inputs
- Call transcripts
- Opportunity record and stage definitions
- Qualification framework fields
- Email templates and messaging library
- Systems it usually connects to
- Gong
- Salesforce
- HubSpot
- Gmail
- How the work splits
2 rules, 3 model, 1 person steps
How it runs, step by step
6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.
- Rules Fixed logic in code
- Model AI reads or drafts, with a confidence score
- Person A named person decides
- 1
Summarize the call
ModelA model writes a short summary with decisions, objections and agreed next steps, each tied to a point in the transcript.
- 2
Propose the CRM changes
ModelFields such as next step, close date, stakeholders and qualification answers are proposed from what was said.
- 3
Draft the follow-up
ModelA follow-up email is drafted from the summary and the messaging library, with the agreed owners and dates.
- 4
Approve and send
PersonThe rep edits and sends the email, and confirms or changes each proposed CRM update.
- 5
Write the approved changes
RulesConfirmed fields are saved to the opportunity with the call as their source.
- 6
Create the tasks
RulesNext-step tasks and reminders are created for the rep and any internal owner.
Where people approve
The decisions that stay with your team, whatever the confidence score says.
- The rep approves every follow-up before it is sent.
- Changes to stage, amount and close date need a rep to confirm.
- Managers decide the forecast category.
KPIs to track
What to measure, before and after. Targets come from your own baseline.
- 01Share of calls followed up within a day
- 02Open opportunities with a valid next step
- 03Fields changed by the rep after proposal
- 04Time reps spend on admin after calls
Questions about this workflow
Will it write things into the CRM that the customer never said?
It proposes only what is in the transcript and links each proposal to the passage. The rep confirms before anything is saved. We track how often reps reject a proposal as a quality measure.
Do we need call recording?
Transcripts need a recording or notes source. If your team does not record calls, the same flow can work from notes the rep dictates or pastes, and some regions require consent to record that you must handle.
Which steps use rules, a model and a person?
Rules: write the approved changes; create the tasks. Model: summarize the call; propose the CRM changes; draft the follow-up. Person: approve and send. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.
What do we need to start?
Typically: call transcripts; opportunity record and stage definitions; qualification framework fields; email templates and messaging library. You also need read access to Gong, Salesforce, HubSpot and Gmail, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.