Verified against ChatGPT · 2026-08-08
Summarize a messy CRM record into a clean handoff brief for a new account owner
Condenses a cluttered, multi-year CRM history into a handoff brief a new account owner can actually use on day one, separating durable relationship facts from stale one-off notes.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Summarize this account's CRM history into a clean handoff brief for a new account owner taking over — someone who needs to be useful on their first call, not read the full multi-year history to piece it together themselves. RAW CRM NOTES AND ACTIVITY LOG 18 months of call notes, including an early note calling the champion 'very enthusiastic' and a note from last month noting they filed a complaint about a support delay. ACCOUNT VALUE AND CONTRACT STATUS $65K ACV, contract renews in 4 months, no upsell activity in the last year. WHY THE HANDOFF IS HAPPENING Previous account owner left the company; account was unassigned for three weeks before this reassignment. Separate durable relationship facts — who the actual decision-makers and champions are, what they care about, any standing sensitivities or past friction — from stale one-off notes that were relevant to a single moment and don't matter anymore, like a scheduling note from eight months ago about a call that already happened. If the CRM notes contain contradictions (one note says the champion is happy, a later note says they raised a complaint), resolve it by trusting the more recent note and flag the contradiction explicitly rather than silently picking one and ignoring the other. If the reason for the handoff itself is relevant context the new owner should know (the previous rep left the company, was reassigned after a complaint, and so on) and it would materially change how the new owner should approach the account, say so plainly rather than omitting it out of excessive discretion. Do not include contact information (emails, phone numbers) since that lives in the CRM record itself and doesn't need restating here — this brief is for context, not as a contact card. OUTPUT FORMAT 1. Who's who: key contacts, their role in the decision, and one line on what each cares about. 2. Account status: value, contract terms, and where things currently stand. 3. Relationship context: what's gone well, any friction points, and the handoff reason if it's relevant. 4. Any contradiction found in the notes, stated explicitly with which version you trusted and why. 5. The single most important thing for the new owner to know before their first call.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The explicit separation of durable relationship facts from stale one-off notes targets the core reason CRM handoffs fail: a multi-year activity log mixes permanently useful context (who the real decision-maker is) with time-bound noise (a scheduling note about a call that already happened), and a model asked to just 'summarize this CRM record' without that distinction will compress everything with roughly equal weight, producing a brief that's shorter than the original log but no more useful, because the new owner still can't tell what's still true from what expired months ago. The instruction to resolve contradictions by trusting the more recent note, while flagging the contradiction rather than silently picking a side, matters because CRM histories genuinely do contain outdated information alongside current information with no built-in way to tell which is which — a model that silently picks whichever note it processes as more prominent (often earlier, more detailed notes) risks handing the new owner a stale, contradicted fact stated with full confidence, which is worse than an acknowledged gap because it produces false confidence going into a first call. Requiring the handoff reason to be surfaced when materially relevant, rather than omitted for discretion, corrects a tendency for models to default toward blandly professional omissions when a topic seems sensitive (a rep leaving under complaint) — but a new account owner walking into a first call with an angry customer without knowing the previous rep departure was related to a complaint is set up to be blindsided, which is a real cost that outweighs the mild awkwardness of stating the context plainly. Excluding raw contact information keeps the brief focused on judgment and context, which is the part that actually requires synthesis, rather than padding it with data that's one click away in the CRM record itself.
What you get back
Who's who: Priya Shah, VP Operations, primary decision-maker, cares most about response time on support tickets. Account status: $65K ACV, renews in 4 months, no upsell motion in the past year. Relationship context: early relationship was strong, but a complaint was filed last month about a support delay — this is the more recent and more reliable signal, contradicting an earlier note calling the relationship 'very enthusiastic.' Handoff reason: relevant — the account sat unassigned for three weeks after the previous owner left, which likely contributed to the support complaint going unaddressed. Most important thing before the first call: acknowledge the recent support delay directly rather than opening with a generic introduction, since it's the freshest and most negative thing in their recent experience.
Verified against
ChatGPT GPT-5.1 · 2026-08-08
Changelog
- 2026-08-08 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
