An automatic follow-up email after a sales call should usually mean an automatic draft, not an automatic send. The safe workflow extracts supported commitments, prepares a concise message, verifies recipients and promised materials, then lets the accountable rep edit and approve it.
Direct answer: automate capture, evidence linking, structure, and draft creation. Keep recipient choice, unsupported claims, commercial commitments, sensitive content, attachments, suppression, and send authority behind explicit review.
Define what automatic should mean
Separate stages: eligible call ends, source artifact becomes available, meeting and CRM identities resolve, commitments are extracted, a draft is generated, the rep reviews, the approved message is created in the mailbox, and the rep sends. Each stage needs an observable success, failure, and owner.
Microsoft Graph documents creating a draft message and sending it later as separate operations. The create-message reference specifies the draft payload and permissions. That separation is a useful product boundary: software can reduce assembly work without taking send authority.
This guide owns the evidence-to-draft system. The sales call follow-up guide covers message craft more broadly.
Extract only supported commitments
Create a proposition ledger from the call: topic, decision, buyer question, seller promise, next action, owner, date, attachment, unresolved issue, source span, speaker, and uncertainty. Preserve negation and conditionals.
- “We can send the security document” is not “Security approved.”
- “Let’s try next week” does not establish a calendar date.
- “I will ask finance” does not make finance the buyer.
- A rep’s internal note is not a buyer statement.
If the source is incomplete or an owner is absent, ask the rep instead of manufacturing a clean commitment. A no-draft state is valid.
Build the follow-up draft contract
A useful draft contains a truthful subject, short thanks, the buyer’s stated priority in non-sensitive language, agreed decisions, a compact owner-and-date list, promised links or attachments, unresolved questions, and one next step. It should not insert urgency, authority, budget, approval, legal meaning, or product claims that were not supported.
| Draft field | Required evidence or control |
|---|---|
| Recipients | Eligible meeting participants plus current CRM and suppression checks |
| Claims | Source span or approved product evidence |
| Commitments | Named owner, action, date, and uncertainty |
| Attachments | Approved current file, permission, and correct audience |
| Timing | Freshness deadline and local sending policy |
| Approval | Reviewer identity, edits, final recipients, and accepted version |
Display source evidence and CRM destination beside the draft. Reviewing prose alone will not catch a wrong opportunity or external recipient.
Gate recipients and send authority
Re-resolve recipients at review time. Meetings can include assistants, consultants, personal addresses, distribution lists, internal employees, or people who should receive notes but not commercial material. Apply consent, suppression, region, active-opportunity ownership, and company policy before draft creation and again before send.
Keep the message in the rep’s drafts and record that draft creation succeeded. Do not report “follow-up sent” until the mailbox has a verified sent event. If another sequence or rep already contacted the account, pause and reconcile rather than duplicating outreach.
Handle no-draft and exception states
Do not generate or release a draft when capture was ineligible, identity is ambiguous, no external recipient is allowed, the call has no meaningful follow-up, the evidence is incomplete, a promised asset is unavailable, sensitive content needs specialist review, or the account is suppressed.
Handle CRM and mailbox outages, revoked tokens, a timeout after draft creation, deleted or moved drafts, edited source notes, and recipient changes. Use a stable meeting-and-version key so retries find the existing draft instead of creating multiples.
Measure accepted drafts, not sends
Track eligible calls, draftable calls, drafts created, rep acceptance, material edit rate, unsupported claims, wrong recipients, missing commitments, attachment errors, duplicate drafts, time to approved draft, sends after approval, replies, complaints, and correction work.
Segment by call type and message job. A discovery recap, pricing follow-up, security response, and customer handoff require different evidence and review. Do not publish a blended automation success rate that hides high-consequence errors.
Where Gangly fits
Gangly repository facts describe generating a recommended follow-up email after a call for rep review and editing. It does not auto-send. Evaluate Post-Call Notes against your evidence, recipient, attachment, suppression, draft, and exception contract. This draft does not claim reply-rate or time-saving outcomes.