Extract needs, objections, and commitments from a sales call
Convert a call record into traceable customer evidence without promoting seller interpretations to facts
8 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Extract a faithful sales-call record from the supplied material.
Transcript or notes, speakers, timestamps, corrections, consent, and inaudible sections:
[record]
Stage, participants, account facts, goal, product boundaries, prior commitments, and CRM terms:
[context]
Fields, quote limits, confidence, privacy, owner confirmation, and sharing audience:
[output]
Treat the call record as primary evidence and context as secondary. Separate direct customer statement, direct seller statement, observed example, explicit decision, explicit commitment, seller interpretation, hypothesis, contradiction, and unknown. Never convert interest into intent, a question into an objection, a role into authority, a date mention into a deadline, or polite agreement into a commitment. For every need, constraint, consequence, objection, alternative, success criterion, stakeholder, decision process, risk, and next step, include speaker and timestamp or exact note locator. Record commitments only when owner, action, and timing were explicitly accepted; otherwise mark confirmation needed. Preserve uncertainty and competing statements. Do not invent CRM values. End with a concise follow-up agenda, confirmation questions, privacy audit, and fields safe to enter versus fields to leave blank.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Call record
00:40 Seller: What made the review useful? 01:02 Priya, Operations Director: Our brand projects sometimes sit in client review because the team is not sure who can accept changes. Last month one launch waited two days. 02:10 Marco, Project Lead: That happened once; most reviews move. 05:22 Priya: We use Teams. IT requires SSO. I don't know about hosting. 08:15 Seller: Would an 18% reduction be valuable? 08:21 Priya: Of course, but we'd need to see our own baseline. 12:04 Marco: Can you send the security overview? 12:20 Seller: Yes, I'll send it tomorrow. 16:30 Priya: A mapping session sounds reasonable. 17:10 Seller: Shall we book Tuesday at 2? 17:18 Priya: I need to check with IT; email me options. Recording consent confirmed at start.
Deal context
First discovery call. Product supports Teams; SSO Enterprise only; no on-premise. Seller is Alex. No existing budget or deadline. CRM terms: pain evidence, current process, required capability, next step, decision participant.
Output rules
Internal CRM summary and customer follow-up prep. Short quotes allowed internally with timestamps. Redact no supplied names. Use high/medium/low confidence. Do not name owners or meetings unless explicit.
Example output
Customer evidence
• Workflow issue — high confidence: Priya said brand projects “sometimes sit in client review” because acceptance authority is unclear (01:02). One launch waited two days last month. Marco added that it happened once and most reviews move (02:10); preserve this limiting evidence. Frequency and broader impact remain unknown.
• Current environment — high: Teams is used; IT requires SSO (Priya, 05:22). Hosting requirement is explicitly unknown. Enterprise-tier fit and on-premise exclusion require clarification.
• Success evidence — medium: Priya wants Northstar's own baseline before judging improvement (08:21). The seller's prompted 18% number is not a customer target or expected result.
• Request — high: Marco asked for the security overview (12:04).
Explicit commitment
Alex will send the security overview tomorrow (12:20). Confirm the calendar date and link before customer-facing use.
Not yet a commitment
Priya called a mapping session reasonable (16:30) but did not accept Tuesday; she must check with IT and asked for emailed options (17:18). Record next step as “send scheduling options; customer to check IT availability,” with no meeting date or customer owner confirmed.
Safe CRM fields: pain evidence with both Priya and Marco's statements; Teams; SSO requirement; security request; Alex's send commitment. Leave budget, authority, hosting, deadline, target outcome, and scheduled meeting blank. Follow-up should confirm hosting, relevant IT participant, baseline measure, exact date for the promised security email, and mutually accepted mapping time.
Why this works
1
Evidence types prevent conversational signals from becoming inflated pipeline claims.
2
Commitment tests protect both parties from invented owners and dates.
Check the result
Does every material field point to a speaker and locator?
Are interpretation, hypothesis, and unknown visibly separate from customer statements?
Do recorded commitments include explicitly accepted owner, action, and timing?
ChatGPT