thinkhard.SI

Prompt repository Customer support & success

Turn sales notes into a handoff for customer success

A deal has closed and the person taking over the account needs to know what was promised, why they bought and who is who.

Registry no.
SUP-025
Collection
Customer support & success
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
5
Added

Customer support & successAny chat

The prompt

Score 10 of 10, Excellent

Use it when A deal has closed and the person taking over the account needs to know what was promised, why they bought and who is who.

  • {{receiver}}
  • {{customer}}
  • {{sales_notes}}
  • {{terms}}
  • {{sales_owner}}
Full prompt and why it works
Prompt
Turn the sales notes below into a handoff document for {{receiver}}, who takes over the {{customer}} account now that the deal has closed. They will use it to run the kickoff and the first 90 days, so it has to capture what the customer was promised and why they bought, in a form they can trust.

Sales notes, call summaries, emails and the proposal:
"""
{{sales_notes}}
"""

The signed terms or order summary: {{terms}}

Use these headings:
1. Why they bought: the problem, what made them buy now, and the goals they stated, in their words where the notes quote them.
2. What was promised: every commitment made during the sale (features, timelines, integrations, training, discounts, special terms), each with where it appears in the notes. Mark anything promised that is not in the signed terms "NOT IN CONTRACT: confirm with {{sales_owner}}".
3. People: a table of stakeholders with role, what each cares about, and who signs off on renewal.
4. Success measures: how the customer will judge the first 90 days, as stated in the notes.
5. Risks and sensitivities: objections raised, competitors considered, anything that nearly stopped the deal.
6. Open questions for {{sales_owner}} before kickoff.

Keep it under 600 words. Write it as plain facts the receiver can rely on, citing the source of each promise, for example "(call notes, May 12)".

Do not add goals, promises or contacts that are not in the notes, and do not soften commitments that may be hard to keep, because the receiver needs to know about them now. Leave out personal opinions about individuals unless they affect the account.

If the notes contradict each other, such as two different go-live dates, list both under open questions rather than choosing one. If a section has nothing in the notes, write "Not covered in sales notes" so the gap is visible.

Variables

{{receiver}}
Who takes over, for example "the onboarding specialist" or "our customer success manager".
{{customer}}
The customer's company name.
{{sales_notes}}
Call notes, emails, the proposal and anything the sales rep wrote down.
{{terms}}
The signed contract terms or order summary.
{{sales_owner}}
The salesperson who closed the deal.

Why it works

  • Background facts. Every promise is checked against the signed terms, so commitments made only in conversation surface before kickoff, not at renewal.
  • What good looks like. Each promise cites where it came from, which lets the receiver trust the document or check it quickly.
  • If unsure. Conflicting details become open questions for the salesperson, and empty sections say so rather than being filled in.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/sales-to-success-handoff

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "sales-to-success-handoff"}, or just ask for it by name.