Account Executive skill · call-notes-to-crm
Call notes to CRM update
What it does
Turns rough call notes or a transcript into a clean CRM update: summary, pain points, stakeholders and roles, next steps with owners and dates, risks and the fields to update. Use it right after a sales call so the CRM stays current without retyping.
- Time saved
- ~10–20 min per call (estimate)
- Difficulty
- Beginner
- Version
- v1 · 2026-10-01
What you give it
- Your call notes or transcript excerpt — e.g. spoke w/ ops lead + IT. pain = re-keying web orders. IT worried about ERP access. want pilot. follow up next tue w/ security doc
- CRM fields you need to fill (optional) (optional) — e.g. Stage, next step, close date, MEDDICC fields
How it works
- Summarise the call in at most three sentences.
- Extract pain points in the customer's words where possible.
- List stakeholders by role with their stance (supportive, neutral, sceptical) only when the notes show it.
- Turn every commitment into an action with owner and due date; if a date is missing write "date to confirm".
- Flag risks (blockers, missing decision-makers, timing).
- Fill the requested CRM fields only from the notes; write "unknown" rather than guess.
Output
Summary (≤ 3 sentences) · Pain points · Stakeholders (role → stance) · Next steps (table: action · owner · due) · Risks · Field updates (field → value, or "unknown").
Quality checklist
- ☑ Nothing added that wasn't in the notes
- ☑ Every next step has an owner
- ☑ Unknowns are marked, not guessed
Human check: Check the update against your memory of the call before saving it to the CRM, and don't paste call content into unapproved tools.
Example (fictional)
- Your call notes or transcript excerpt: spoke w/ ops lead + IT. pain = re-keying web orders. IT worried about ERP access. want pilot. follow up next tue w/ security doc
Summary: Ops lead and IT joined. Main pain is re-keying web orders; IT is concerned about ERP access. They want a pilot.
Next steps
| Action | Owner | Due |
|---|---|---|
| Send security documentation | Me | Next Tuesday (date to confirm) |
Risks: IT access concerns could delay the pilot.
Field updates: Stage → Discovery · Close date → unknown
▶ Try it
Guests get 3 runs a day — sign in for more.Don't paste confidential or personal data.
Take it with you
Paste into any chat assistant and replace the {{placeholders}} with your details.
You are helping me with this task: Call notes to CRM update.
## Instructions
1. Summarise the call in at most three sentences.
2. Extract pain points in the customer's words where possible.
3. List stakeholders by role with their stance (supportive, neutral, sceptical) only when the notes show it.
4. Turn every commitment into an action with owner and due date; if a date is missing write "date to confirm".
5. Flag risks (blockers, missing decision-makers, timing).
6. Fill the requested CRM fields only from the notes; write "unknown" rather than guess.
## Output format
**Summary** (≤ 3 sentences) · **Pain points** · **Stakeholders** (role → stance) · **Next steps** (table: action · owner · due) · **Risks** · **Field updates** (field → value, or "unknown").
## Before you answer, check
- Nothing added that wasn't in the notes
- Every next step has an owner
- Unknowns are marked, not guessed
If something important is missing from my inputs, say what you assumed. Never invent facts, numbers, names or quotes — mark anything you are unsure of as [to verify].
## My inputs
Your call notes or transcript excerpt:
{{notes}}
CRM fields you need to fill (optional) (optional):
{{crm_fields}}