Customer Success Prompts to Save Time On Repetitive Tasks

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 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 a customer success manager building an expansion revenue playbook. Business context: [DESCRIBE: Product/platform, expansion types available (seats/modules/usage/services), typical expansion triggers, current expansion process (defined or ad hoc), who owns expansion (CS/sales/both)] Build the playbook: 1. Expansion triggers — specific customer signals that indicate readiness: usage hitting limits / new team onboarded / new use case discussed / renewal with growth 2. Expansion qualification — criteria for a genuine expansion opportunity vs. a wish 3. Conversation approach — how to raise expansion in the context of customer value, not our quota 4. Handoff decision — at what point does CS own the expansion vs. hand to sales? 5. Objection handling — top 3 expansion objections and how to address them Output: Expansion playbook. Trigger list. Qualification criteria. Conversation guide. Handoff rules.

You are a customer success manager building an intervention plan for a Red-status account. Account data: [PASTE: Account | ARR | Health indicators (usage drop / support escalations / NPS low / champion left / payment issue) | Renewal date | What has been tried | Root cause hypothesis] Build the intervention plan: 1. Root cause — what is actually driving the risk? (product gap / adoption failure / competitive / relationship / budget) 2. Intervention owner — CSM / account manager / VP-level / executive sponsor? 3. Specific actions — each action tied to a root cause; not generic "check in calls" 4. Timeline — what must happen in the next 7 / 30 / 60 days to prevent churn? 5. Go/no-go decision — at what point do we accept churn is likely and shift to minimum-cost retention vs. maximum-effort recovery? Output: Account intervention plan. Day 1 / Week 1 / Month 1 actions with owner. Decision trigger for escalation or accept.

You are a customer success operations manager designing lifecycle communications. Context: [DESCRIBE: Product type, customer segments, key lifecycle moments (onboarding / first value / adoption milestone / renewal / expansion), current automated communications in place, any gaps in coverage] Design the lifecycle communication plan: 1. Onboarding sequence (Days 1–30): welcome / setup completion nudge / first-use guidance / check-in 2. Adoption phase (Days 31–90): feature discovery / best practice tips / peer benchmark / 60-day check-in 3. Value realization (Day 90): value summary / ROI snapshot / request for feedback 4. Ongoing engagement: monthly product updates / quarterly business review invitation / renewal prep 5. Expansion triggers: usage-limit notifications / new feature relevant to their use case / peer success story For each communication: channel (email/in-app/call) / owner (automated/CSM/exec) / goal. Output: Lifecycle communication map. Owner and channel per touchpoint. Gaps in current coverage. Recommended additions.

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 manager preparing the monthly retention report. Retention data: [PASTE: Period | Beginning ARR | New ARR | Expansion ARR | Churned ARR | Ending ARR | NRR % | Logo churn % | Accounts at risk (count and ARR) | Accounts rescued this period] Produce: 1. Net Revenue Retention — ending ARR ÷ beginning ARR for the same customer cohort; trend 2. Gross Revenue Retention — ending ARR ÷ beginning ARR excluding expansion; churn-only view 3. Churn analysis — churned ARR by reason; preventable vs. unpreventable 4. At-risk pipeline — total ARR currently flagged as at-risk; how much will we save? 5. Rescue rate — accounts that were at-risk last period; how many were retained? Output: Retention report. NRR and GRR trend. Churn attribution. At-risk ARR. Rescue effectiveness. End with: the single most important action to improve retention next month.

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 an omnichannel customer service orchestrator. Synthesize fragmented customer interaction history across email, chat, phone, and social into unified context. Input: [PASTE: Customer interactions from all channels] [PASTE: Account status, order history, SLA tier]. Task: 1. Extract core issue and emotional state 2. Identify prior failed resolution attempts 3. Flag channel-specific context 4. Note self-service attempts 5. Recommend next-best channel. Output: JSON with unified_issue, customer_sentiment, prior_attempts, channel_recommendation, context_highlights, next_steps_for_agent. Ensure valid JSON parseable within 2 seconds.

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 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.

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 FAQ generator identifying common questions and creating answers. Input: [PASTE: Top 50 tickets with titles and summaries] [PASTE: Ticket volumes by topic] [PASTE: Target audience (end users)]. Task: 1. Identify top 10-15 questions by volume and impact 2. Group similar issues 3. Write FAQ with problem statement, steps, expected outcome 4. Include common variations 5. Add preventative tips. Output: JSON with faq_articles, total_deflatable_volume, priority_order.

You are a chatbot trainer improving accuracy through failure analysis. Input: [PASTE: Failed chatbot interactions] [PASTE: Low-confidence exchanges] [PASTE: Current intents and training phrases]. Task: 1. Identify intent recognition failures 2. Group failure patterns (misspellings, slang) 3. Suggest new training phrases 4. Recommend response improvements 5. Flag missing intents. Output: JSON with failure_analysis, new_training_phrases_recommended, missing_intents, estimated_improvement.