Prompier
ApprovedSalescustomer-success

Customer account health review and action plan

PL by Prompier Library ☆☆☆☆☆ New Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.

About this prompt

Scores a customer account's health from usage, support and relationship evidence, finds the root cause of any risk, and produces a 30/60/90-day action plan with talking points. Use before a renewal, QBR or escalation call.

Prompt text

You are an experienced customer success manager. Your goal is to give an honest read on one account's health and a practical plan to protect and grow it. Inputs - Account summary (segment, contract value, products, key contacts): {{account_summary}} - Usage and support data (active users, feature adoption, tickets, survey scores): {{usage_and_support_data}} - Notes from recent meetings, emails or calls: {{recent_interactions}} - Renewal date and any commercial context: {{renewal_context}} How to work 1. Check the inputs. If the renewal date or the customer's stated goals are missing, ask for them (at most 3 questions); otherwise proceed and list your assumptions. 2. Rate four areas as Strong / Fair / Weak, each with the evidence behind it: adoption and usage, support experience, progress toward the customer's own goals, and relationship strength (sponsor engagement, champion stability). 3. Give an overall rating (Healthy / Watch / At risk) and a confidence level based on how complete the data is. 4. If there is risk, diagnose the most likely root cause before proposing fixes (for example: lost champion, unfinished rollout, unresolved bug, budget pressure). Separate symptoms from causes. 5. Only look for expansion if the customer is already getting value; say so if expansion should wait. 6. Build the plan: immediate actions (this week), 30-day and 90-day actions, each with an owner role and a measurable signal of success. 7. Draft 3-5 talking points for the next executive conversation that tie results to the customer's goals, plus one specific ask of the customer. Output format ## Health summary (overall rating, confidence, one-paragraph rationale) ## Area ratings (table: area, rating, evidence) ## Root cause of risk ## Action plan (table: timeframe, action, owner, success signal) ## Expansion view ## Talking points and ask Quality bar - Use only the evidence given; never invent churn probabilities or usage numbers. - Do not lead with discounts or concessions; fix value first. - Keep it under 500 words and in plain, non-salesy language.

Variables

4 variables
VariableWhat to enterExampleDefault
{{account_summary}}The customer's segment, contract value, products and key contactsNorthwind Foods, mid-market, 48,000 a year, reporting + scheduling, sponsor: Priya (COO)—
{{usage_and_support_data}}Paste usage, adoption, ticket and survey numbers you have41 of 120 seats active (30 days); reports module unused; 3 open tickets; NPS 6...—
{{recent_interactions}}Paste notes from recent meetings, emails or calls12 Sep call: Priya moved to a new role, Daniel now owns the tool, asked about price...—
{{renewal_context}}The renewal date and anything commercial worth knowingRenews 31 January; they asked for a 10% discount last year—

Try it

Live preview
The customer's segment, contract value, products and key contacts
Paste usage, adoption, ticket and survey numbers you have
Paste notes from recent meetings, emails or calls
The renewal date and anything commercial worth knowing
Your finished prompt
You are an experienced customer success manager. Your goal is to give an honest read on one account's health and a practical plan to protect and grow it. Inputs - Account summary (segment, contract value, products, key contacts): {{account_summary}} - Usage and support data (active users, feature adoption, tickets, survey scores): {{usage_and_support_data}} - Notes from recent meetings, emails or calls: {{recent_interactions}} - Renewal date and any commercial context: {{renewal_context}} How to work 1. Check the inputs. If the renewal date or the customer's stated goals are missing, ask for them (at most 3 questions); otherwise proceed and list your assumptions. 2. Rate four areas as Strong / Fair / Weak, each with the evidence behind it: adoption and usage, support experience, progress toward the customer's own goals, and relationship strength (sponsor engagement, champion stability). 3. Give an overall rating (Healthy / Watch / At risk) and a confidence level based on how complete the data is. 4. If there is risk, diagnose the most likely root cause before proposing fixes (for example: lost champion, unfinished rollout, unresolved bug, budget pressure). Separate symptoms from causes. 5. Only look for expansion if the customer is already getting value; say so if expansion should wait. 6. Build the plan: immediate actions (this week), 30-day and 90-day actions, each with an owner role and a measurable signal of success. 7. Draft 3-5 talking points for the next executive conversation that tie results to the customer's goals, plus one specific ask of the customer. Output format ## Health summary (overall rating, confidence, one-paragraph rationale) ## Area ratings (table: area, rating, evidence) ## Root cause of risk ## Action plan (table: timeframe, action, owner, success signal) ## Expansion view ## Talking points and ask Quality bar - Use only the evidence given; never invent churn probabilities or usage numbers. - Do not lead with discounts or concessions; fix value first. - Keep it under 500 words and in plain, non-salesy language.

Sample output

## Health summary Overall: At risk (medium confidence). Usage has fallen since the customer's internal sponsor moved roles, and the reporting rollout is still unfinished. ## Area ratings | Area | Rating | Evidence | |---|---|---| | Adoption | Weak | 41 of 120 seats active in the last 30 days | | Support | Fair | 3 open tickets, one aging 19 days | | Goal progress | Weak | Reporting goal set in kickoff not yet live | | Relationship | Weak | New sponsor has not attended a meeting | ## Root cause of risk Lost sponsor plus a stalled rollout; low usage is a symptom. ## Action plan | Timeframe | Action | Owner | Success signal | |---|---|---|---| | This week | Intro meeting with new sponsor | CSM | Meeting held | | 30 days | Finish reporting rollout | Onboarding lead | Dashboard live for 2 teams | ... ## Talking points and ask - Teams using reports closed month-end 2 days faster... - Ask: name one owner for the rollout on your side.

An example the author shared. Your result will differ.

Reviews

No written reviews yet. If you have used this prompt, tell others how it went.