Autonomous post meeting follow up (L5)

After every customer call, an agent sends the recap and next step email, updates the CRM, and books the agreed next meeting, without waiting for the rep. Reps review a queue rather than authoring each message.

WORKFLOW1Restrict to agreed conten… onlyGong2Set the review windowSalesforce3Write back structured dataAgentforce4Audit accuracy weeklyManual
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 5.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L5 Autonomous. Running it above your level is how pilots stall.
Measures of successtime to follow up; recap accuracy rate; next meeting booked ratePROVE IT WORKEDtime to follow uprecap accuracy ratenext meeting booked rate

The steps

  1. 01

    Restrict to agreed content only

    Tool: Gong

    The recap may only contain items said on the call: agreed next steps, owners, dates, and open questions. No new pricing, no new commitments, no invented timelines. Owner: sales leadership. DoD: content rules written and tested against ten real calls.

  2. 02

    Set the review window

    Tool: Salesforce

    Send after a short hold, for example thirty minutes, during which the rep can edit or cancel from one queue. Full pre approval kills the speed benefit, zero hold kills trust. Pitfall: no cancel path on a mis-transcribed commitment. DoD: hold and cancel tested end to end.

  3. 03

    Write back structured data

    Tool: Agentforce

    Next step, date, attendees, and stage relevant fields update from the same evidence as the email. One source, two outputs, no divergence. Owner: RevOps. DoD: CRM fields update with a source link to the call.

  4. 04

    Audit accuracy weekly

    Tool: Manual

    Sample twenty sent recaps weekly against the transcript. Any invented commitment is a stop the line event, not a tuning note. Owner: sales ops. DoD: weekly audit with a documented stop rule.

Tools in this playbook

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.