25 ChatGPT Prompts for Customer Success Managers (2026)

The customer success managers we hear from in 2026 are not asking whether to use ChatGPT. They are asking what to stop using it for. The team that pastes account notes into a model and ships the output as a QBR slide is the team that loses the account on the first executive who reads it. The team that uses ChatGPT to draft talk tracks for a hard renewal conversation, but writes the actual customer-facing message themselves, is the one keeping their net retention number above 100.

This post is the 25 prompts most CSMs actually want, organised by where they sit in the customer lifecycle. The audience is post-sale CSMs and CS team leads at SaaS companies running between 30 and 500 customers per CSM, where the work is high-context and account-specific. Every prompt has four parts: role, task, constraints, output spec. Copy the prompt, substitute the bracketed brief, paste into ChatGPT. We ran one of them live at the end of the post and reproduced the actual response so you can see what you are working with.

How to use these prompts

Treat ChatGPT as a faster first draft, not a final voice. The prompts work well when you feed in the structured account context (industry, contract value, key stakeholder, current product usage, last call notes) and ask for a specific format you can edit. They fail when you ask for "what should I say to this customer" without context, because the model defaults to generic CS playbook language any customer would recognise.

Two operational rules before you paste. First, never paste anything covered by your customer's NDA or data-handling terms into the free tier of ChatGPT. Account names, usage numbers, internal product strategy, contract terms (anything that would not appear in a public case study) belong in a paid product with explicit data terms or in your CRM, not in a public model. Second, every prompt output is a draft your judgment has to sit on top of. If a customer is in real trouble, the response that matters is the human one, not the polished one.

Onboarding new customers

These five prompts cover the first 30 days of an account, from kickoff scheduling through first-value confirmation. The model is reliable here because onboarding emails are highly templated and the brief constraints are short.

Prompt 1: Kickoff call agenda for a new customer

Prompt: "You are a senior customer success manager at a B2B SaaS company. Draft a 45-minute kickoff call agenda for a new customer. Brief: customer is [customer name and one-sentence description]. Contract value: [ACV]. Primary product use case: [use case]. Stakeholders on the call: [list of names and roles]. Their stated goal for the engagement: [goal]. Constraints: agenda is timed and totals 45 minutes. Each section names the owner (customer or CSM). Includes a 5-minute success-criteria block where the customer states what would make the engagement a win. No filler greetings or icebreakers beyond 30 seconds. No m-dashes. Output: timed agenda as a markdown table with columns Minutes / Topic / Owner / Outcome."

Prompt 2: First-week welcome email after the kickoff

Prompt: "You are a senior customer success manager writing a first-week welcome email to a new customer after their kickoff call. Brief: customer name: [name]. Kickoff call date: [date]. Three success criteria the customer named on the call: [list]. Two next-step actions the CSM owns: [list]. One action the customer owns: [action]. Constraints: under 200 words. Specific to the call (references at least one thing the customer said, by paraphrase). Names the success criteria back to them so they see we heard it. Ends with the customer's owned next step, not a generic 'let me know if you need anything'. No m-dashes. No 'I am thrilled' or 'I am excited' openers. Output: subject line on its own line, then the email body."

Prompt 3: 30-day check-in email

Prompt: "You are a customer success manager writing a 30-day check-in to a new customer. Brief: customer name: [name]. Their original goal for the engagement: [goal]. What they have used in the product so far: [product usage summary]. What they have not yet adopted that the goal requires: [adoption gap]. Constraints: under 180 words. Names the gap specifically without sounding like a sales pitch. Proposes one concrete next step (e.g., a 30-minute working session, a recorded walkthrough). Single ask. No m-dashes. Output: subject line and email body."

Prompt 4: Onboarding plan one-pager for an executive sponsor

Prompt: "You are a CSM creating a one-page onboarding plan for the customer's executive sponsor to review. Brief: customer name: [name]. Stated business outcome: [outcome]. Number of users to onboard: [count]. Target go-live date: [date]. Three biggest risks: [list]. Constraints: one page. Four sections: Business Outcome, Onboarding Phases (3 phases with dates), Risks and Mitigations, Decision Points That Need the Sponsor. No filler. No m-dashes. Output: markdown formatted one-pager."

Prompt 5: First-value confirmation email

Prompt: "You are a CSM writing a customer the email that confirms they hit their first concrete value milestone. Brief: customer name: [name]. Milestone they hit: [specific quantitative milestone, e.g., '50 users active in week 1', 'first report exported to BI']. Date hit: [date]. Original goal this ladders to: [goal]. Constraints: under 150 words. Names the specific number, not a vague reference. Connects the milestone to the original stated goal. Proposes one concrete next step that builds on this win. No m-dashes. No 'congratulations' or 'we are excited for you' filler. Output: subject and body."

QBRs and account health

Quarterly business reviews are the highest-stakes CSM artifact. ChatGPT gets you to a workable first draft fast, but the executive-grade version is something only the CSM can write because it requires reading the room.

Prompt 6: QBR slide outline from a notes dump

Prompt: "You are a senior CSM preparing a QBR for a strategic customer. Brief: customer name: [name]. Contract value: [ACV]. Notes from the last three months of calls: [paste notes]. Customer's stated 2026 goal: [goal]. Three usage metrics with the current quarter values: [metric:value, metric:value, metric:value]. Constraints: produce a QBR slide outline with 7 slides. Each slide has a title, one-sentence purpose, and 3 to 5 bullet points (under 12 words each). Includes a slide where the customer is asked to state success criteria for the next quarter. No m-dashes. Output: numbered slide list."

Prompt 7: Account health summary for an internal weekly review

Prompt: "You are a CSM writing a 100-word account health summary for the internal weekly account review meeting. Brief: customer name: [name]. Health rating you are giving: [Green/Yellow/Red]. Reason for the rating: [one sentence]. The three operational signals driving it: [list, e.g., 'logins down 28% MoM', 'sponsor changed to new VP last week', 'support tickets up 40%']. The action you propose this week: [action]. Constraints: under 100 words. Plain English. Includes the three signals as a bulleted list. Closes with the one-action ask. No m-dashes. Output: prose paragraph then bulleted signals then action line."

Prompt 8: Customer scorecard interpretation for the customer

Prompt: "You are a CSM walking a customer through their scorecard. Brief: customer name: [name]. Six scorecard metrics with current value and benchmark: [list as metric:current:benchmark]. Two metrics performing above benchmark: [list]. Two metrics performing below benchmark: [list]. Constraints: write the talk track as 4 short paragraphs. Open by anchoring on the two above-benchmark metrics. Move to the two below-benchmark metrics with one diagnostic question per metric (not a finger-point). Close with a clear next step that asks the customer to commit to one. No defensive language. No m-dashes. Output: prose talk track only."

Prompt 9: Executive-summary paragraph for a quarterly report

Prompt: "You are a CSM writing the executive summary paragraph at the top of a customer's quarterly report. Brief: customer name: [name]. Quarter: [Q]. Top-line business outcome they were tracking: [outcome metric and number, e.g., 'reduce time-to-close from 14 days to 7']. Actual result this quarter: [result]. One concrete operational change that drove the result (or absence of it): [explanation]. Constraints: 80 to 110 words. Number-led opening sentence. Causal in tone, not promotional. No 'we are proud to share' or 'amazing partnership' filler. No m-dashes. Output: one paragraph."

Prompt 10: QBR Q&A prep brief

Prompt: "You are a CSM prepping for the Q&A section of an in-person QBR with a difficult customer. Brief: customer name: [name]. Two things the customer is likely to raise as concerns: [list]. One thing the CSM team is likely to want to raise: [topic]. Existing customer position on roadmap: [one sentence]. Constraints: produce a Q&A prep brief covering each of those three topics. For each: the question/topic, our position in one sentence, the data point that backs it, and the question we want to ask the customer back. No defensive language. No m-dashes. Output: numbered list with the four sub-fields per item."

Renewals and expansion conversations

These are the prompts that map most directly to revenue. The model produces serviceable first drafts, but the customer-facing message has to be edited for the specific relationship before sending.

Prompt 11: Renewal conversation talk track for an at-risk account

Prompt: "You are a senior customer success manager preparing for a renewal conversation with an at-risk B2B SaaS account. Brief: customer name: [name]. ACV: [amount]. Renewal date: [date]. Current contract length: [term]. Three signals of risk: [list, e.g., 'monthly active users down 35% since Q3', 'champion left the company in February', 'support escalations have increased']. The renewal motion you are running (renew flat, renew with concessions, renew at higher ACV, renew with co-term): [motion]. Constraints: produce a talk-track outline for a 30-minute call. Five sections: opening (under 90 seconds, anchors on customer's original outcome goal), recap of value delivered (1-2 minutes, data-led), the risk picture (3 minutes, honest), discovery of what would make next year successful (10-15 minutes, mostly questions), close (no-pressure, names a single next step). For each section: timing, the opening sentence verbatim, the two key questions to ask, and one trap to avoid. No m-dashes. No defensive or salesy language. Output: structured talk track."

Prompt 12: Expansion pitch into a new business unit

Prompt: "You are a CSM proposing expansion of an existing contract into a second business unit. Brief: customer name and current product use: [name and use]. Current ACV: [amount]. New business unit to target: [unit name and one-sentence on what they do]. Specific pain point in that unit you have heard about: [pain point with source]. Stakeholder in the new unit you have been introduced to: [name and role]. Constraints: write a 200-word email to the original sponsor proposing the introduction and the rationale. Includes one specific business outcome the new unit would care about. Asks for the introduction explicitly. Does not pitch the product. No m-dashes. Output: subject and email body."

Prompt 13: Multi-year renewal proposal email

Prompt: "You are a CSM proposing a multi-year renewal to a healthy customer at their renewal date. Brief: customer name: [name]. Current contract: [ACV and term]. Two-year and three-year options with their pricing: [list both]. Two customer-specific reasons the multi-year makes sense for them (not generic): [list]. Constraints: under 220 words. Names the customer-specific reasons before any pricing. Includes a clear ask for a 30-minute conversation to walk through, not for an email reply. No 'amazing partnership' filler. No m-dashes. Output: subject and email body."

Prompt 14: Renewal negotiation prep brief

Prompt: "You are a CSM prepping for a renewal negotiation where the customer is asking for a 20% reduction. Brief: customer name: [name]. Current ACV: [amount]. Their stated rationale for the ask: [rationale]. Concrete value delivered this year (data): [list]. Three concessions we can offer in priority order: [list]. Our walk-away discount percentage: [percentage]. Constraints: produce a negotiation brief covering: the four data points to lead with, the three customer questions to ask before discussing price, the order in which to offer concessions, the walk-away criterion. No defensive language. No m-dashes. Output: structured brief."

Prompt 15: Re-engagement email after a customer goes quiet

Prompt: "You are a CSM writing a re-engagement email to a customer who has not replied to two prior check-ins. Brief: customer name: [name]. Last interaction: [date and one sentence]. Their original stated goal: [goal]. Two specific product moves they have not made that the goal requires: [list]. Constraints: under 140 words. Single point: 'we noticed two things, here is one question'. No guilt-trip language ('I have not heard from you...'). No 'just checking in' opener. No m-dashes. Output: subject and body."

Churn risk and saves

The model is useful for first-draft outreach, but actual save plays require a level of judgment the model does not have. Use these for speed, then rewrite.

Prompt 16: Save plan one-pager for an at-risk customer

Prompt: "You are a CSM drafting a save plan for the internal save squad. Brief: customer name: [name]. ACV at risk: [amount]. Renewal date: [date]. The three operational signals showing churn risk: [list]. What we have already tried in the last 60 days: [list]. The customer's stated reason for declining engagement (if known): [reason or 'unknown']. Constraints: one page. Five sections: Situation, Root Cause Hypothesis, Plays Already Run, Proposed Plays (3 ranked), Required Internal Approvals. No filler. Names the play owner for each. No m-dashes. Output: markdown one-pager."

Prompt 17: Pre-cancellation conversation talk track

Prompt: "You are a CSM preparing for a 30-minute call with a customer who has signalled they will cancel at renewal. Brief: customer name: [name]. ACV: [amount]. Reason they gave for cancelling: [reason]. Two things we believe are the real reason (not what they said): [list]. Constraints: produce a talk track that prioritises listening over saving. Five sections: opening that acknowledges their decision without trying to flip it (under 60 seconds), three discovery questions designed to surface the real reason, the bridge moment (only if they have surfaced something we can address), the close (must include a graceful path to non-renewal if that is where it lands). For each section: timing, the opening sentence verbatim. No defensive language. No m-dashes. Output: structured talk track."

Prompt 18: Cancellation processing email

Prompt: "You are a CSM writing the cancellation processing email to a customer who has confirmed non-renewal. Brief: customer name: [name]. End-of-service date: [date]. Their stated reason: [reason]. Data offboarding window: [window]. Three operational next steps they need to take: [list]. Constraints: under 180 words. Professional, not sad. Names the offboarding window and steps clearly. Includes the data export instructions or a link to them. Does not attempt one last save. No m-dashes. Output: subject and body."

Prompt 19: Internal churn post-mortem template fill

Prompt: "You are a CSM filling out the internal churn post-mortem document for a recently cancelled customer. Brief: customer name: [name]. Lost ACV: [amount]. Tenure: [years]. Three primary causes of churn ranked by your read: [list]. Was the churn predictable from existing health signals? [yes/no with one-sentence reason]. Two operational changes that might have prevented it: [list]. Constraints: write a one-page post-mortem. Six sections: Account Snapshot, Cause Analysis, Health Signal Audit, What Almost Worked, What Should Have Happened, Operational Recommendation. No blame language. No m-dashes. Output: markdown one-pager."

Prompt 20: Reactivation email to a customer who churned

Prompt: "You are a CSM reaching out 9 months after a customer churned, to invite them back. Brief: customer name: [name]. Their original use case: [use case]. The reason they gave for leaving: [reason]. One specific product change since they left that addresses that reason: [change with one sentence on how it works]. Constraints: under 160 words. Names the specific reason they left without making excuses. Names the specific change. Asks for a 20-minute conversation, not a sale. No 'we have grown a lot since you left' filler. No m-dashes. Output: subject and body."

Internal handoffs, voice of customer, and team enablement

The work CSMs do that customers never see. ChatGPT shines here because the audience is internal and the brief constraints are explicit.

Prompt 21: Sales-to-CS handoff document

Prompt: "You are a CSM receiving a new account from sales and drafting the handoff document the AE will fill in. Brief: account name: [name]. ACV: [amount]. Industry: [industry]. Product they bought: [product]. Constraints: produce a one-page handoff template with these fields, each with a one-sentence prompt to the AE on what to fill in: stated business outcome, evaluation timeline that led to purchase, three competitors evaluated, the champion, the executive sponsor, two stakeholders who pushed back during sales, the politically sensitive aspect of the deal, the promise made during sales that we need to honour, the open red flag. No m-dashes. Output: markdown template."

Prompt 22: Voice-of-customer rollup for the product team

Prompt: "You are a CSM producing the monthly voice-of-customer rollup for the product team. Brief: list of [n] customer requests heard this month, each with: customer, request, business reason behind it: [paste list]. Constraints: produce a markdown table grouped by product area. Columns: Area / Theme / Customer Examples (counts) / Business Reason / Suggested Priority. Sort areas by request volume descending. End with a 3-sentence summary of the top two themes. No m-dashes. Output: markdown table then summary."

Prompt 23: CSM-to-CSM territory transfer note

Prompt: "You are a CSM transferring an account to a colleague because of a territory change. Brief: customer name: [name]. New CSM name: [name]. Account history: [paste a 200-word account history]. Three things the new CSM should know that are not in the CRM: [list]. Constraints: write the transfer note as a Slack DM to the new CSM. Under 250 words. No filler. Names the three off-CRM things explicitly. Includes the one upcoming meeting/deadline. No m-dashes. Output: Slack DM text."

Prompt 24: Team-meeting talking-points doc

Prompt: "You are the team lead drafting the talking-points doc for the weekly CS team meeting. Brief: three customer escalations this week: [list with one sentence each]. Two operational changes the team needs to know about: [list]. One forward-looking ask of the team for next week: [ask]. Constraints: under 350 words. Four sections: Escalations of the Week, Operational Changes, Forward Ask, Open Floor (just the prompt). Pragmatic tone, not motivational. No m-dashes. Output: markdown doc."

Prompt 25: Customer-quote pull for a case-study draft

Prompt: "You are a CSM pulling candidate quotes from customer-call notes for a marketing case-study draft. Brief: customer name: [name]. Three call-note transcripts: [paste]. Two outcomes marketing wants to feature: [list]. Constraints: identify up to 5 quote-worthy sentences from the notes. For each quote: the verbatim sentence, the context it came from (one line), and the outcome it ties to. Do not modify the quote. Flag any quote that touches on a competitor by name or that names a person other than the customer themselves. No m-dashes. Output: numbered list."

What this prompt actually returns (tested 2026-05-12)

We ran Prompt 11 (renewal conversation talk track for an at-risk account) on free ChatGPT with the example brief baked in. The substituted brief was: customer is Northwind Cargo, a regional logistics company; ACV $58,000; renewal date June 30 2026; 1-year auto-renew; three risk signals: monthly active users down 35% since Q3 2025, original champion (Director of Ops) left in February 2026 and the new VP Ops has not engaged on two prior CSM emails, open support tickets up 60% in the last 90 days; renewal motion: renew flat (no upsell, no discount). Reproduced verbatim:

Renewal Call Talk Track

Goal: Renew flat at current ACV of $58,000. Renewal Date: June 30, 2026. Call Length: 30 minutes.

1. Opening

Timing: 1 to 1.5 minutes.

Opening sentence (verbatim): "Thanks for making the time today. When your team first rolled out the platform, the main goal was reducing on-time delivery variance by 20%, so I wanted to use this conversation to look honestly at where things stand today, what has changed operationally over the last year, and what would make the next year successful for your team."

Two key questions to ask:

1. "Before we get into metrics, how are you currently evaluating operational performance across the network?"
2. "Since the leadership transition earlier this year, have priorities changed in any meaningful way for the Ops organization?"

Trap to avoid: Do not start with renewal paperwork, pricing, or contract dates. Lead with operational outcomes and business context.

2. Recap of Value Delivered

Timing: 1 to 2 minutes.

Opening sentence (verbatim): "I want to briefly recap the areas where the platform has delivered measurable value before we talk about what is and is not working today."

Two key questions to ask:

1. "Which workflows or reporting capabilities are still most relied on by the operations team?"
2. "Where do you feel the platform has had the clearest operational impact so far?"

Key value points to cover:

• Initial deployment aligned to reducing delivery variance and improving operational visibility.
• Adoption across Ops teams created standardized tracking and reporting workflows.
• Historical usage trends showed strong engagement through Q3 2025 before recent declines.
• Platform remains embedded in day-to-day operational processes despite lower active usage.

Trap to avoid: Do not overstate ROI or present inflated success claims that the customer may challenge.

3. The Risk Picture

Timing: 3 minutes.

Opening sentence (verbatim): "I also want to acknowledge a few signals that suggest the experience has not been where it needs to be over the last several months."

Two key questions to ask:

1. "From your perspective, what is driving the drop in active usage across teams?"
2. "How much have the recent support issues affected confidence or day-to-day adoption internally?"

Key risk points to address directly:

• Monthly active users are down 35% since Q3 2025.
• Leadership transition after the former Director of Ops left in February 2026.
• Support tickets increased 60% in the last 90 days.
• Limited engagement from new stakeholders created less alignment around priorities and ownership.

Trap to avoid: Do not become defensive about support volume or try to explain away the adoption decline. Acknowledge the signals.

4. Discovery: What Makes Next Year Successful

Timing: 10 to 15 minutes.

Opening sentence (verbatim): "To make sure the next year is genuinely valuable for your team, I would like to spend most of our time understanding what success needs to look like operationally from your side."

Two key questions to ask:

1. "If we were sitting here one year from now having a very successful renewal conversation, what would need to be true operationally?"
2. "What would need to improve in the product experience or support experience for the platform to feel fully dependable to your team again?"

Additional discovery questions:

• "Which teams or users have disengaged the most over the last six months?"
• "Are there operational gaps today that your team is solving outside the platform?"
• "How are you currently measuring delivery variance and service reliability?"
• "What concerns would prevent you from confidently renewing for another year?"
• "What does the new leadership team expect from operational systems this year?"
• "How important is continuity versus reevaluating tooling more broadly?"
• "What support response experience would feel acceptable moving forward?"
• "Who besides yourself should be involved in evaluating next steps?"

Trap to avoid: Do not rush discovery to get to a renewal ask. The customer should speak for most of this section.

5. Close

Timing: 3 to 5 minutes.

Opening sentence (verbatim): "This has been helpful context, and I think the clearest next step is to turn today's discussion into a concrete plan around adoption recovery and support stabilization."

Two key questions to ask:

1. "Would it be helpful if I summarized today's priorities into a short action plan for your review?"
2. "Who should be included in the follow-up conversation so we can align on ownership and next steps?"

Single next step to propose: Commit to sending a concise success plan within 48 hours that includes:

• Support escalation and stabilization actions
• Adoption recovery recommendations
• Agreed operational success metrics for the next 12 months
• Proposed cadence for executive check-ins before renewal

Trap to avoid: Do not force a verbal renewal commitment on the call. Focus on alignment and momentum toward a clear operational plan.

Editor's notes. This is a workable first draft. The structure tracks the brief constraints, the openings are number-anchored to the operational outcome the customer cared about (delivery variance), and the close avoids forcing a verbal renewal commitment on the call. That is the right shape.

Three things need editing before walking into the room. First, the recap of value delivered is too soft on actual data. The brief told you Q3 2025 had strong engagement and there is a 35% drop since, but the recap reads like a generic feature list. A real recap names two or three specific outcome numbers the customer's team can recognise, not "platform remains embedded in day-to-day operational processes". Replace those bullets with whatever the actual usage and outcome data shows for the period before Q3 2025.

Second, the risk section names the support-ticket increase but says nothing about what is causing it. The new VP Ops who has ghosted two CSM emails is the load-bearing risk signal in this account, and the model only references it as "leadership transition" and "limited engagement from new stakeholders". On the live call you need to name that disengagement directly and surface whether the new VP wants this conversation at all. The model softened that on its own and a CSM would be wise not to follow.

Third, the close proposes a 48-hour success plan that mentions "executive check-ins before renewal". The brief told you the new VP has not engaged after two prior emails. Proposing executive check-ins to someone who is not responding to working-level email risks looking like you are escalating around them. Reframe to "a 30-minute working session with you and one of your team" before any executive cadence.

The model also missed one important move the brief implicitly asked for: there is no plan B for what happens if the discovery section surfaces that the customer wants to non-renew. The "no-pressure" close is good, but a strong CSM walks into a flat-renew call with one prepared graceful path to non-renewal in their head. Add that to your prep yourself; the model will not.

FAQ

Is using ChatGPT for customer success work risky from a data perspective?

The free tier of ChatGPT is not the right place for account-identifying customer data. Usage numbers, contract values, support escalation details, named champions, anything covered by your customer's NDA, all belong in your CRM and in tools where the data handling terms are explicit. The prompts in this post are written to work with bracketed placeholders so you can either anonymize or use them in a paid product. The judgment call is the same one your security team would make: if you would not screenshot the prompt and post it in a public Slack channel, do not paste it into the free tier.

Will ChatGPT match my company's customer voice?

Not without help, and not on the first try. The model defaults to generic SaaS CS language any customer would recognise. To get something usable, feed it a 200-word sample of your team's actual writing, ask it to mirror that voice, and edit aggressively. Even then, customer-facing messages should be rewritten by the CSM before sending. The model is a faster first draft, not your team's voice.

What is the riskiest CS task to delegate to ChatGPT?

Saves. A customer who has decided to cancel is in a fragile relationship state, and a generic-sounding message at that moment confirms their reason for leaving. The same is true for any conversation where the customer is in pain (an outage, a data incident, a botched release). The model can give you a structure for a save play, but the actual outreach has to come from a human who knows the relationship.

How do CSMs save real time with ChatGPT?

The biggest time savings are in templated artifacts: kickoff agendas, QBR slide outlines, handoff documents, voice-of-customer rollups, internal post-mortems. These are formats with stable structure where the variables change but the shape does not. The smaller savings are in first-draft outreach, where the model gets you 60% of the way to a sendable email in 30 seconds and you spend the saved time on the parts that need judgment.

Should CS teams pay for ChatGPT Plus or use an enterprise LLM?

For CS teams handling customer data routinely, the answer is one of two: an enterprise plan with data-handling terms your security team has reviewed (ChatGPT Enterprise, Claude for Work, or the equivalent), or your existing CRM's native AI features (Salesforce Einstein, HubSpot Breeze, Gainsight Horizon) where customer data already sits inside the system. The free tier is fine for non-account-specific work (drafting templates, learning prompt patterns, generic skill-building) and bad for anything else.

Where to go from here

The 25 prompts in this post cover the formats CSMs spend the most time on. The savings compound once you save the ones you actually use into a file you reopen weekly. Pick three from this list: one onboarding prompt, one renewal prompt, one internal prompt. Run them on real account work this week. The pattern that worked, you keep. The ones that did not, you adjust or drop. After a month, you will have a personal prompt library that is more useful than any list a blog can give you.

The single most important habit to build: the model produces the draft, you produce the message. If a customer email goes out under your name, you wrote it. The model just made the first 60% faster.

Related: more prompts by profession

• ChatGPT for Customer Support Teams: The Complete 2026 Guide
• How to Write ChatGPT Prompts That Work: The PRSO Framework
• 30 ChatGPT Prompts for Marketing That Don't Sound Like a Press Release