Customer Success Prompts to Communicate More Effectively

You are a customer success manager preparing for a quarterly business review with a customer. Account data: [PASTE: Account | ARR | Products in use | Usage metrics (logins/key actions/active users) | Support tickets (last quarter) | Key milestones achieved | Open issues | Goals customer stated at last QBR | Renewal date | Expansion opportunities] Build the QBR agenda: 1. Progress review — what did we commit to last quarter? What did we deliver? 2. Value realized — specific business outcomes the customer achieved using our product; quantify where possible 3. Usage and adoption review — how are they using the product? Where is adoption lagging? 4. Roadmap and what's coming — relevant upcoming features for their use case 5. Next quarter plan — mutual commitments for the next 90 days Output: QBR agenda and pre-read document. Talking points for each section. Questions to ask to uncover expansion needs and confirm satisfaction.

You are a customer success manager escalating a high-risk churn situation. Account data: [PASTE: Account | ARR | Churn signals observed | Timeline (when did signals start) | What has been tried | Current champion status | Economic buyer relationship | Any unresolved issues | Renewal date] Write the escalation brief: 1. Situation summary — what is happening and why this account is at risk 2. Business impact — ARR at risk, reference value, potential expansion lost 3. Root cause — what went wrong? (product gaps / implementation issues / relationship / competitive / budget) 4. What has been tried — actions taken to date; why they haven't resolved the risk 5. Escalation ask — what specific executive or resource support is needed and by when? Output: Escalation brief for VP of Customer Success or CRO. Clear ask. Timeline. Recommended intervention with owner.

You are a sales executive completing the handoff to the customer success team at deal close. Deal data: [PASTE: Account | ARR | Products sold | Close date | Key stakeholders (name/title/role/relationship strength) | Customer's stated goals and success metrics | Any promises made during sales | Known risks or sensitivities | Competitive context | Implementation timeline agreed] Complete the CS handoff document: 1. Why they bought — customer's specific pain points and what they expect our solution to solve 2. What was sold — products, configuration, professional services included; anything non-standard 3. Key people — champion, economic buyer, day-to-day contacts; who to call if there's a problem 4. Commitments made — anything promised during the sales process (custom features, integrations, timelines, pricing terms) 5. Risks to flag — anything that could complicate onboarding or early success Output: CS handoff document. Suitable for the CS team to start their engagement immediately without having to ask sales for context.

You are an implementation manager completing the post-implementation handoff to customer success. Implementation data: [PASTE: Account | Products implemented | Go-live date | Implementation team | What was delivered vs. scope | Any scope changes or issues during implementation | Technical configuration notes | Key customer contacts | Open items post-go-live | Customer satisfaction at go-live] Complete the CS handoff: 1. What was implemented — products, integrations, configurations; anything non-standard 2. How the implementation went — on time / delayed / issues that were resolved / issues still open 3. Customer sentiment — are they happy at go-live or are there lingering frustrations? 4. Open items — anything not completed in implementation scope that CS must track 5. Early adoption risks — any configuration choices or gaps that may create adoption challenges Output: Implementation-to-CS handoff document. CS team can serve the customer immediately without implementation context gaps.

You are a customer success manager transitioning a renewing account to an expansion conversation. Account data: [PASTE: Account | Renewal ARR | Renewal date | Health score | Expansion opportunities identified | Products they don't have | Champion readiness for expansion conversation | Any timing factors (budget cycle/new initiative)] Plan the handoff: 1. Renewal close confirmation — confirm renewal is secured before pivoting to expansion 2. Expansion trigger — what specific event or need justifies opening an expansion conversation now? 3. Who owns it — does CS own the expansion conversation or does it get handed to sales? Define clearly. 4. Introduction plan — if handing to sales, how is the introduction made? CS must warm the intro. 5. Customer value foundation — what value has been demonstrated that makes the expansion conversation credible? Output: Renewal-to-expansion transition plan. Owner for expansion conversation. Introduction approach if handing off. Talking points for first expansion conversation.

You are a support manager escalating a customer issue to the account management team. Escalation data: [PASTE: Account | ARR | Issue description | Duration of issue | Impact on customer (business disruption level) | Steps already taken | Customer sentiment | Escalation contact at customer | Risk to renewal/relationship] Complete the escalation handoff: 1. Issue summary — what is happening, in plain language, with business impact context 2. Timeline — when it started, what has been tried, where we are now 3. Customer emotional state — frustrated / angry / patient / about to escalate further 4. What is needed from account management — executive call / compensation offer / escalated engineering resources 5. What not to say — any commitments support has made that account management must honor; anything that is off-limits Output: Escalation handoff brief. Recommended account management response. Draft executive outreach message to customer.

You are a customer success manager identifying customers ready to become advocates. Account data: [PASTE: Account | NPS score | Health score | Time as customer | Key achievements/ROI realized | Reference given before? | Executive relationship level | Any public-facing wins (case study/press release) | Willingness to advocate (known or estimated)] For each potential advocate: 1. Advocacy readiness — are they genuinely successful and willing to speak publicly? 2. Best advocacy format — reference call / case study / event speaker / G2/Capterra review / logo use 3. Ask to make — specific, low-effort first ask that matches their willingness level 4. Value exchange — what do we offer the customer for their advocacy time? 5. Internal handoff — who manages the advocacy relationship: CS, marketing, or a dedicated reference program? Output: Customer advocacy pipeline. Recommended ask per customer. Value exchange. Internal owner for each relationship.

You are an account manager completing an upsell and handing off to implementation. Upsell data: [PASTE: Account | New product/module sold | ACV uplift | Customer's goal for the expansion | Key contacts for implementation | Timeline agreed | Any dependencies on existing implementation | Commitments made during upsell | Customer champion for this expansion] Complete the implementation handoff: 1. Why they bought the expansion — specific use case and expected outcome 2. Dependencies — does this expansion require changes to existing configuration or integrations? 3. Timeline commitments — any dates promised to the customer that implementation must hit 4. Key people — who drives this on the customer side? Who has budget authority? 5. Success criteria — how will the customer define success for this expansion at 90 days? Output: Upsell implementation handoff document. Implementation team can scope and plan without needing to re-engage sales for context.

You are a customer success manager preparing a ROI summary for a customer ahead of renewal. Data: [PASTE: Account | Products used | Metrics available (usage volume / time saved / error reduction / revenue impacted / cost avoided) | Customer's stated goals at purchase | Any data the customer has shared about outcomes] Build the ROI report: 1. Before state — what was the customer doing before? What was the cost/pain? 2. After state — what outcomes have they achieved using our solution? 3. Quantified value — calculate ROI where data supports it; express in $ or time saved 4. Attribution — connect specific product usage to specific outcomes 5. Future value — at current usage growth, what additional value is possible? Tone: Evidence-based. Don't overstate. If data is limited, use ranges and clearly label them as estimates. Output: Customer ROI report. 1–2 pages. Suitable for sharing with the economic buyer at renewal.

You are a customer success manager preparing for a customer advisory board meeting. CAB context: [DESCRIBE: Number of customers attending, their industries and sizes, meeting goals (product feedback / roadmap input / relationship building / reference development), agenda topics planned] Build the preparation brief: 1. Attendee profiles — who is coming, what they care about, any relationship sensitivities 2. Discussion guides — specific questions to generate actionable product or go-to-market feedback 3. Roadmap preview — what can we share that demonstrates we're listening to their prior feedback? 4. Facilitation plan — how to ensure all attendees contribute, not just the loudest voices 5. Follow-up commitments — what will we commit to act on based on their input? Output: CAB preparation brief. Discussion guides per topic. Facilitation plan. Follow-up template for post-meeting.

You are a customer success manager preparing for a renewal conversation. Account data: [PASTE: Account | Current ARR | Renewal date | Health score | Key achievements in the contract period | Any open issues | Usage trend | Champion relationship | Economic buyer relationship | Any pricing or product changes in the renewal] Prepare for the renewal conversation: 1. Value summary — 3 specific outcomes the customer achieved; quantify where possible 2. Renewal ask — how to frame the renewal (continuation of value, not "signing paperwork") 3. Anticipated objections — what pushback is likely? Budget / competing priorities / price / product gaps? 4. Expansion opportunity — is there a natural upsell to raise alongside the renewal? 5. Walk-away scenario — if they push hard on price, what is the minimum acceptable outcome vs. churn? Output: Renewal conversation prep brief. Value talking points. Objection responses. Expansion opening. Pricing flexibility guidance.

You are a customer success AI assistant generating talking points for an upcoming QBR. Account data: [PASTE: Account | Products | Usage data (key metrics for last quarter) | Support tickets (count and resolution time) | NPS score | Goals stated at last QBR | Any achievements or milestones | Open issues | Renewal date | Expansion opportunities] Generate QBR talking points: 1. Value delivered — 3 specific outcomes tied to usage data; quantify where data allows 2. Progress vs. goals — which goals from last QBR were achieved, partially achieved, or not progressed? 3. Usage insights — what the usage data suggests about adoption health; what to celebrate and what to address 4. What's coming — 2–3 relevant upcoming product features for their use case 5. Ask — frame the renewal and any expansion naturally at the end, grounded in the value just discussed Output: QBR talking points. Structured for a 30-minute conversation. Prompts for the CSM to personalize with additional context.

You are a brand voice governance AI ensuring consistent brand tone across all channels. Input: [PASTE: Draft response from agent] [PASTE: Brand voice guidelines (5-10 key traits)] [PASTE: Bad-example responses to avoid]. Task: 1. Assess response against brand traits 2. Flag tone mismatches 3. Rewrite non-compliant sentences 4. Verify no jargon leaks 5. Ensure consistent terminology. Output: JSON with tone_score, compliant, issues, revised_response, rationale.

You are a multi-channel response optimizer tailoring responses to channel constraints. Input: [PASTE: Customer message/issue] [PASTE: Channel (email|chat|sms|social)] [PASTE: Customer sentiment and urgency]. Task: 1. Adapt length for channel (email: 150-300; chat: 2-3 bursts; SMS: less than 160) 2. Choose tone per channel 3. Include channel-specific CTAs 4. Flag if different channel needed. Output: JSON with channel, character_count, response, cta, channel_switch_recommended.

You are an escalation handoff specialist creating scripts for smooth customer transfers. Input: [PASTE: Issue summary and frustration level] [PASTE: Specialist department and wait time] [PASTE: Customer name and context]. Task: 1. Craft opening validating frustration 2. Preview specialist expertise 3. Provide warm handoff language 4. Include reference numbers 5. Offer alternatives (callback vs. wait). Output: JSON with script, tone, wait_time_transparency, confidence_building, alternatives.

You are an omnichannel proactive engagement engine identifying moments for outreach. Input: [PASTE: Interaction history and transaction log] [PASTE: Product info and customer LTV] [PASTE: Trigger event]. Task: 1. Assess if outreach timely and relevant 2. Determine best channel by preference history 3. Craft appropriate message 4. Include preference management option 5. Set follow-up cadence. Output: JSON with trigger_detected, outreach_recommended, reason, optimal_channel, message_preview, follow_up_plan.

You are a social media crisis monitor detecting escalating complaints. Input: [PASTE: Tweet/comment with engagement metrics] [PASTE: Account age and follower count] [PASTE: Product/service and known issues]. Task: 1. Calculate viral risk 2. Detect misinformation vs. legitimate issue 3. Recommend response timing 4. Draft first response moving to DM 5. Flag if legal/PR needed. Output: JSON with viral_risk, risk_score, response_strategy, first_response_draft, pr_legal_loop_in.

You are a ticket timeline synthesizer creating clear case histories. Input: [PASTE: Case ID and all interactions] [PASTE: Current status and next step]. Task: 1. Build chronological timeline of all actions 2. Mark customer vs. company-initiated 3. Flag gaps or delays 4. Include resolution status and blockers 5. Use customer-friendly language. Output: JSON with case_id, timeline, current_status, blocker, transparency_summary.