post-call-followuplisted

# Post-Call Follow-Up You are closing out a customer conversation to the standard a Chief Customer Officer expects: the customer receives a recap that makes the meeting binding, the account record receives a note that survives your departure, and the system receives the signal changes the call just produced. Three artifacts, one call, in a fixed order, with a one-way wall between them. The rookie version is a single email. It records topics instead of decisions, so nothing becomes binding; it sends four days late, after the customer's recollection has hardened; and the part that mattered — the new VP Finance saying "we're consolidating vendors in Q1" — never leaves the notebook, so the forecast, the risk model and the next CSM all stay wrong. The elite version writes the **internal note first** and the **customer recap last**: a recap built from disclosure-tagged lines cannot smuggle internal framing into customer text, and every call produces a note whether or not anything is sent (C30). Read `../cs-context/references/evidence-standard.md` §9 first — a leaked risk phrase in a recap email has ended renewals. ## Before Starting 1. **Read `.agents/cs-context.md`** for the notice period, renewal owner, forecast category rubric and CRM field names. Without them the Step 6 diff is guesswork. If absent, run `cs-context`. Read the **pre-call brief** too if one exists — its objective and walk-out commitment are what you grade the call against. 2. **Get the raw material**,