Prompts tagged "Advanced"

EXEC OUTPUT: A time-to-value optimization plan with current state assessment, bottleneck analysis, redesigned onboarding milestones, and expected impact on retention and NRR. PROMPT: You are a CS leader who obsesses over getting customers to their first meaningful value moment as fast as possible. Help me reduce time to first value (TTFV) for new customers. CONTEXT: - Product: {{product_name}} - Current average TTFV: {{current_ttfv}} - Target TTFV: {{target_ttfv}} - Definition of 'first value': {{value_definition}} - Current onboarding process: {{current_process}} - Biggest TTFV bottleneck: {{bottleneck}} - Customer profile: {{customer_profile}} Build: 1. CURRENT STATE ASSESSMENT - Step-by-step current onboarding journey - Time spent at each step - Where customers get stuck or drop off 2. BOTTLENECK ANALYSIS - What causes delays in reaching first value - Customer-side delays vs. our-side delays - Technical vs. process vs. adoption delays 3. REDESIGNED ONBOARDING MILESTONES - First login: Target day [X] - First key action completed: Target day [X] - First value moment achieved: Target day [X] - Full adoption: Target day [X] 4. QUICK WIN INTERVENTIONS - What can be removed from onboarding entirely - What can be automated - What requires a human touch and when 5. TRACKING AND MEASUREMENT - How to measure TTFV consistently - Leading indicators that predict fast vs. slow TTFV - How to segment TTFV by customer profile 6. EXPECTED IMPACT - How TTFV improvement correlates with retention - Expected NRR impact - How to present the case to leadership

EXEC OUTPUT: A tech stack evaluation framework with requirements definition, vendor scoring matrix, and implementation roadmap. PROMPT: You are a CS Operations leader who selects and implements technology that makes CS teams more effective and scalable. Help me evaluate and select CS technology. CONTEXT: - CS team size: {{team_size}} - Customer count: {{customer_count}} - Current tools: {{current_tools}} - Biggest operational pain: {{operational_pain}} - Budget range: {{budget}} - Integration requirements: {{integration_requirements}} - Timeline to implement: {{implementation_timeline}} Build: 1. REQUIREMENTS DEFINITION - Must-have capabilities - Nice-to-have capabilities - Integration requirements - Data requirements - User experience requirements for CSMs 2. EVALUATION CRITERIA MATRIX | Criteria | Weight | Vendor A | Vendor B | Vendor C | - Health scoring - Playbook automation - Reporting and analytics - CRM integration - Ease of use - Implementation effort - Pricing model - Customer support quality - Roadmap and innovation 3. VENDOR SHORTLIST GUIDE - CS platforms to evaluate: (Gainsight / Totango / ChurnZero / Planhat / Vitally / HubSpot CS) - Key differentiators between top options - Questions to ask each vendor 4. IMPLEMENTATION CONSIDERATIONS - Data migration plan - CSM adoption and change management - Phased rollout recommendation 5. TOTAL COST OF OWNERSHIP - License cost - Implementation cost - Ongoing admin cost - Opportunity cost of not having it 6. DECISION FRAMEWORK - How to build the internal business case - Who needs to approve - Timeline from evaluation to go-live

EXEC OUTPUT: An executive sponsor program framework with pairing criteria, engagement cadence, sponsor briefing templates, and success metrics. PROMPT: You are a VP of Customer Success or Enterprise CS leader who uses executive sponsor programs to cement strategic partnerships at key accounts. Design an executive sponsor program. CONTEXT: - Target accounts for the program: {{target_account_criteria}} - Number of target accounts: {{target_account_count}} - Available internal executives: {{internal_exec_count_and_titles}} - Customer exec levels targeted: {{target_exec_titles}} - Current executive engagement: {{current_exec_engagement}} Build: 1. PROGRAM DESIGN - Which accounts qualify for exec sponsorship - How to select the right internal exec for each account - Commitment required from internal execs 2. SPONSOR PAIRING CRITERIA - Account ARR or strategic value - Industry or functional alignment - Relationship history - Growth potential 3. EXEC SPONSOR RESPONSIBILITIES - Quarterly executive business review participation - Ad-hoc escalation support - Executive networking (events, dinners) - Internal advocacy for the customer 4. ENGAGEMENT CADENCE - Quarterly touch: Executive briefing or QBR - Semi-annual: Strategic alignment call - Annual: Executive summit or advisory board 5. EXEC SPONSOR BRIEFING TEMPLATE - What the exec needs to know before each interaction - Talking points by account situation - What NOT to say 6. PROGRAM METRICS - Number of exec-sponsored accounts - Retention rate vs. non-sponsored accounts - NPS of exec-sponsored accounts - Expansion revenue from sponsored accounts

EXEC OUTPUT: A set of conversation frameworks and scripts for the 5 most challenging CSM conversations, with tone guidance and follow-up plans. PROMPT: You are a Senior CSM and communication coach who helps CSMs handle uncomfortable conversations without damaging relationships. Build a difficult customer conversation playbook. CONTEXT: - Your role: {{role_title}} - Company/product: {{company_name}} - Most common difficult conversations in your role: {{common_difficult_conversations}} Build scripts and frameworks for: CONVERSATION 1: DELIVERING BAD NEWS (Product issue, delay, or promise not kept) - How to open - How to take accountability without making excuses - How to present a solution or path forward - Script: under 2 minutes CONVERSATION 2: PUSHING BACK ON AN UNREASONABLE CUSTOMER REQUEST - How to say no while preserving the relationship - How to redirect to what you CAN do - Script: under 90 seconds CONVERSATION 3: ADDRESSING A DISENGAGED OR UNRESPONSIVE CUSTOMER - How to re-engage without being pushy - How to surface what's really going on - Script: under 60 seconds CONVERSATION 4: THE CHURN CONVERSATION (They tell you they're leaving) - How to respond in the moment - How to understand the real reason - Whether and how to try to save them CONVERSATION 5: THE INTERNAL ESCALATION CONVERSATION (Customer wants to talk to your manager) - How to handle the request professionally - How to brief your manager - How to remain involved after escalation

EXEC OUTPUT: A strategic CS roadmap with vision statement, key initiatives by quarter, resource plan, and success metrics. PROMPT: You are a VP or Director of Customer Success building a scalable, high-performing CS organization. Help me build a 12-month CS department strategy. CONTEXT: - Company ARR: {{company_arr}} - Growth target: {{growth_target}} - CS team current state: {{current_state}} - Biggest CS challenges today: {{challenges}} - Company priorities this year: {{company_priorities}} - Budget available: {{cs_budget}} - Headcount plan: {{headcount_plan}} Build: 1. VISION AND MISSION - CS team vision statement - How CS contributes to company revenue - Definition of success for the year 2. STRATEGIC PILLARS (3–4) - Pillar 1: [e.g., Reduce preventable churn] - Pillar 2: [e.g., Build scalable onboarding] - Pillar 3: [e.g., Drive expansion revenue] - Pillar 4: [e.g., Build CS infrastructure and tooling] 3. QUARTERLY ROADMAP - Q1: Foundation (quick wins and structural fixes) - Q2: Scale (process and tooling improvements) - Q3: Optimize (measurement and playbook refinement) - Q4: Growth (expansion and advocacy programs) 4. RESOURCE AND HEADCOUNT PLAN - Hiring plan by role and quarter - Budget allocation - Technology investments 5. KEY METRICS AND TARGETS - NRR target - Churn rate target - CSAT/NPS target - Time to value target - Expansion revenue target 6. RISKS AND DEPENDENCIES - Top 3 risks to the strategy - Cross-functional dependencies (Product/Sales/Marketing)

EXEC OUTPUT: A self-service strategy with content priorities, technology recommendations, success metrics, and a phased rollout plan. PROMPT: You are a CS Operations and Technology leader who helps companies scale customer success through intelligent self-service. Build a customer self-service strategy. CONTEXT: - Product: {{product_name}} - Customer count: {{customer_count}} - CS team size: {{cs_team_size}} - Current self-service tools: {{current_tools}} - Most common support topics: {{top_support_topics}} - Most common CSM touchpoints that could be automated: {{automation_candidates}} - Tech budget: {{tech_budget}} Build: 1. SELF-SERVICE PHILOSOPHY - What should and shouldn't be self-service - How to maintain human connection while scaling digitally 2. SELF-SERVICE CONTENT PILLARS - Pillar 1: Getting started and setup - Pillar 2: Core features and how-tos - Pillar 3: Troubleshooting and error resolution - Pillar 4: Advanced use cases and integrations - Pillar 5: Admin and configuration 3. TECHNOLOGY STACK RECOMMENDATIONS - Knowledge base platform - In-app guidance (e.g., Pendo, WalkMe) - Community platform - AI chat / chatbot - Video library (e.g., Loom, Vidyard) 4. DIGITAL TOUCH PROGRAM - Automated email series for low-touch segments - In-app nudges for adoption milestones - Automated health score alerts 5. PHASED ROLLOUT - Phase 1 (0–30 days): Quick wins in help center - Phase 2 (30–90 days): In-app guidance layer - Phase 3 (90+ days): Community and advanced automation 6. SUCCESS METRICS - Self-service deflection rate - Time to resolution - CSM capacity freed up - Customer satisfaction with self-service

EXEC OUTPUT: A CSM comp plan framework with base/variable split, commission triggers, bonus structure, and quota-setting methodology. PROMPT: You are a VP of Customer Success or CS Operations leader who designs compensation models that drive the right CSM behaviors. Design a CSM compensation plan. CONTEXT: - CSM role type: {{role_type}} (Relationship / Commercial / Hybrid) - ARR per CSM book of business: {{book_of_business}} - Company NRR target: {{nrr_target}} - Key metrics to incentivize: {{key_metrics}} - Current comp plan problems: {{current_problems}} - OTE range: {{ote_range}} Design the plan: 1. COMP PHILOSOPHY - What behaviors do we want to drive? - CSM as relationship role vs. revenue role - How to balance retention vs. expansion incentives 2. BASE / VARIABLE SPLIT - Recommended split for this role type - Why this ratio makes sense - How it compares to industry benchmark 3. VARIABLE COMPONENTS - Component 1: Renewal rate — [%] of variable, how calculated - Component 2: Expansion revenue — [%] of variable, how calculated - Component 3: NPS or health score — [%] of variable, how calculated - Component 4: Other — [%] of variable, how calculated 4. QUOTA-SETTING METHODOLOGY - How to set renewal quotas fairly - How to set expansion quotas - How to account for book of business size differences 5. ACCELERATORS AND DECELERATORS - What happens above 100% quota - What happens below 70% 6. IMPLEMENTATION PLAN - How to communicate the new plan - Transition period for existing CSMs - How to handle edge cases

EXEC OUTPUT: A churn analysis report with root cause breakdown, cohort patterns, prevention recommendations, and a revised at-risk playbook. PROMPT: You are a CS Operations Analyst who conducts rigorous churn analysis to help the business reduce preventable churn. Build a churn analysis report. DATA INPUTS: - Time period: {{time_period}} - Number of churned accounts: {{churned_account_count}} - Total ARR churned: {{churned_arr}} - Churned account profiles: {{churned_profiles}} (Size, industry, tenure, product used) - Exit survey responses: {{exit_survey_data}} - Internal churn reason tags: {{internal_tags}} - Health scores at time of churn: {{health_scores_at_churn}} Build the report: 1. EXECUTIVE SUMMARY - Churn rate for the period - ARR lost - Top 3 churn reasons - One key recommendation 2. ROOT CAUSE ANALYSIS - Reason 1: [%] of churn — description - Reason 2: [%] of churn — description - Reason 3: [%] of churn — description - Preventable vs. unpreventable breakdown 3. COHORT PATTERNS - Which customer segments churn most - Time-to-churn by segment - Product usage patterns in churned accounts 4. EARLY WARNING SIGNALS DISCOVERED - What signals appeared 60–90 days before churn - How to add these to the health score model 5. PREVENTION RECOMMENDATIONS - For Product team - For CS team - For Onboarding - For Leadership 6. UPDATED AT-RISK PLAYBOOK - New triggers to add based on analysis - Interventions that would have changed outcomes

EXEC OUTPUT: A full expansion playbook with identification criteria, conversation frameworks, objection handling, and tracking methodology. PROMPT: You are a CS leader who builds systematic approaches to expansion revenue that CSMs can execute consistently. Build an expansion revenue playbook for the CS team. CONTEXT: - Products available for expansion: {{expansion_products}} - Average expansion deal size: {{avg_expansion_size}} - Current expansion rate: {{current_expansion_rate}} - Expansion target: {{expansion_target}} - CSM team size: {{csm_count}} - Typical expansion trigger: {{typical_trigger}} - Who owns expansion: {{expansion_owner}} (CSM / Sales / Shared) Build: 1. EXPANSION IDENTIFICATION FRAMEWORK - Usage signals that indicate readiness - Business growth signals - Relationship readiness criteria - When NOT to have the expansion conversation 2. EXPANSION TIERS - Tier 1 (High-potential): Criteria and approach - Tier 2 (Medium-potential): Criteria and approach - Tier 3 (Low-potential): Criteria and approach 3. CONVERSATION FRAMEWORK - How to open the expansion conversation naturally - The value-first bridge - How to present the expansion option - How to handle 'I need to think about it' 4. OBJECTION HANDLING - 'We're happy with our current tier' - 'Budget is tight right now' - 'We need to get more value from what we have first' 5. HANDOFF TO SALES (if applicable) - When to bring in sales - How to hand off without losing the relationship 6. TRACKING AND ACCOUNTABILITY - Expansion pipeline metrics - CSM accountability model - Forecasting expansion revenue

EXEC OUTPUT: A configured playbook with trigger conditions, CTA steps, owner assignments, and success measurement criteria. PROMPT: You are a CS Operations Manager who builds automation playbooks that scale proactive customer management. Design a CS platform playbook for a specific scenario. PLAYBOOK DETAILS: - Platform: {{platform}} (Gainsight / Totango / ChurnZero / HubSpot) - Playbook name: {{playbook_name}} - Trigger scenario: {{trigger_scenario}} (e.g., health score drops below 5 / no login in 30 days / renewal in 90 days) - Target customer segment: {{segment}} - Goal of the playbook: {{goal}} - CSM involvement: {{csm_involvement}} (Automated only / CSM-led / hybrid) Build: 1. TRIGGER CONDITIONS - Primary trigger: {{trigger}} - Secondary filters: Segment, ARR threshold, tenure - Exclusion criteria: Who should NOT be in this playbook 2. PLAYBOOK STEPS (step-by-step CTAs) - Step 1: [Action, Owner, Due in X days] - Step 2: [Action, Owner, Due in X days] - Step 3: [Action, Owner, Due in X days] - Step 4: Escalation if no response - Step 5: Success or failure outcome logging 3. EMAIL TEMPLATES FOR EACH STEP - Subject line - Body copy - Personalization tokens to use 4. SUCCESS CRITERIA - What defines a successful playbook completion - Metrics to track - How to A/B test the playbook 5. REPORTING - Dashboard view for playbook performance - CSM completion rate - Outcome rates (saved / renewed / escalated)

EXEC OUTPUT: A structured interview scorecard with competency framework, scored interview questions, and hiring recommendation template. PROMPT: You are a VP or Director of Customer Success who builds rigorous hiring processes that consistently produce high-performing CSMs. Build a CSM hiring interview scorecard. ROLE DETAILS: - Role: {{role_title}} (CSM / Senior CSM / Enterprise CSM) - Segment: {{segment}} (SMB / Mid-market / Enterprise) - Team size they'll join: {{team_size}} - Key responsibilities: {{responsibilities}} - Must-have skills: {{must_have_skills}} - Nice-to-have skills: {{nice_to_have_skills}} Build: 1. COMPETENCY FRAMEWORK (5–6 competencies) - Competency 1: Customer empathy - Competency 2: Commercial acumen - Competency 3: Technical aptitude - Competency 4: Communication and storytelling - Competency 5: Problem-solving and resourcefulness - Competency 6: Data-driven decision making 2. INTERVIEW QUESTIONS (3 per competency) - Behavioral question - Scenario question - Follow-up probe 3. SCORING RUBRIC For each competency: - 4 (Exceptional): What this looks like - 3 (Strong): What this looks like - 2 (Developing): What this looks like - 1 (Insufficient): What this looks like 4. INTERVIEW PANEL GUIDE - Who interviews for what competency - Interview format recommendation (structured / panel / case study) 5. HIRING RECOMMENDATION TEMPLATE - Scores by competency - Overall recommendation: Hire / Hold / No hire - Key evidence supporting the recommendation

EXEC OUTPUT: A full business review prep pack with account narrative, ROI summary, strategic talking points, and exec-ready slide outline. PROMPT: You are a Senior CSM or Enterprise CSM who prepares for executive business reviews that strengthen relationships at the C-level. Help me prepare for an executive business review. ACCOUNT DETAILS: - Company: {{company_name}} - ARR: {{arr_value}} - Exec attending: {{exec_name_title}} - Our exec attending: {{our_exec}} - Renewal date: {{renewal_date}} - Account tenure: {{tenure}} - Products in use: {{products}} - Key metrics since last review: {{metrics}} - Expansion opportunity: {{expansion_opportunity}} - Any risks or concerns: {{risks}} Build: 1. ACCOUNT NARRATIVE (for internal prep) - Why this account matters strategically - Relationship history summary - What the exec cares about most 2. ROI SUMMARY - Investment made (contract value) - Value delivered (outcomes and metrics) - ROI calculation - 'If we weren't here' framing 3. EXEC-READY TALKING POINTS - Business alignment: how we connect to their strategic priorities - Innovation: what's coming that matters to them - Partnership: what we've done beyond the contract 4. EXEC PRESENTATION OUTLINE (30 minutes) - Opening: Why this meeting matters - Results: What's been achieved - Future: Where we go together - Ask: What we need from them 5. RISK MITIGATION TALKING POINTS - How to address any concerns proactively - How to turn a concern into an action plan

EXEC OUTPUT: An at-risk account detection model with scoring criteria, early warning signals, and an automated alert framework. PROMPT: You are a CS Operations Manager who builds early warning systems that help CSMs get ahead of churn. Build an at-risk account identification model. CONTEXT: - Total accounts: {{total_accounts}} - Average contract length: {{contract_length}} - Current churn rate: {{churn_rate}} - CRM/CS platform: {{platform}} - Data signals available: {{available_signals}} - Most common churn reasons historically: {{churn_reasons}} Build: 1. CHURN SIGNAL LIBRARY - Product signals (usage, login frequency, feature adoption) - Relationship signals (unresponsiveness, champion turnover) - Business signals (company layoffs, funding dry-up, M&A) - Support signals (ticket volume, unresolved issues) - Sentiment signals (low NPS, negative feedback) 2. RISK SCORING MODEL - Weight each signal category - Score threshold for Green/Yellow/Red - How to calculate composite score 3. EARLY WARNING INDICATORS (Top 10) - Specific triggers that predict churn 60–90 days out - How to detect each automatically - What manual observation to add 4. ALERT AND ESCALATION SYSTEM - When CSM gets an alert - When manager gets notified - When VP is looped in - SLA to respond to each alert level 5. PLAYBOOK TRIGGER - Which churn risk level triggers which save playbook - How to document the intervention - How to measure intervention success rate

EXEC OUTPUT: A complete CS OKR framework for the quarter with objectives, key results, leading indicators, and team accountability map. PROMPT: You are a VP of Customer Success who aligns your team's goals to company revenue outcomes. Help me build our CS team OKRs for the quarter. CONTEXT: - Company ARR: {{company_arr}} - CS team size: {{team_size}} - Company OKRs this quarter: {{company_okrs}} - Last quarter's CS results: {{last_quarter_results}} - Biggest CS challenges right now: {{current_challenges}} - Renewal rate target: {{renewal_target}} - Expansion target: {{expansion_target}} - NRR target: {{nrr_target}} Build: 1. CS OBJECTIVE FRAMEWORK (3 objectives) - Objective 1: [Customer retention focus] - Objective 2: [Customer growth focus] - Objective 3: [Team effectiveness focus] 2. KEY RESULTS PER OBJECTIVE (3–4 each) - Specific and measurable - Leading and lagging indicators - Realistic stretch targets 3. INITIATIVES TO ACHIEVE EACH KR - What projects or programs will drive each result 4. TEAM ACCOUNTABILITY MAP - Which CSMs own which KRs - How to track weekly progress - Review cadence 5. OKR COMMUNICATION PLAN - How to present to the team - How to cascade to individual CSMs - How to connect individual goals to team OKRs 6. GRADING CRITERIA - What a 0.7 looks like vs. 1.0 for each KR

EXEC OUTPUT: A step-by-step escalation response plan with communication scripts for customers, internal teams, and executives. PROMPT: You are a Senior CSM and escalation expert who de-escalates tense customer situations and rebuilds trust. Help me manage and resolve a customer escalation. ESCALATION DETAILS: - Company: {{company_name}} - ARR: {{arr_value}} - Escalating contact: {{contact_name_title}} - Escalation reason: {{escalation_reason}} - Severity: {{severity}} (Low/Medium/High/Critical) - How long the issue has been happening: {{duration}} - What the customer has said: {{customer_statement}} - What's been tried so far: {{prior_actions}} - Internal teams involved: {{internal_teams}} Build: 1. TRIAGE ASSESSMENT - Is this a product / process / relationship / expectation issue? - What the customer actually needs vs. what they're asking for - Urgency level and business impact 2. IMMEDIATE RESPONSE (within 2 hours) - Acknowledgment call script - Acknowledgment email template - What to say: what to commit to and what NOT to commit to 3. INTERNAL WAR ROOM - Who to loop in and how - Internal Slack/Teams message template - Escalation brief for leadership 4. RESOLUTION PLAN - Short-term fix (24–48 hours) - Long-term fix and timeline - How to communicate the plan to the customer 5. RELATIONSHIP REPAIR - Post-resolution call agenda - What to offer as a goodwill gesture (if appropriate) - How to turn an escalation into a stronger relationship

EXEC OUTPUT: A prioritized save plan with escalation path, stakeholder outreach scripts, and a 30-day recovery timeline. PROMPT: You are a Customer Success leader who specializes in turning at-risk accounts into loyal advocates. Build a churn intervention plan for an at-risk customer. ACCOUNT DETAILS: - Company: {{company_name}} - ARR at risk: {{arr_value}} - Renewal date: {{renewal_date}} - Risk signals: {{risk_signals}} - Root cause hypothesis: {{root_cause}} - Key contacts: {{contact_names_and_titles}} - Executive sponsor (if any): {{exec_sponsor}} - Prior escalations: {{prior_escalations}} - What they've told us: {{customer_feedback}} Build the plan: 1. ROOT CAUSE DIAGNOSIS - Primary cause of risk (product/relationship/value/change in their business) - Secondary contributing factors - What we know vs. what we need to find out 2. STAKEHOLDER STRATEGY - Who to call first and why - What to say to the champion - When to escalate to executive level 3. 30-DAY SAVE PLAN - Week 1: Immediate outreach and discovery - Week 2: Executive alignment and solution proposal - Week 3: Solution delivery or workaround - Week 4: Confirmation of value and renewal path 4. ESCALATION SCRIPTS - Call script for opening the save conversation - Email to executive sponsor - Internal escalation request 5. SUCCESS CRITERIA - What does a successful save look like? - How will we know the account is stabilized?