30 Claude Prompts for Customer Success Managers

You are a customer success manager who scores account health for a quarterly business review with leadership. <context> I need to turn raw usage and engagement data into a clear health score writeup for one account. </context> <inputs> - Account name: [ACCOUNT NAME] - Product usage trend: [USAGE TREND, e.g. down 15 percent over 60 days] - Support ticket volume and sentiment: [TICKET VOLUME AND SENTIMENT] - Stakeholder engagement: [ENGAGEMENT LEVEL, e.g. champion left the company] - Contract renewal date: [RENEWAL DATE] </inputs> <task> Write a health score summary that assigns a rating of green, yellow, or red, explains the reasoning behind that rating, and lists the top 3 factors driving it. </task> <constraints> Base the rating only on the data given, do not soften a red rating to yellow to be polite. Keep the writeup under 200 words. Avoid vague filler adjectives entirely. </constraints> <format> Start with the rating in bold, then a short paragraph of reasoning, then a bulleted list of the top 3 driving factors. </format>

You are a customer success manager explaining a health score change to your VP of Customer Success. <context> An account's health score dropped from last quarter and my VP wants to know why before the renewal conversation. </context> <inputs> - Account name: [ACCOUNT NAME] - Previous health score: [PREVIOUS SCORE] - Current health score: [CURRENT SCORE] - Changes in the account over the period: [CHANGES, e.g. lost champion, feature adoption dropped] - Any actions already taken: [ACTIONS TAKEN, e.g. scheduled exec check in] </inputs> <task> Write a short explanation of why the score dropped, tying each change directly to the score movement, and state what is already being done about it. </task> <constraints> Do not speculate about causes that were not listed in the changes. Keep it to 3 short paragraphs maximum. Be direct about risk level, do not bury bad news in soft language. </constraints> <format> Three paragraphs: What Changed, Why It Matters, What We Are Doing About It. </format>

You are a customer success operations lead designing a scoring rubric for how CSMs rate account health. <context> Our team scores accounts inconsistently right now and I need a rubric everyone can apply the same way. </context> <inputs> - Signals we currently track: [SIGNALS, e.g. login frequency, feature adoption, support tickets, NPS] - Number of tiers wanted: [NUMBER OF TIERS, e.g. 3 or 5] - Team size using this rubric: [TEAM SIZE] - Biggest current disagreement between CSMs: [DISAGREEMENT DESCRIPTION] </inputs> <task> Build a scoring rubric that defines exactly what values on each signal push an account into each health tier, so two different CSMs would score the same account the same way. </task> <constraints> Every tier boundary must use a specific number or condition, not a vague word like low or high on its own. Keep the rubric to one page for a team of [TEAM SIZE]. Address the specific disagreement mentioned directly. </constraints> <format> A table with rows for each signal and columns for each health tier, showing the exact threshold for that signal in that tier. End with one paragraph resolving the stated disagreement. </format>

You are a customer success manager reaching out to a customer whose product usage has dropped sharply. <context> Usage data shows this account has gone quiet and I want to check in without sounding like a sales pitch. </context> <inputs> - Customer name: [CONTACT NAME] - Account name: [ACCOUNT NAME] - Usage drop specifics: [USAGE DROP DETAILS, e.g. no logins in 21 days] - Feature they used most before the drop: [MOST USED FEATURE] - My relationship history with this contact: [RELATIONSHIP HISTORY, e.g. spoke last at kickoff only] </inputs> <task> Write a short outreach message that names the usage drop honestly, offers a specific reason to re-engage, and asks one clear question. </task> <constraints> Under 120 words. Do not guilt trip the customer about not using the product. Do not mention contract value or renewal, this is a relationship check in, not a sales push. </constraints> <format> A single email with a subject line and body, ready to send. </format>

You are a customer success manager preparing a portfolio summary for your manager's weekly review. <context> I manage a book of accounts and need a roll up of health status across all of them before our 1 on 1. </context> <inputs> - List of accounts with current health rating: [ACCOUNT LIST WITH RATINGS] - Total portfolio ARR: [TOTAL ARR] - Accounts that changed rating this week: [ACCOUNTS THAT CHANGED, with old and new rating] - My top 2 concerns this week: [TOP CONCERNS] </inputs> <task> Summarize the portfolio health at a glance, highlight which accounts changed rating and why that matters given their ARR, and surface my top concerns clearly. </task> <constraints> Lead with the accounts that got worse, not the ones that improved. Keep the summary to half a page. Do not list every account individually if nothing changed, group stable accounts together. </constraints> <format> Sections: Portfolio Snapshot (one line with counts per rating), Rating Changes This Week, Top Concerns, Stable Accounts (grouped, one line). </format>

You are a customer success manager responding to an angry customer who just escalated an issue to your leadership team. <context> A customer emailed my VP directly about an unresolved problem and I need to respond quickly and rebuild trust. </context> <inputs> - Customer name: [CUSTOMER NAME] - Original issue: [ORIGINAL ISSUE DESCRIPTION] - What has already been tried: [ATTEMPTED FIXES] - Root cause if known: [ROOT CAUSE OR UNKNOWN] - Timeline for full resolution: [RESOLUTION TIMELINE] </inputs> <task> Write a response that acknowledges the frustration directly, explains what happened without over-explaining, states what is being done, and gives a specific timeline. </task> <constraints> Do not use the phrase we apologize for any inconvenience. Do not promise a timeline shorter than the one given. Keep it under 150 words. No corporate hedging language. </constraints> <format> A single email, ready to send, with a subject line. </format>

You are a customer success manager escalating a customer issue internally to engineering and product leadership. <context> I need engineering to prioritize a fix and the request will get ignored unless the business impact is clear. </context> <inputs> - Account name and ARR: [ACCOUNT NAME AND ARR] - Issue description: [ISSUE DESCRIPTION] - Business impact on the customer: [BUSINESS IMPACT] - How long the issue has been open: [DURATION OPEN] - Renewal or expansion date at risk: [DATE AT RISK] </inputs> <task> Write an internal escalation brief that gives engineering leadership everything needed to prioritize this without a follow up meeting. </task> <constraints> Lead with business impact, not technical detail. State the deadline that matters and why. Do not exaggerate the impact beyond what is described. Keep it under 200 words. </constraints> <format> Sections: Account and Stakes, Issue Summary, Business Impact, Deadline, Ask. </format>

You are a customer success manager rebuilding trust with an account after a major escalation was resolved. <context> The technical issue is fixed but the relationship took damage and I need a plan to rebuild confidence before renewal. </context> <inputs> - Account name: [ACCOUNT NAME] - What went wrong: [WHAT WENT WRONG] - How it was resolved: [RESOLUTION SUMMARY] - Time until renewal: [TIME UNTIL RENEWAL] - Key stakeholder who was most affected: [KEY STAKEHOLDER NAME AND ROLE] </inputs> <task> Build a recovery plan with specific touchpoints between now and renewal that rebuild trust, including at least one gesture that shows accountability, not just an apology. </task> <constraints> Do not suggest a discount as the primary gesture unless specifically asked for one. Keep the plan to 4 or fewer touchpoints so it feels achievable, not another burden on the customer. Name a specific owner for each touchpoint. </constraints> <format> A table with columns: Touchpoint, Purpose, Owner, Target Date. </format>

You are a customer success manager writing a root cause summary after closing out a customer escalation. <context> Leadership wants a short retrospective on what caused the escalation so we can prevent it happening to other accounts. </context> <inputs> - Account name: [ACCOUNT NAME] - Timeline of events: [TIMELINE OF EVENTS] - Root cause identified: [ROOT CAUSE] - Where the process broke down internally: [INTERNAL BREAKDOWN POINT] - Suggested process fix: [SUGGESTED FIX] </inputs> <task> Write a root cause summary that is honest about where our own process failed, not just what the customer experienced, and ends with a concrete recommendation. </task> <constraints> Do not assign blame to a specific individual by name, focus on the process. Keep it under 250 words. Be specific about the internal breakdown, do not gloss over it. </constraints> <format> Sections: Timeline, Root Cause, Where Our Process Failed, Recommendation. </format>

You are a customer success manager preparing for a call with a stakeholder who has been consistently difficult and dismissive. <context> I have a call coming up with a stakeholder who shuts down conversations quickly and I want to walk in prepared. </context> <inputs> - Stakeholder name and role: [STAKEHOLDER NAME AND ROLE] - History of past interactions: [PAST INTERACTION NOTES] - Topic of the upcoming call: [CALL TOPIC] - What I need from this call: [DESIRED OUTCOME] </inputs> <task> Prepare talking points and likely objections for this call, along with a response to each objection based on the stakeholder's known pattern of behavior. </task> <constraints> Base the predicted objections only on the history given, do not invent a personality that was not described. Keep talking points short enough to glance at during the call, not a script to read word for word. </constraints> <format> Two columns: Likely Objection, My Response. End with one sentence naming the single outcome I must walk away with. </format>

You are a customer success manager assessing renewal risk 90 days out from a contract end date. <context> I need an honest risk read on this account before I brief my manager on the renewal. </context> <inputs> - Account name and ARR: [ACCOUNT NAME AND ARR] - Days until renewal: [DAYS UNTIL RENEWAL] - Usage trend: [USAGE TREND] - Stakeholder relationship status: [STAKEHOLDER STATUS, e.g. champion is engaged, economic buyer unknown] - Competitive threats mentioned by the customer: [COMPETITIVE THREATS OR NONE MENTIONED] </inputs> <task> Assess the renewal risk level, name the top 3 risk factors in order of severity, and recommend the single next action that would most improve the odds of renewal. </task> <constraints> Do not rate the risk as low just because usage looks fine if the stakeholder relationship is weak, both matter. Be specific about which risk factor is most urgent. Under 200 words. </constraints> <format> Start with a risk level (Low, Medium, High), then a numbered list of the top 3 risk factors, then one paragraph on the recommended next action. </format>

You are a customer success manager preparing for the renewal conversation itself with the decision maker. <context> I have the renewal call scheduled and want to lead with value delivered rather than just asking them to sign. </context> <inputs> - Customer name and role: [CUSTOMER NAME AND ROLE] - Contract value and term length: [CONTRACT VALUE AND TERM] - Results achieved since signing: [RESULTS ACHIEVED, with numbers if available] - Any pricing change for this renewal: [PRICING CHANGE OR NONE] - Known objections from past conversations: [KNOWN OBJECTIONS] </inputs> <task> Build talking points for the renewal call that open with concrete results achieved, address the pricing change directly if there is one, and prepare responses to the known objections. </task> <constraints> Lead with results, not price. Do not apologize for a price increase if one exists, state the reasoning plainly instead. Keep talking points to bullet phrases, not full paragraphs. </constraints> <format> Sections: Opening (Results Achieved), Pricing Discussion, Objection Responses, Close (the specific ask). </format>

You are a customer success manager writing a business case document the customer's champion can use internally to justify renewal spend. <context> My champion needs to defend this renewal to their own finance team and asked me for something they can forward. </context> <inputs> - Customer name: [CUSTOMER NAME] - Renewal amount: [RENEWAL AMOUNT] - Quantifiable results since signing: [QUANTIFIABLE RESULTS] - Team or process the product supports: [TEAM OR PROCESS] - Champion's name and title: [CHAMPION NAME AND TITLE] </inputs> <task> Write a one page business case the champion can forward internally, framed as if a stakeholder inside their company is asking why this spend is worth renewing. </task> <constraints> Write it from the champion's perspective, defending the spend, not from our company selling itself. Use only the quantifiable results given, do not invent numbers. Keep it to one page. </constraints> <format> Sections: Summary, Results to Date, Cost of Not Renewing, Recommendation. Address it as an internal memo the champion is sending to their own leadership. </format>

You are a customer success manager pitching a multi year renewal instead of a standard annual renewal. <context> I want to propose a multi year term to this account to lock in revenue and reduce renewal churn risk next year. </context> <inputs> - Account name and current ARR: [ACCOUNT NAME AND ARR] - Proposed term length: [PROPOSED TERM LENGTH] - Discount or incentive being offered: [DISCOUNT OR INCENTIVE] - Customer's stated long term plans: [CUSTOMER LONG TERM PLANS] - Any hesitations they have expressed: [HESITATIONS] </inputs> <task> Outline a proposal that frames the multi year term as aligned with the customer's own stated long term plans, addresses their hesitations directly, and states the incentive clearly. </task> <constraints> Do not oversell the discount as the main reason to sign, tie it to their stated plans instead. Address every hesitation listed, do not skip one. Keep the outline to one page. </constraints> <format> Sections: Why Multi Year Fits Your Plans, Terms and Incentive, Addressing Your Questions, Next Steps. </format>

You are a customer success manager writing up notes right after a renewal closed, win or loss. <context> I just finished the renewal conversation and want to capture what happened while it is fresh, for both CRM records and team learning. </context> <inputs> - Account name: [ACCOUNT NAME] - Outcome: [OUTCOME, e.g. renewed at same price, renewed with discount, churned] - What the customer said drove their decision: [CUSTOMER'S STATED REASONING] - What I would do differently next time: [MY OWN REFLECTION] - Any competitor mentioned: [COMPETITOR NAME OR NONE] </inputs> <task> Write a renewal debrief that captures the outcome, the customer's real reasoning, and one lesson the team should take from this specific renewal. </task> <constraints> Be honest even if the outcome was a loss, do not soften it for the record. Keep it under 150 words. If a competitor was mentioned, name it plainly, do not vague it out. </constraints> <format> Sections: Outcome, Customer's Reasoning, Lesson for the Team. </format>

You are a customer success manager looking for expansion opportunities inside an existing account. <context> This account is healthy and I want to find a genuine expansion angle before I bring it up, not just push more seats. </context> <inputs> - Account name and current plan: [ACCOUNT NAME AND CURRENT PLAN] - Current usage pattern: [USAGE PATTERN] - Teams or departments not yet using the product: [TEAMS NOT USING PRODUCT] - Stated goals for this year: [STATED GOALS] - Available upsell products or tiers: [AVAILABLE UPSELL OPTIONS] </inputs> <task> Identify the single most credible expansion opportunity based on their actual usage and goals, and explain why it fits before naming the product or tier to pitch. </task> <constraints> Do not recommend the most expensive option by default, recommend the one that actually fits the usage pattern and goals described. If no credible opportunity exists yet, say so directly instead of forcing one. </constraints> <format> One paragraph on the opportunity and why it fits, followed by the specific product or tier recommendation in bold. </format>

You are a customer success manager writing an expansion pitch to a happy, engaged customer. <context> I identified a genuine expansion fit and want to raise it in a way that feels helpful, not like a sales push. </context> <inputs> - Customer name: [CUSTOMER NAME] - Current plan: [CURRENT PLAN] - Recommended upgrade or add-on: [RECOMMENDED UPGRADE] - Specific problem this solves for them: [SPECIFIC PROBLEM SOLVED] - Evidence from their own usage supporting this: [USAGE EVIDENCE] </inputs> <task> Write an email that references their own usage evidence, names the specific problem the upgrade solves, and asks for a short call rather than pushing for an immediate yes. </task> <constraints> Under 130 words. Skip hype verbs. Frame it as solving their problem, not as a revenue opportunity for us. </constraints> <format> A single email with subject line and body, ready to send. </format>

You are a customer success manager building the internal case an economic buyer needs to approve an expansion purchase. <context> My champion supports the expansion but needs to convince their own finance or procurement approver, and I want to give them ammunition. </context> <inputs> - Account name: [ACCOUNT NAME] - Expansion cost: [EXPANSION COST] - Current ROI from existing product usage: [CURRENT ROI OR RESULTS] - Expected impact of the expansion: [EXPECTED IMPACT] - Approver's likely priority: [APPROVER PRIORITY, e.g. cost control, headcount efficiency] </inputs> <task> Build a short business case that connects current proven ROI to the expected impact of the expansion, framed around the approver's stated priority. </task> <constraints> Do not inflate the expected impact beyond what is described. Speak directly to the approver's stated priority, not a generic value pitch. Keep it to half a page. </constraints> <format> Sections: Proven Results So Far, Expansion Ask and Cost, Expected Impact, Why This Matters for [APPROVER PRIORITY]. </format>

You are a customer success manager preparing discovery questions to uncover cross sell opportunities on an upcoming call. <context> I have a regular check in call coming up and want to naturally surface whether other teams or use cases could benefit from additional products. </context> <inputs> - Account name: [ACCOUNT NAME] - Products they currently use: [CURRENT PRODUCTS] - Products not yet adopted: [PRODUCTS NOT ADOPTED] - Known company structure or departments: [COMPANY STRUCTURE] - Relationship warmth with this contact: [RELATIONSHIP WARMTH, e.g. strong trust, still building rapport] </inputs> <task> Write 5 discovery questions that naturally surface cross sell opportunities without feeling like an interrogation or a sales script. </task> <constraints> Questions must sound like genuine curiosity about their business, not lead-ins to a pitch. Match the tone to the relationship warmth given, more direct if trust is strong, softer if still building rapport. No question should mention pricing. </constraints> <format> A numbered list of 5 questions, each with a one line note on what cross sell signal a positive answer would reveal. </format>

You are a customer success manager following up right after a customer verbally agreed to an expansion during a call. <context> The customer said yes to an expansion on our call and I need to send a follow up that locks it in before momentum fades. </context> <inputs> - Customer name: [CUSTOMER NAME] - What they agreed to: [WHAT WAS AGREED] - Next step needed to finalize: [NEXT STEP, e.g. sign order form, internal approval] - Timeline they mentioned: [TIMELINE MENTIONED] - Anyone else who needs to be looped in: [ADDITIONAL STAKEHOLDERS OR NONE] </inputs> <task> Write a follow up email that confirms what was agreed in writing, states the exact next step, and references the timeline they gave so it feels like their own commitment, not pressure from us. </task> <constraints> Under 100 words. Do not introduce new asks beyond what was agreed on the call. If additional stakeholders need looping in, name the action for that clearly. </constraints> <format> A single email with subject line and body, ready to send within the hour. </format>

You are a customer success manager building the outline for a quarterly business review with a customer's leadership team. <context> I have a QBR scheduled and need a structure that shows value clearly instead of just listing features used. </context> <inputs> - Account name: [ACCOUNT NAME] - Attendees expected: [EXPECTED ATTENDEES] - Results achieved this quarter: [RESULTS ACHIEVED] - Goals for next quarter: [GOALS FOR NEXT QUARTER] - Any open issues to address: [OPEN ISSUES OR NONE] </inputs> <task> Outline a QBR structure that opens with results achieved, addresses open issues honestly, and closes with agreed goals for next quarter. </task> <constraints> Do not bury open issues at the end, address them in the middle so they do not feel hidden. Keep the outline to one page. Every section should end with a clear takeaway, not just information. </constraints> <format> Sections in order: Results This Quarter, Open Items and How We Are Addressing Them, Goals for Next Quarter, Agreed Next Steps. </format>

You are a customer success manager turning a spreadsheet of usage metrics into a narrative for a quarterly business review slide. <context> I have raw numbers from our analytics dashboard and need them turned into a story the customer's executives will actually understand. </context> <inputs> - Raw metrics: [RAW METRICS LIST] - Comparison period: [COMPARISON PERIOD] - Customer's stated business goal these metrics support: [BUSINESS GOAL] - Audience for this slide: [AUDIENCE ROLE] </inputs> <task> Turn the raw metrics into a short narrative that connects the numbers directly to the customer's stated business goal, written for the audience given. </task> <constraints> Use only the numbers provided, do not estimate or round in a way that changes the meaning. Avoid jargon the stated audience would not use day to day. Keep it to 3 sentences plus one headline number. </constraints> <format> One bolded headline number, followed by a 3 sentence narrative explaining what it means for their business goal. </format>

You are a customer success manager sending a quarterly update directly to an executive sponsor who does not attend regular check ins. <context> The executive sponsor is busy and only reads a short email, so I need to summarize the whole quarter in a way that respects their time. </context> <inputs> - Executive name and title: [EXECUTIVE NAME AND TITLE] - Account name: [ACCOUNT NAME] - Top result this quarter: [TOP RESULT] - One risk or open item worth their attention: [RISK OR OPEN ITEM] - Ask, if any: [ASK OR NONE] </inputs> <task> Write a short executive update email that leads with the top result, flags the one item that genuinely needs their attention, and makes any ask explicit and easy to act on. </task> <constraints> Under 100 words total. Do not include more than one risk item, executives lose the thread if there are several. No filler opening like I hope this finds you well. </constraints> <format> A single email with subject line and body. </format>

You are a customer success manager writing your weekly status report for your manager. <context> I need to summarize my week across multiple accounts quickly without losing the important details my manager needs to know. </context> <inputs> - Accounts worked this week: [ACCOUNTS WORKED] - Wins this week: [WINS] - Blockers or risks needing manager attention: [BLOCKERS OR RISKS] - Priorities for next week: [NEXT WEEK PRIORITIES] </inputs> <task> Write a weekly status report that highlights wins, flags what needs manager attention clearly, and lists next week's priorities in order of importance. </task> <constraints> Keep the whole report under 200 words. List blockers separately from wins, do not blend them together. Order next week's priorities by urgency, most urgent first. </constraints> <format> Sections: Wins, Needs Your Attention, Next Week Priorities (numbered by urgency). </format>

You are a customer success manager writing a full year account review to present at annual planning. <context> I need to summarize a full year of the relationship with this account for both the customer and my own leadership. </context> <inputs> - Account name: [ACCOUNT NAME] - Key milestones achieved this year: [KEY MILESTONES] - Change in usage or scope over the year: [USAGE OR SCOPE CHANGE] - Challenges faced and how they were resolved: [CHALLENGES AND RESOLUTIONS] - Goals for the coming year: [GOALS FOR NEXT YEAR] </inputs> <task> Write a full year account review that tells the story of the relationship's progress, is honest about challenges faced, and sets up clear goals for next year. </task> <constraints> Do not present the year as flawless if challenges were listed, name them and their resolution plainly. Keep it to one page. End with goals framed as a shared plan, not a unilateral list. </constraints> <format> Sections: Year in Review, Challenges and How We Resolved Them, Looking Ahead. </format>