A working library of eight tested prompts for Customer Success work, plus a meta-prompt for building your own.
The companion document to the article The CSM’s Prompt Library: Eight Prompts That Earn Their Place in the Workflow on CSM Redefined.
The article explains the prompts and the patterns behind them. This document is the operational tool — copyable prompts ready to paste, with space underneath each one to save your adapted version.
The five patterns that make any CS prompt work (from the article):
These produce internal-only artifacts. The customer never sees the result.
When to use: You just got off a customer call. You have the transcript. You need a structured internal note in 3 minutes.
You are converting a customer call transcript into a structured internal CSM note.
The note is for internal CRM use only. The customer will never see it.
Read the transcript below. Then produce exactly these five sections in this order:
1. DECISIONS MADE — bullet list of any decisions reached during the call. Each bullet under 15 words. Include who made the decision if it's clear from the transcript.
2. ACTION ITEMS — bullet list of action items, each in the form "[Owner] will [action] by [deadline if mentioned, else 'TBD']."
3. STAKEHOLDER SIGNALS — note any change in attendees, sentiment, or political dynamics. Specifically flag: a new stakeholder mentioned, a stakeholder departing, a frustration that wasn't there before, or an unexpected enthusiasm.
4. RISK FLAGS — anything in the conversation that suggests renewal risk, expansion blocker, or escalation potential. Two sentences max per flag.
5. NOTABLE QUOTES — up to 3 verbatim quotes from the customer that are worth keeping. Use direct quotes only; no paraphrasing.
Constraints:
- Be specific. "Customer was happy" is not useful; "CFO said the integration with NetSuite was the deciding factor" is useful.
- If a section has nothing to report, write "None this call." Do not fabricate.
- Total length under 400 words. Be ruthless.
TRANSCRIPT:
[paste transcript here]Paste your adapted version here.
When to use: QBR in six days. You need a slide-by-slide outline based on the customer’s history.
You are building a QBR outline for an internal prep document. The outline structures the meeting; the CSM will write the actual slide content.
Read the account context below. Produce a QBR outline with exactly 7 slides:
1. OPENING — one suggested theme for the meeting (a tension or question, not a brag).
2. WINS SINCE LAST QBR — 3 specific wins, each linked to something the customer cares about. If a "win" can only be described in product feature terms, leave it out.
3. METRICS THAT MATTER — the 3 metrics this customer specifically asked about last QBR, plus the one new metric you should introduce this quarter.
4. OPEN COMMITMENTS — what we said we'd do last QBR. Honest status: done, in progress, blocked, or dropped. Do not soften "dropped."
5. WHAT'S CHANGED ON THEIR SIDE — anything in the account context that suggests their priorities have shifted.
6. ASK — one thing we want from them in the next 90 days. One, not a list.
7. NEXT STEPS — placeholder; CSM will fill this in based on conversation.
Constraints:
- Each slide gets a one-line "what this slide answers for them" question. Not a topic — a question.
- If their last QBR commitments include items that are "dropped," call them dropped. The QBR is more credible when the bad news is on the page.
- No slide titles like "Strategic Alignment" or "Partnership Vision." Use plain English.
ACCOUNT CONTEXT:
[paste account summary, last QBR notes, current usage data, recent activity]
When to use: 1:1 with your manager in 30 minutes. You need a digest of what changed this week across your portfolio.
You are producing a weekly portfolio-change digest for a CSM's 1:1 with their manager.
The output is internal-only. The manager will scan it in under 2 minutes.
For each account in the activity log below, produce one line in this exact format:
[ARR band] | [Account name] | [What changed this week] | [Status]
Where:
- ARR band: $0-100K, $100-500K, $500K-1M, $1M+
- What changed: one specific change. Not "had a meeting" — but "introduced new sponsor in finance team." Maximum 12 words.
- Status: one of GREEN / YELLOW / RED. GREEN means on track for renewal. YELLOW means watching. RED means actively at risk.
After the per-account lines, add a "MANAGER ATTENTION" section listing the accounts (max 3) the manager should ask about first, with one sentence why.
Constraints:
- Sort by ARR band (highest first), then by status (RED first within band).
- "What changed" must be a change, not a summary of state. If nothing changed, omit the account from the digest.
- Do not use the word "good" in any status description.
ACTIVITY LOG:
[paste CRM activity, recent emails, usage data summaries]
These produce customer-facing drafts. You are the final author. Review and edit every output before it ships.
When to use: 60 days from renewal. You need the initial proposal email, in three different formality levels.
You are drafting a renewal proposal email for a CSM to send to their primary stakeholder at a customer account.
Read the context below. Produce THREE drafts of the email, labeled:
- DRAFT A: Formal-direct (for a CFO or procurement-led decision)
- DRAFT B: Warm-direct (for a longstanding champion relationship)
- DRAFT C: Brief-collaborative (for accounts with strong day-to-day engagement)
Each draft must:
- Be under 120 words
- Open with one specific reference to the customer's situation or recent interaction (not "I hope this finds you well")
- State the renewal terms clearly: dates, scope, price
- Propose a specific next step with a specific timeframe
- Close without marketing language
DO NOT use any of these phrases in any draft:
- "I hope this finds you well"
- "as discussed"
- "exciting opportunity"
- "we value our partnership"
- "looking forward to"
CONTEXT:
[paste account name, current contract terms, proposed renewal terms, stakeholder name and recent interactions, any relevant relationship context]
When to use: Your champion just emailed saying they’re leaving. You need to congratulate, ask for a handoff, and not extract a reference.
You are drafting a response to an email from a CSM's customer champion announcing they are leaving the company.
The response must:
1. Genuinely congratulate them on the new role (assume the new role is mentioned in their email; if not, congratulate the move).
2. Ask for a warm handoff to whoever is taking over the relationship, framed as helpful to them and their company, not extractive of you.
3. Acknowledge the relationship without performing it.
The response must NOT:
- Ask for a reference call (we will not ask the departing champion for a reference, ever).
- Express disappointment, anxiety, or self-interest about the renewal.
- Use the phrase "stay in touch."
- Promise a coffee, lunch, or call "to celebrate."
Format:
- Single email, under 100 words.
- Tone: warm, brief, professional. Not effusive.
CONTEXT:
[paste the champion's departure email, plus 1-2 sentences about how long they've been your sponsor]
When to use: Customer pushed back on a renewal price increase. You need a structural alternative, not a discount.
You are drafting a response to a customer who has pushed back on a renewal price increase.
The response must propose ONE structural alternative — not a discount. Structural alternatives include:
- Term length change (multi-year for the lower rate)
- Scope change (drop a module they're not using)
- Payment cadence change (annual vs quarterly billing)
- Effective date change (delay renewal by 60 days to align with their fiscal year)
The response must NOT:
- Offer a percentage discount or dollar concession
- Use the phrase "let me see what we can do"
- Concede before naming the alternative
Format:
- Email body, 100-150 words.
- Open by acknowledging their specific objection (not "thanks for the feedback").
- State the alternative in one paragraph.
- Close by inviting a 20-minute conversation specifically about the alternative.
CONTEXT:
[paste the customer's pushback email, current pricing, proposed pricing, and any context about why the increase is happening]
These produce inputs to a human decision. The output is a thinking aid, never sent anywhere directly.
When to use: You’ve placed an account at a renewal probability. You want the strongest possible case against your estimate before you commit.
You are stress-testing a CSM's renewal forecast for a specific account.
The CSM has scored this account at [X]% likely to renew. Your job is to argue the opposite case — make the strongest argument you can that the actual probability is significantly lower (or higher, if asked to argue up).
Read the account context below. Then produce:
1. THE COUNTERCASE: 3-4 specific reasons the actual probability could be 15-25 percentage points lower than the CSM's estimate. Each reason must reference something specific in the context, not generic risk factors.
2. THE EVIDENCE THE CSM IS UNDERWEIGHTING: 2 things in the account context that the CSM may have noted but not fully internalized.
3. THE SINGLE STRONGEST POINT: of all the reasons above, which one would you put on the page if you only had one shot to change the CSM's forecast?
Constraints:
- Be specific. "The champion could leave" is a generic risk; "the champion's LinkedIn shows recent activity around a new role" is specific.
- Do not produce a "balanced" view. Your job is the countercase.
- If the case is genuinely strong, say so in the final point: "On reflection, the CSM's estimate looks defensible because..."
ACCOUNT CONTEXT:
[paste account summary, recent interactions, usage data, stakeholder map, current forecast and reasoning]
When to use: A vendor sent you their deck or one-pager. You want to translate vendor language into operator language before the demo.
You are translating a vendor pitch into operator language for a CSM evaluating a tool.
Read the vendor material below. Produce:
1. WHAT IT ACTUALLY DOES: in 50 words or less, describe the tool's actual function. Strip every marketing word ("revolutionize," "AI-powered," "seamless"). Describe what the software literally does.
2. WHAT IT DOES NOT DO: 2-3 things the deck implies but does not commit to. Look for: "supports," "integrates with," "designed for" — these are softer than "does."
3. THE DATA QUESTION: what data does the tool require from us, and what data does it send out to third parties or its own backend?
4. THE FAILURE CATEGORY: based on the pitch, which failure mode is most likely? Choose from:
- Vaporware (the feature described doesn't fully exist yet)
- Pre-trained on generic data (the AI is not trained on your business)
- Black box (you can't see why it produces what it produces)
- Workflow lock-in (the tool only works if you adopt their workflow, not yours)
- Slow time-to-value (the tool requires extensive setup before producing output)
5. THE QUESTION FOR THE DEMO: one specific question the CSM should ask in the demo that will reveal whether the failure mode applies.
Constraints:
- Be ruthless. Vendor decks are aspirational; your job is to find the gap between aspiration and reality.
- If the deck is unusually honest, say so: "this deck makes specific, falsifiable claims; the demo question is straightforward verification."
VENDOR MATERIAL:
[paste deck text, one-pager, or product page content]
When you need a prompt for a CS task that isn’t in this library, use this meta-prompt. It generates new prompts in the same disciplined format.
You are building a working prompt for a CSM, in the format used by The CSM's Prompt Library.
I will describe a CS task. You will produce a prompt that follows this structure:
1. Opens with "You are [doing the task] for a CSM..." — establishes the role.
2. Specifies who the output is for (the CSM, the customer, the manager — be explicit).
3. Defines the format of the output: number of sections, length cap, specific labels.
4. Names 2-4 things the prompt must NOT do (failure modes to avoid).
5. Includes a [CONTEXT] placeholder block at the end for the CSM to paste their context.
The prompt must:
- Be under 350 words.
- Use plain language. No marketing words.
- Be specific about lengths (word counts), formats (bullets vs. paragraphs), and exclusions.
- Acknowledge that the output goes through human review unless it's an Automate-quadrant task.
After writing the prompt, produce a brief "expected output" description and a "failure modes" list — what the model tends to get wrong on this kind of task.
THE TASK I NEED A PROMPT FOR:
[describe the task in plain English — what you're trying to produce, who it's for, what good looks like]Use this meta-prompt every time you need a new prompt. The library compounds — your tenth prompt is better than your first because you’ve internalized what the structure is doing.
As you add prompts to the library, drop them below. Use the same format:
This library is provided free, without an email gate, because the point of CSM Redefined is to be useful, not to build a list. If you find these prompts valuable, share them with a peer who needs them.
New pieces ship every two weeks at csmredefined.com.