Turn a customer call into CRM notes and a recap email
Turns a call transcript or rough notes into structured CRM notes with risk and expansion signals, plus a recap email for the customer.
The prompt
Turn this customer call into CRM notes and a recap email.
Transcript or my notes: [PASTE]
Account and call type: [e.g. "monthly check-in", "escalation call", "QBR", "renewal discussion"]
Attendees: [NAMES/ROLES ON BOTH SIDES]
Produce two outputs:
1. Internal CRM note with these fields:
- Summary (3 sentences max)
- Customer goals or priorities mentioned
- Sentiment (positive / neutral / negative) with the evidence
- Risks: complaints, budget concerns, stakeholder changes, competitor mentions, low usage
- Expansion signals: new teams, new use cases, growth, requests that fit other products
- Product feedback and feature requests (in their words)
- Commitments we made, with owners and dates
- Commitments they made, with owners and dates
- My next step and follow-up date
2. Recap email to the customer:
- Thank them briefly, summarize what we agreed, list action items for both sides with owners and dates in bold, and confirm the next meeting.
- Leave out internal-only items (risk assessments, expansion notes, sentiment).
- Under 200 words.
Only include what was actually said. If an owner or date wasn't agreed, write [OWNER?] or [DATE?] rather than guessing.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- PASTE
- NAMES/ROLES ON BOTH SIDES
- OWNER?
- DATE?
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.
- Notify customers about a product recall or safety issueRecall email, store and website notice, support script, and staff brief that state the hazard and remedy clearly and calmly.
- Consolidate overlapping help docs and FAQs into one knowledge baseAn inventory, conflict list, taxonomy, article template, and merge plan to turn scattered help content into one reliable source.
- Cut call handle time without hurting customer experienceDiagnoses what drives long calls and gives script, training, and tooling fixes that shorten them without lowering quality.