Customer Success Prompts to Manage Your Team and Business

You are a customer success manager preparing for upcoming renewals. Renewal data: [PASTE: Account | ARR | Renewal date | Health score | Last QBR date | Champion strength | Economic buyer relationship | Any open issues | Usage trend (up/flat/down)] For each renewal in the next 90 days: 1. Risk classification: low / medium / high based on health signals 2. Key risk factors — what specifically could cause churn or downgrade? 3. Required actions before renewal conversation — fix issues, re-engage stakeholders, demonstrate value 4. Expansion opportunity — is there a natural expansion conversation to have alongside renewal? 5. Internal escalation — any renewal requiring VP or executive involvement? Output: Renewal pipeline by risk level. At-risk renewals with specific action plan and owner. Total ARR at risk. Expansion opportunities to bring into renewal conversations.

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 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 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 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 reviewing onboarding progress for a new customer. Onboarding data: [PASTE: Account | Go-live date | Days since go-live | Onboarding milestones (list with complete/incomplete status) | Active users vs. contracted users | Key feature adoption (yes/no for each) | Any support tickets or issues | Last CSM contact date] Assess: 1. Milestone completion rate — % of onboarding milestones completed on schedule 2. User adoption — active users as % of contracted licenses; flag if <50% at day 30 3. Feature adoption — are they using the core features that drive value for their use case? 4. Issue log — any open issues that are blocking adoption or creating negative sentiment 5. 30/60/90 day health outlook — based on current trajectory, will this customer be successful? Output: Onboarding health assessment. At-risk indicators. Recommended interventions. Next CS action with specific deadline.

You are a customer success operations manager planning CS team capacity. Data: [PASTE: Current CS headcount | Total ARR managed | ARR per CSM | Account count per CSM | Average time per account per month (hrs) | Churn rate by CSM ratio | Upcoming new customer volume | Any planned team changes] Analyze: 1. Current CSM-to-ARR ratio — how does it compare to benchmark? (typically $2–5M ARR per CSM depending on segment) 2. Account coverage — how many accounts per CSM? Is it manageable for the required touch model? 3. Time capacity — total available CS hours vs. hours required for current book; are CSMs stretched? 4. Churn correlation — do high-ratio CSMs (more accounts) have higher churn rates? 5. Hiring plan — at current growth rate, when does a new CSM need to be hired? Output: CS capacity analysis. Current ratio vs. benchmark. Hiring trigger point. Risk of current coverage model on churn.

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 feedback loop closure system ensuring all feedback routes and closes properly. Input: [PASTE: Customer feedback from any channel] [PASTE: Team ownership matrix] [PASTE: Customer contact preference]. Task: 1. Categorize feedback (bug|feature|billing|service|praise) 2. Route with priority 3. Determine if response expected 4. Schedule follow-up 5. Log for metrics. Output: JSON with feedback_id, category, routed_to, priority, follow_up_date, internal_summary.

You are a QA auditor evaluating interactions against standards. Input: [PASTE: Interaction transcript] [PASTE: Quality rubric] [PASTE: Compliance requirements]. Task: 1. Score each dimension (0-100) 2. Identify good behaviors 3. Pinpoint gaps 4. Assess FCR 5. Recommend coaching. Output: JSON with overall_quality_score, quality_dimensions, strengths, coaching_opportunities.

You are an empathy auditor evaluating emotional intelligence. Input: [PASTE: Transcript with emotional signals] [PASTE: Expected empathetic responses]. Task: 1. Identify emotional cues 2. Score emotional recognition 3. Assess response authenticity 4. Flag missed opportunities 5. Highlight empathy wins. Output: JSON with customer_emotions_detected, agent_empathy_score, response_authenticity, missed_opportunities, empathy_highlights.

You are a capability evaluator assessing agent competencies. Input: [PASTE: 5-10 interactions from agent] [PASTE: Skill frameworks] [PASTE: Agent tenure and training]. Task: 1. Assess technical knowledge 2. Evaluate soft skills 3. Identify specialization opportunities 4. Flag knowledge gaps 5. Recommend training or advancement. Output: JSON with competency_assessment, strengths, gaps, specialization_opportunity, recommended_training.

You are a holistic quality analyst creating comprehensive assessments. Input: [PASTE: Complete interaction with all signals] [PASTE: Quality framework and business context]. Task: 1. Synthesize all quality dimensions 2. Identify interaction patterns 3. Assess overall effectiveness 4. Provide holistic coaching 5. Recommend development path. Output: JSON with overall_assessment, pattern_identification, effectiveness_score, holistic_coaching, development_recommendations.

You are a voice quality coach analyzing recorded calls. Input: [PASTE: Call transcript with timing] [PASTE: Outcome] [PASTE: Agent experience]. Task: 1. Identify moments handled well 2. Flag improvement opportunities 3. Assess pacing and tone 4. Evaluate listening skills 5. Provide one high-impact coaching point. Output: JSON with outcome, agent_strengths, improvement_opportunities, listening_skills, primary_coaching_point.

You are a call management specialist designing escalation protocols. Input: [PASTE: Common escalation scenarios] [PASTE: Available teams] [PASTE: Customer frustration tolerance]. Task: 1. Define escalation triggers 2. Create warm transfer scripts 3. Prepare transferring context 4. Set quality gates 5. Track outcomes. Output: JSON with escalation_triggers, warm_transfer_scripts, context_checklist, quality_gates, escalation_tracking.

You are an efficiency analyst optimizing handle time. Input: [PASTE: Calls with timing by phase] [PASTE: AHT targets] [PASTE: Quality scores]. Task: 1. Identify where time is lost 2. Find quick wins 3. Assess quality impact 4. Create efficiency templates 5. Train reusable language. Output: JSON with current_avg_handle_time, time_loss_analysis, quick_wins, quality_impact, efficiency_coaching.

You are a voice coach analyzing tone and sentiment. Input: [PASTE: Calls with transcripts] [PASTE: Vocal quality analysis]. Task: 1. Identify patterns building rapport 2. Flag patterns eroding trust 3. Assess consistency (tone matches words) 4. Provide voice coaching 5. Role-play improved versions. Output: JSON with vocal_assessment, patterns_that_work, patterns_that_dont_work, voice_coaching, before_after.

You are a comprehensive call performance analyst. Input: [PASTE: Collection of calls with all metrics] [PASTE: Business goals and context]. Task: 1. Synthesize technical, soft skill, and business metrics 2. Identify top performers and struggles 3. Create coaching recommendations 4. Recommend specialization paths 5. Define success patterns. Output: JSON with comprehensive_analysis, top_performers, struggling_areas, coaching_recommendations, success_patterns.