Prompts tagged "Analytical"

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: A CSAT survey design, scoring methodology, response analysis framework, and improvement action plan. PROMPT: You are a Customer Experience Manager who uses CSAT data to continuously improve service quality. Design a CSAT survey program and analysis framework. CONTEXT: - Product/service: {{product_name}} - Survey touchpoints: {{touchpoints}} (Post-onboarding / post-support / post-QBR / quarterly pulse) - Current CSAT score: {{current_csat}} - Target CSAT score: {{target_csat}} - Response rate: {{response_rate}} - Survey tool: {{survey_tool}} - Team reviewing results: {{review_team}} Build: 1. SURVEY DESIGN - Core CSAT question: 'How satisfied were you with [X]?' (1–5 scale) - Follow-up question options: - What did we do well? - What could we improve? - Net effort score question - Length: Maximum 3 questions - Timing and delivery recommendations 2. SEGMENTATION - How to break down CSAT by: - Customer tier - Product area - Support category - CSM 3. SCORING AND BENCHMARKING - How to calculate CSAT % - Industry benchmarks by category - Internal trending targets 4. RESPONSE ANALYSIS FRAMEWORK - Categorize open-text responses by theme - Identify top drivers of high and low scores - Monthly review process 5. ACTION PLAN - How to respond to low CSAT scores within 48 hours - How to use CSAT data in team performance reviews - How to share insights with Product and CS leadership 6. CLOSING THE LOOP - Response template for low CSAT - How to turn a negative experience into a recovery win

EXEC OUTPUT: A 5-stage customer maturity model with criteria for each stage, CSM actions per stage, and progression triggers. PROMPT: You are a Senior CSM or CS leader who uses maturity models to systematically move customers up the adoption curve. Build a customer maturity model for your product. CONTEXT: - Product: {{product_name}} - Key use cases: {{key_use_cases}} - Typical customer journey: {{journey_description}} - Adoption metrics available: {{adoption_metrics}} - Time to full adoption (typical): {{time_to_adoption}} Build: 1. MATURITY STAGES (5 levels) - Stage 1: Activated (set up, first login, basic configuration) - Stage 2: Adopting (core use case in use, team using regularly) - Stage 3: Proficient (key features adopted, measurable ROI) - Stage 4: Advanced (full feature adoption, integrated workflows) - Stage 5: Champion (advocacy, expansion, reference-ready) 2. CRITERIA FOR EACH STAGE - Quantitative: Usage metrics, feature adoption % - Qualitative: Feedback, engagement, champion presence 3. CSM ACTIONS BY STAGE - How to move customer from Stage 1 → 2 - How to move from Stage 2 → 3 - And so on through Stage 5 4. STUCK-STAGE PLAYBOOK - Signs a customer is stuck at a stage - Why they might be stuck (common blockers) - Intervention actions 5. MEASURING PROGRESSION - How to track stage in CRM/CS platform - Distribution across your book (how healthy is it?) - Correlation between stage and renewal/expansion rate

EXEC OUTPUT: A product feedback loop design with capture methods, routing rules, prioritization criteria, and a closed-loop communication process. PROMPT: You are a CS Operations leader who builds systems that make sure customer product feedback actually reaches the product team and gets acted on. Build a customer product feedback loop. CONTEXT: - Product: {{product_name}} - CS team size: {{cs_team_size}} - Product team contact: {{product_contact}} - Current feedback process: {{current_process}} - Biggest gap: {{biggest_gap}} - Tools available: {{tools}} (Productboard / Jira / Salesforce / Gainsight / etc.) Build: 1. FEEDBACK CAPTURE METHODS - In-product feedback (NPS, in-app surveys) - CSM-sourced feedback (call notes, email) - Support ticket analysis - Customer interview programs - Advisory board input 2. FEEDBACK CATEGORIZATION - Feature request - Bug report - UX improvement - Performance issue - Integration request - How to tag and categorize consistently 3. ROUTING RULES - Who receives each type of feedback - SLA for acknowledgment by product team - How to handle duplicate requests 4. PRIORITIZATION FRAMEWORK - Volume (how many customers request this) - ARR impact (what ARR is asking for this) - Strategic alignment (does this fit the roadmap) - Effort vs. impact scoring 5. CLOSED-LOOP COMMUNICATION - How to notify CSMs when feedback is actioned - How CSMs communicate back to customers - Customer-facing roadmap communication template 6. METRICS - Feedback submitted per month - Feedback-to-product-action rate - Time from feedback to product decision

EXEC OUTPUT: A structured 90-day onboarding plan for a new CSM with milestones, learning objectives, shadowing schedule, and first book of business criteria. PROMPT: You are a CS Director or Enablement Manager who onboards new CSMs to be productive and confident quickly. Build a 30-60-90 day ramp plan for a new Customer Success Manager. CONTEXT: - New hire name: {{name}} - Role: {{role_title}} - Segment: {{segment}} (SMB / Mid-market / Enterprise) - Start date: {{start_date}} - Manager: {{manager_name}} - Team they're joining: {{team_context}} - Tools they'll use: {{tools}} Build: DAYS 1–30: LEARN - Week 1: Company, product, and team orientation - Week 2: Product deep-dive and shadowing - Week 3: CS process, tools, and playbooks - Week 4: First customer introductions and co-pilot calls MILESTONES AT 30 DAYS: - Product certification complete - Shadowed 5+ customer calls - CRM and CS platform setup - First book of business accounts reviewed DAYS 31–60: BUILD - Own 25% of book of business - First QBR or check-in call completed independently - First renewal or expansion conversation coached - Manager 1:1 cadence established MILESTONES AT 60 DAYS: - [Number] accounts fully owned - First at-risk account identified and plan created - NPS response handled independently DAYS 61–90: PERFORM - Full book of business ownership - First QBR run independently - Contributing to team playbooks - First renewal closed MILESTONES AT 90 DAYS: - 100% of book owned - Health scores assessed for all accounts - Performance metrics established

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 knowledge base audit report with content gap analysis, quality scorecard, recommended new articles, and a 60-day content improvement plan. PROMPT: You are a Customer Education Specialist who optimizes knowledge bases to reduce support tickets and improve customer self-service. Conduct a knowledge base audit and improvement plan. CONTEXT: - Product: {{product_name}} - Knowledge base platform: {{kb_platform}} - Total articles: {{total_articles}} - Monthly views: {{monthly_views}} - Top support ticket topics (last 90 days): {{top_ticket_topics}} - Article feedback data (helpful / not helpful): {{feedback_data}} - Last major content update: {{last_update_date}} Build: 1. CONTENT AUDIT FRAMEWORK - Categories to review - Quality criteria per article (accurate / clear / current / actionable) - How to score each article: Pass / Update / Archive 2. GAP ANALYSIS - Top ticket topics with NO corresponding article - Topics with articles that get poor ratings - Features released in last 6 months with no documentation 3. QUALITY SCORECARD - Average article quality by category - Most searched but low-satisfaction articles - Highest-impact articles to prioritize 4. RECOMMENDED NEW ARTICLES (Top 10) - Title and description - Priority (High/Medium/Low) - Estimated effort 5. 60-DAY IMPROVEMENT PLAN - Week 1–2: Archive outdated content - Week 3–4: Update top 10 existing articles - Week 5–6: Publish top 5 new articles - Week 7–8: Review and QA all changes 6. SUCCESS METRICS - Ticket deflection rate - Article satisfaction score - Search-to-article match rate

EXEC OUTPUT: A comprehensive technical onboarding checklist covering environment setup, integrations, data migration, security, and go-live validation. PROMPT: You are an Implementation Engineer who ensures enterprise customers are technically set up for success from day one. Build a technical onboarding checklist for a new enterprise customer. CUSTOMER DETAILS: - Company: {{company_name}} - Product: {{product_name}} - Technical environment: {{tech_environment}} - Integrations required: {{integrations}} - Data migration scope: {{data_migration_scope}} - Security requirements: {{security_requirements}} - IT contacts: {{it_contacts}} - Go-live date: {{golive_date}} Build the checklist: 1. ENVIRONMENT SETUP - User provisioning and SSO configuration - Role and permission structure - Admin account setup - Environment testing (staging vs. production) 2. INTEGRATION CHECKLIST - Integration 1: {{integration_1}} — setup steps and validation - Integration 2: {{integration_2}} — setup steps and validation - API key management and documentation - Webhook configuration and testing 3. DATA MIGRATION - Data audit and mapping - Migration script testing - Data validation post-migration - Rollback plan 4. SECURITY AND COMPLIANCE - SSO and MFA configuration - Data residency confirmation - Security review sign-off - Compliance documentation provided 5. GO-LIVE VALIDATION - Smoke test checklist - User acceptance testing (UAT) sign-off - Performance baseline - Monitoring and alerting setup 6. HANDOFF TO SUPPORT - Known issues and workarounds documented - Escalation contacts confirmed - Support tier configured

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 quarter renewal forecast with confidence tiering, ARR at risk, expected renewals, and action plan per deal. PROMPT: You are a Renewal Manager who builds accurate renewal forecasts that leadership can trust. Help me build a quarterly renewal forecast. MY RENEWALS: - Total ARR up for renewal this quarter: {{total_renewal_arr}} - Number of accounts renewing: {{renewal_account_count}} - My renewal target: {{renewal_target_percent}} For each account category, provide framework: 1. RENEWAL CONFIDENCE TIERS - Green (>80% confidence): Criteria and evidence needed - Yellow (50–80% confidence): Criteria and risk flags - Red (<50% confidence): Criteria and intervention triggers 2. ACCOUNT-BY-ACCOUNT TEMPLATE | Account | ARR | Renewal Date | Health Score | Confidence | Risk Flags | Next Action | 3. FORECAST SUMMARY - Committed ARR (Green accounts) - At-risk ARR (Yellow + Red accounts) - Expected renewal rate - Gap to target 4. ACTION PLAN BY TIER - Green: Maintenance touchpoints - Yellow: Intervention steps - Red: Save plan activation 5. RISK MITIGATION - Top 3 things that could hurt the forecast - How to protect committed ARR - Escalation criteria for Red accounts 6. REPORTING TO LEADERSHIP - Weekly forecast update format - What to escalate vs. manage independently - How to communicate slippage early

EXEC OUTPUT: A full-year outreach cadence by customer tier with touchpoint types, topics by quarter, and email and call templates. PROMPT: You are a CSM who keeps customers engaged and successful through consistent, valuable proactive outreach. Build a proactive outreach cadence for my book of business. MY BOOK: - Number of accounts: {{account_count}} - Tier breakdown: {{tier_breakdown}} - Average ARR per account: {{avg_arr}} - Current touchpoint frequency: {{current_cadence}} - Available time for outreach per week: {{weekly_hours}} - Tools available: {{tools}} (Gainsight/Totango/HubSpot/etc.) Build: 1. CADENCE BY TIER Tier 1 (Enterprise): - Monthly: [Type of touch] - Quarterly: [Type of touch] - Annually: [Type of touch] Tier 2 (Mid-market): - Bi-monthly: [Type of touch] - Quarterly: [Type of touch] Tier 3 (SMB): - Quarterly: [Type of touch] - Automated touches: [What to automate] 2. TOUCHPOINT CONTENT CALENDAR - Q1 theme: [e.g., New year planning / goal alignment] - Q2 theme: [e.g., Mid-year ROI check-in] - Q3 theme: [e.g., Usage review and new features] - Q4 theme: [e.g., Renewal prep and planning] 3. OUTREACH TEMPLATES - Proactive check-in email - Milestone celebration email - Product update email - Re-engagement email for silent accounts 4. TIME MANAGEMENT - How to batch outreach efficiently - Which accounts to prioritize each week - How to use automation without losing the human touch

EXEC OUTPUT: A complete CS metrics framework with KPI definitions, benchmarks, dashboard layout, and team accountability structure. PROMPT: You are a CS Operations leader who builds metric systems that drive proactive customer management. Build a customer success metrics dashboard framework. CONTEXT: - Team size: {{csm_count}} - Customer count: {{customer_count}} - ARR: {{total_arr}} - Current tools: {{tools_used}} - Key business goals: {{business_goals}} - Biggest measurement gap: {{measurement_gap}} Build: 1. TIER 1 METRICS (Board-level outcomes) - Net Revenue Retention (NRR): definition and target - Gross Revenue Retention (GRR): definition and target - Customer churn rate: definition and target - Expansion revenue: definition and target 2. TIER 2 METRICS (Team performance) - Health score distribution - QBR completion rate - Time to first value (TTFV) - Onboarding completion rate - Renewal forecast accuracy 3. TIER 3 METRICS (Leading indicators — daily/weekly) - Touchpoint frequency by tier - Tickets per account - Feature adoption rates - Executive sponsor coverage 4. DASHBOARD LAYOUT RECOMMENDATION - Executive view (monthly) - Manager view (weekly) - CSM view (daily) 5. BENCHMARKS - Industry benchmarks per metric - How to set internal targets - Red/amber/green thresholds 6. ACCOUNTABILITY MODEL - Who owns each metric - Review cadence - How metrics tie to compensation

EXEC OUTPUT: A tiered escalation matrix with response SLAs, ownership by level, and customer communication templates for each severity. PROMPT: You are a Customer Service Manager who builds escalation systems that resolve issues fast and protect customer relationships. Build a support ticket escalation framework. CONTEXT: - Product type: {{product_type}} - Support team size: {{support_team_size}} - Customer tiers: {{customer_tiers}} - Current average resolution time: {{current_resolution_time}} - Most common escalation triggers: {{escalation_triggers}} - Tools used: {{support_tools}} (Zendesk/Intercom/Salesforce/etc.) Build: 1. SEVERITY DEFINITIONS - P1 (Critical): Definition and examples - P2 (High): Definition and examples - P3 (Medium): Definition and examples - P4 (Low): Definition and examples 2. ESCALATION MATRIX | Severity | Response SLA | Resolution SLA | Level 1 Owner | Level 2 Owner | Level 3 Owner | 3. ESCALATION TRIGGERS - When to escalate from L1 to L2 - When to escalate from L2 to L3 - When to pull in the CSM - When to notify leadership 4. CUSTOMER COMMUNICATION TEMPLATES - P1 acknowledgment email (within 1 hour) - Status update template (every 4 hours for P1) - Resolution notification email - Post-incident summary template 5. INTERNAL ESCALATION PROCESS - Slack/Teams notification format - Escalation brief template - Post-mortem process for P1 incidents

EXEC OUTPUT: A customer segmentation framework with tier definitions, coverage models, and resource allocation recommendations. PROMPT: You are a CS Operations Manager who builds scalable systems to ensure every customer gets the right level of attention. Help me build a customer segmentation model for my CS team. CUSTOMER BASE DETAILS: - Total customers: {{total_customers}} - ARR range across base: {{arr_range}} - Team size (CSMs): {{csm_count}} - Average book of business per CSM: {{book_of_business}} - Current segmentation (if any): {{current_segmentation}} - Key variables available in CRM: {{crm_variables}} Build: 1. TIER DEFINITIONS - Tier 1 (Enterprise/Strategic): Criteria and ARR threshold - Tier 2 (Mid-market): Criteria and ARR threshold - Tier 3 (SMB/Digital): Criteria and ARR threshold - Tier 4 (Self-serve/Community): Criteria 2. COVERAGE MODEL PER TIER - CSM ratio (customers per CSM) - Touchpoint cadence - Channel (high-touch / low-touch / tech-touch / self-serve) - QBR frequency 3. SCORING CRITERIA - ARR weight: [%] - Growth potential weight: [%] - Strategic importance weight: [%] - Complexity weight: [%] 4. RESOURCE ALLOCATION RECOMMENDATIONS - How many CSMs per tier - Where to invest vs. automate - Metrics to track by tier 5. MIGRATION RULES - How customers move between tiers - Review frequency for tier assignments

EXEC OUTPUT: A risk matrix for the implementation with mitigation plans, revised timeline, and stakeholder communication guide. PROMPT: You are an Implementation Manager who proactively identifies risks before they derail go-live. Run an implementation risk assessment for an active project. PROJECT DETAILS: - Customer: {{company_name}} - Product: {{product_name}} - Go-live date: {{golive_date}} - Current phase: {{current_phase}} - Days until go-live: {{days_to_golive}} - Current blockers: {{current_blockers}} - Customer engagement level: {{engagement_level}} (High/Medium/Low) - Technical complexity: {{technical_complexity}} - Dependencies: {{dependencies}} Build the assessment: 1. RISK MATRIX | Risk | Likelihood (H/M/L) | Impact (H/M/L) | Owner | Mitigation | - List 6–10 risks 2. TOP 3 CRITICAL RISKS - Detailed analysis of each - Why it matters - Specific mitigation steps 3. GO-LIVE READINESS SCORECARD - Configuration complete: [%] - Data migration complete: [%] - User training complete: [%] - Integration testing complete: [%] - Overall readiness: [Go / Caution / Not Ready] 4. REVISED TIMELINE (if needed) - Adjusted milestones - New go-live date recommendation - How to communicate the change 5. STAKEHOLDER COMMUNICATION - Email to customer champion about risks - Internal escalation if critical risk identified

EXEC OUTPUT: A structured VoC report with top themes, sentiment scores, product feedback, and prioritized recommendations for internal teams. PROMPT: You are a Customer Insights Analyst who transforms raw customer feedback into strategic business intelligence. Synthesize customer feedback into a Voice of Customer (VoC) insight report. INPUT DATA: - Feedback source(s): {{feedback_sources}} (NPS / CSAT / interviews / support tickets / churn surveys) - Time period: {{time_period}} - Number of responses: {{response_count}} - Customer segments included: {{segments}} - Raw feedback themes: {{raw_themes}} - Top verbatim quotes: {{top_quotes}} Build the report: 1. EXECUTIVE SUMMARY (half page) - 3 headline findings - Overall sentiment trend - Most urgent recommendation 2. THEME ANALYSIS - Top 5 themes by frequency - Sentiment per theme (positive/neutral/negative) - Representative quotes per theme 3. SEGMENT BREAKDOWN - How feedback differs by customer size, industry, or tenure - Which segments are happiest / most at risk 4. PRODUCT FEEDBACK - Feature requests (ranked by frequency) - Bugs or friction points mentioned - What customers love (protect this) 5. RECOMMENDATIONS - For Product team - For Customer Success team - For Leadership - Priority: Quick wins vs. strategic initiatives 6. NEXT STEPS - How to share findings internally - How to close the loop with customers who gave feedback

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: Response templates and action plans for all three NPS categories, plus a follow-up workflow to close the loop. PROMPT: You are a Customer Experience Manager who turns NPS feedback into relationship-strengthening actions. Build an NPS response playbook. CONTEXT: - Product: {{product_name}} - NPS score received: {{nps_score}} - Customer: {{company_name}} - Contact: {{contact_name_title}} - Their verbatim feedback: {{verbatim_feedback}} - Customer tenure: {{tenure}} - ARR: {{arr_value}} - Renewal date: {{renewal_date}} Build responses for each scenario: DETRACTOR (Score 0–6): - Acknowledgment email (within 24 hours) - How to open a recovery conversation - Call script for follow-up - Escalation criteria PASSIVE (Score 7–8): - Response email that moves them toward promoter - One action to improve their experience - How to identify the gap and close it PROMOTER (Score 9–10): - Thank-you response that feels genuine - How to ask for a reference, case study, or review - How to deepen the relationship WORKFLOW: - Who gets notified when NPS comes in - Response SLA by category - How to close the loop in CRM - Monthly NPS review process

EXEC OUTPUT: A week-by-week onboarding plan with milestones, owners, and success checkpoints for a new customer implementation. PROMPT: You are an Implementation Manager who delivers onboarding projects on time and sets customers up for measurable success. Create a detailed onboarding project plan. CUSTOMER DETAILS: - Company: {{company_name}} - Product: {{product_name}} - Complexity: {{complexity_level}} (Simple / Standard / Complex) - Go-live date: {{golive_date}} - Internal champion: {{champion_name_title}} - Their team involved: {{customer_team}} - Our team: {{internal_team}} - Key integrations needed: {{integrations}} - Data migration required: {{data_migration_yes_no}} Build the plan: 1. ONBOARDING PHASES - Phase 1: Setup and configuration (Week 1–2) - Phase 2: Data and integration (Week 2–3) - Phase 3: Training and adoption (Week 3–4) - Phase 4: Go-live and stabilization (Week 4–6) - Phase 5: Value confirmation (Week 6–8) 2. MILESTONE TRACKER | Milestone | Owner | Due Date | Status | 3. RISK LOG - Top 3 onboarding risks - Mitigation plan for each 4. COMMUNICATION PLAN - Weekly status update format - Escalation path if milestones slip - Stakeholder update cadence 5. SUCCESS CRITERIA - Definition of a successful go-live - 30/60/90-day adoption targets