Most lists of AI prompts for customer success look great until you run them on a real account. The model fills gaps with confident guesses, invents a usage number, or writes a cheerful email to a customer who is three days into a Sev1. The prompt wasn't the problem. The missing rules around it were.
Below are six prompts I use as starting points, followed by the four rules that make any CSM prompt safe to rely on. Swap the [brackets] for your own field names.
The four rules to put above every prompt
- Name your sources. Tell the agent exactly which tools or exports it may read. If it isn't listed, it doesn't count.
- No invented numbers. Every figure must come from a source. Anything it can't verify gets a [CONFIRM] tag instead of a guess.
- Say what you couldn't check. End every output with a Skipped line. A broken connection should never look like a quiet week.
- Draft only. Nothing goes to a customer or an executive until a person reads it.
1. Churn signal sweep
Review [accounts] for [date range] vs the prior period of equal length.
Flag an account only if it shows 2 or more signals: tickets up 50% or more,
any open Sev1 or Sev2 older than 3 days, weekly active users down 20% or more,
an executive email unanswered for 5 days, renewal inside 90 days with health
not Green. For each flagged account give the signals with source references
and one next step. End with a Skipped line.
The threshold of two signals keeps the list short enough to act on. One noisy week shouldn't put an account on your Monday list. There's a full write-up in the churn risk review routine guide.
2. QBR fact pack
For [account], collect from [CRM, tickets, usage, notes] since [last QBR date]:
goals they set last time and evidence on each, usage trend, top 3 ticket themes,
promises we made and whether we kept them, renewal date and stakeholders.
Mark anything you can't support as [CONFIRM]. Do not write slides yet.
Separate the facts from the story. Once you trust the facts, asking for a narrative is easy. More in QBR prep with AI.
3. Escalation brief
Write a one-page brief on [ticket or account] for [leader]: what happened,
customer impact in their words, timeline with dates, what we've done, what's
blocked and who owns it, the decision we need, and the next update time.
Quote the customer only from source messages.
See how to write an escalation brief for the structure and a worked example.
4. Renewal brief
For renewals landing in [90/60/30] days, list owner, ARR band, health, open
risks, last executive touch, and the one thing that would most improve the
odds of renewing. Use only [CRM fields]. End with a Skipped line.
5. Post-call follow-up
From these call notes, draft a follow-up email: a two-sentence recap, action
items with owners and dates, and one question that moves the account forward.
Keep it under 150 words and in my voice, based on these sample emails: [paste].
6. Friday update to your manager
Summarize my week from [calendar, CRM changes, closed tickets]: wins, risks,
asks. Five bullets max. No adjectives about effort.
Weak prompt vs strong prompt
| Weak | Strong | Why it's better |
|---|---|---|
| Which accounts are at risk? | Flag accounts with 2 or more of these 5 signals for Oct 5 to 11 vs the week before | Fixed window and a clear rule |
| Write a QBR for Acme | List Acme's goals and evidence from these 3 sources. Facts only. | Facts before story |
| Summarize this escalation | One page for the VP: impact, timeline, owner, the decision needed | Names the reader and the ask |
Why prompts alone plateau
A one-off prompt saves you ten minutes. A routine that runs on a schedule, reads the same sources and reports what it skipped saves you hours, because you stop doing the gathering at all. That's the shift from prompting to running AI agents for customer success.
Questions
Can I use ChatGPT for customer success work?
Yes, for drafting and summarizing, as long as your company approves it for customer data. Remove names from exports if you're unsure.
What makes a good CSM prompt?
Named sources, fixed date windows, a rule against invented numbers, and a line listing what it couldn't check.
Should AI send emails to customers?
No. Let it draft and have a person read every message before it goes out.
Want one complete routine with guardrails and a sample result? Get the free play at https://draftfirstcs.com/free
The full guide, with every prompt in one place, is at Draft First.
Top comments (0)