Revenue Operations
Summarize a Sales Call and Next Steps
Convert supplied sales-call notes into a traceable facts, decisions, and actions summary without turning ambiguity into commitments.
Quick facts
- Best for
- Owners · Founder-operators · Sales leaders
- Prompt type
- Efficiency
- Expected result
- A source-traceable facts, decisions, and actions call summary with promises, unknowns, proposed CRM edits, an internal handoff, and a buyer recap draft.
- Time saved
- 30-45 minutes per call summary
- Required inputs
- SOURCE CALL NOTES · PIPELINE STAGE · PRIOR CONTACT HISTORY · VERIFIED OBJECTIONS · PROMISED ACTIONS · DECISION PROCESS · RELEVANT DATES · OFFER · CRM FIELDS · FOLLOW-UP OWNER
- Works with
- ChatGPT + Claude
What this prompt does
- Separates observed facts, explicit decisions, promised actions, open questions, and proposed next steps.
- Creates a review-ready handoff without writing unsupported details into the opportunity record.
When to use
- After a service sales conversation when notes, stage context, and opportunity fields need a consistent human-reviewed summary.
When not to use
- Do not use it when the source notes are missing, or as permission to record, send, schedule, or promise anything without review.
- Do not place unauthorized call notes or unnecessary personal, sensitive, or confidential data in an AI system.
The prompt
#CONTEXT:
Summarize supplied sales-call evidence for a service-business opportunity. Produce a draft handoff for human review, not a live CRM entry or buyer communication.
#INPUTS:
- Source call notes or transcript excerpt authorized for analysis: [SOURCE CALL NOTES]
- Current verified pipeline stage: [PIPELINE STAGE]
- Contact history and call context: [PRIOR CONTACT HISTORY]
- Objections explicitly stated in the supplied notes: [VERIFIED OBJECTIONS]
- Actions explicitly promised by either party: [PROMISED ACTIONS]
- Known decision participants, criteria, and process: [DECISION PROCESS]
- Dates explicitly supplied in the notes or record: [RELEVANT DATES]
- Approved service offer, scope, and claims: [OFFER]
- Current supplied CRM fields, including blanks and conflicts: [CRM FIELDS]
- Named human follow-up owner: [FOLLOW-UP OWNER]
#INSTRUCTIONS:
1. Treat only supplied notes and fields as evidence. Label paraphrases as paraphrases; reproduce a quote only when exact quoted wording was supplied.
2. Do not invent, infer, or fabricate commitments, quotes, dates, objections, decisions, contact facts, or CRM state. Mark unsupported details Unknown and name the missing evidence.
3. Separate facts from explicit decisions, promised actions, proposed actions, and open questions. Interest or discussion is not a decision.
4. For each action, identify the party, exact action, supplied due date or Unknown, source evidence, and approval status. Do not assign a date that was not supplied.
5. Compare the call evidence with the CRM fields. List conflicts and proposed record edits as drafts only.
6. Recommend whether the verified evidence supports the current stage. If stage criteria were not supplied, mark the stage assessment Unknown.
7. Draft a concise internal summary and a separate buyer-facing recap draft. Include only verified offer and decision-process facts.
8. Use only authorized records in an approved AI workspace or approved AI vendor. Minimize the supplied data and redact or omit unnecessary personal, sensitive, or confidential data. Follow company retention and vendor policy.
9. Do not send, contact, schedule, update a live CRM, make a commitment, or present an offer. A named human owner must approve the exact draft and each consequential action before use.
#RESPONSE FORMAT:
## Facts, decisions, and actions call summary
### Verified facts
- Fact — supplied source
### Explicit decisions
- Decision or None recorded — evidence
### Promised actions
| Party | Exact action | Supplied due date or Unknown | Evidence | Approval status |
|---|---|---|---|---|
### Open questions and missing evidence
- Unknown — evidence needed — owner
## Pipeline and CRM review
- Current stage — supported, unsupported, or Unknown — reason
- Proposed field edit — evidence — human approval required
## Internal handoff draft
[Concise evidence-backed summary]
## Buyer recap draft
DRAFT — HUMAN APPROVAL REQUIRED
[Verified recap and proposed next step]Input checklist
- SOURCE CALL NOTES
- PIPELINE STAGE
- PRIOR CONTACT HISTORY
- VERIFIED OBJECTIONS
- PROMISED ACTIONS
- DECISION PROCESS
- RELEVANT DATES
- OFFER
- CRM FIELDS
- FOLLOW-UP OWNER
Example input
Fictional example — SOURCE CALL NOTES: July 30 notes — Taylor said the team wants a process map before discussing implementation and can spare no more than two workshop hours; seller said a two-hour workshop option would be drafted by August 4; Taylor said the operations approver still needs to be identified. PIPELINE STAGE: Discovery. PRIOR CONTACT HISTORY: Video call with Taylor at Alder Legal Operations on July 30; prior contact was one consented email. VERIFIED OBJECTIONS: Concern that the team cannot spare more than two workshop hours. PROMISED ACTIONS: Seller will draft a two-hour workshop option by August 4; buyer will identify the operations approver, with no date stated. DECISION PROCESS: Taylor evaluates; operations approver unknown; no purchase decision recorded. RELEVANT DATES: July 30 call; seller draft due August 4. OFFER: Northstar Workflow Assessment; supplied scope includes process mapping. CRM FIELDS: Stage=Discovery; next_step blank; close_date=2026-08-15 with no supporting note. FOLLOW-UP OWNER: Mina, Solutions Lead.Expected output structure
- A source-traceable facts, decisions, and actions call summary with promises, unknowns, proposed CRM edits, an internal handoff, and a buyer recap draft.
Customize this prompt
- Provide speaker-attributed notes when exact responsibility and wording matter.
- Keep the internal handoff distinct from the shorter buyer recap so internal uncertainty is not hidden.
Guardrails
- Do not invent, infer, or fabricate commitments, quotes, dates, objections, decisions, contact facts, or CRM state; mark unsupported details Unknown with the missing evidence.
- A named human owner must approve every external send, external message, contact, and scheduling action before any action.
- A named human owner must approve every live CRM record or account update before any update.
- A named human owner must approve every commitment, promise, offer, price, policy exception, permission, and legal commitment before any action.
- A named human owner must approve every payment, billing, financial, tax, or pricing decision before any action.
- Use only authorized records in an approved AI workspace or approved AI vendor; minimize data, redact or omit unnecessary personal, sensitive, or confidential data, and follow company retention and vendor policy.
- The assistant must not treat discussion as a decision or alter the source notes.
NEXT STEP