Handle Every Ticket Faster — Without Sounding Like a Robot

Write an onboarding welcome email for new customers who just signed up for [PRODUCT/SERVICE NAME] by [COMPANY NAME]. The customer's first name will be inserted dynamically as [FIRST NAME]. Context about the product: [BRIEF DESCRIPTION — what it does and who it helps] Key action we want them to take in the first 24 hours: [ONE SPECIFIC ACTION] Secondary resources available: [HELP CENTER / VIDEO TUTORIAL / ONBOARDING CALL / COMMUNITY] The email should: 1. Open with a warm, human welcome that references the specific value they signed up for (not generic excitement) 2. Set expectations: what happens next, what they can do right now 3. Highlight ONE primary action with a clear CTA button label 4. Provide 2-3 quick-start resources without overwhelming them 5. Give them a direct reply address or support option so they know help is available 6. Close with a short personal sign-off from a real team member (use [SENDER NAME] placeholder) Subject line: Write 3 options with different angles (value, action, curiosity). Tone: warm, confident, and focused. Under 250 words in the body.

Write a subscription renewal email for [COMPANY NAME] to send to customers whose subscription is renewing in [X DAYS]. The product is [PRODUCT NAME] and the renewal amount is [AMOUNT] per [BILLING CYCLE]. The email should: 1. State clearly that their subscription is renewing on [DATE] for [AMOUNT] — no surprises 2. Remind them of the value they have received: [KEY METRIC IF AVAILABLE: e.g., "You have completed 12 tutorials", "You have used X feature Y times"] 3. Highlight any new features or improvements added since their last renewal (2-3 bullets max) 4. Provide a direct link to manage billing or cancel if they choose — do not bury this 5. Include a soft upsell to a higher plan if applicable: [PLAN NAME] with [KEY BENEFIT] 6. Give a support contact for billing questions Subject line: Write 2 options — one that leads with the renewal notice, one that leads with the value reminder. Tone: transparent, confident, and low-pressure. Customers who feel respected renew. Customers who feel surprised churn and complain. Length: under 200 words.

Write a churn prevention email for [COMPANY NAME] to send to a customer showing signs of disengagement. Churn signal: [DESCRIBE TRIGGER: e.g., has not logged in for 21 days, canceled but still in trial, downgraded plan, opened cancellation page but did not complete]. Product: [PRODUCT NAME] Customer segment: [TYPE OF CUSTOMER: small business, freelancer, enterprise, etc.] The email should: 1. Open with an observation, not a guilt trip: acknowledge they have been less active without making them feel bad 2. Ask a direct question: "Is there something specific that got in the way?" — create a reply-to opportunity 3. Offer one concrete piece of value they may have missed (a feature, a use case, a shortcut) 4. Include a clear, low-friction way to re-engage (one-click action or short call offer) 5. Offer a genuine incentive if appropriate: [DISCOUNT / EXTENDED TRIAL / FREE MIGRATION HELP] 6. Give a clear opt-out: if they have decided to leave, make cancellation easy to find Subject line: 3 options — one direct, one curious, one benefit-led. Tone: conversational, not desperate. Length: under 200 words.

Write a feedback request email for [COMPANY NAME] to send to customers [X DAYS] after [TRIGGER: purchase, onboarding completion, support resolution, feature use]. The goal is to collect genuine feedback that we can use to improve. Product: [PRODUCT NAME] What we most want to learn: [E.g., was onboarding clear? did the support interaction resolve their issue? are they happy with the new feature?] The email should: 1. State clearly what you are asking for and why you are asking at this specific moment 2. Set the time expectation: "This takes 2 minutes" 3. Ask ONE primary question in the email body itself (not buried in a survey) — make it easy to reply directly 4. Link to a longer survey for those who want to give more detailed feedback (optional, not required) 5. Assure them that responses are read and acted on — give a concrete example if possible 6. Sign off from a real person, not "The [Company] Team" Subject line: 2 options. Both should feel personal, not automated. Tone: direct, brief, and genuinely curious. Under 150 words in the body.

Write follow-up emails for three NPS response segments for [COMPANY NAME] after customers complete our NPS survey for [PRODUCT NAME]. Write one email for each segment: 1. Promoters (score 9-10): Thank them, invite them to [LEAVE A REVIEW / REFER A FRIEND / JOIN A CASE STUDY]. Make it feel like a VIP acknowledgment, not a marketing ask. 2. Passives (score 7-8): Acknowledge their moderate satisfaction, ask what one thing would make their experience better, and offer a direct path to discuss it (reply to email or schedule a call). 3. Detractors (score 0-6): Acknowledge that they are not satisfied, apologize for falling short, and ask for a brief conversation to understand what went wrong. Do not be defensive. Make it easy to say yes to a call. For each email: - Subject line: personalized to the score segment - Body: under 150 words - One clear CTA - Personal sign-off from [TEAM MEMBER NAME] Tone: the promoter email is warm and celebratory. The passive email is curious and collaborative. The detractor email is humble and action-oriented.

Write a win-back email for [COMPANY NAME] targeting customers who canceled or churned [X WEEKS/MONTHS] ago. The product is [PRODUCT NAME]. Reason for churn if known: [PRICE / MISSING FEATURE / SWITCHED TO COMPETITOR / CIRCUMSTANCES CHANGED / UNKNOWN] What has changed since they left: [NEW FEATURES / PRICING CHANGE / IMPROVED ONBOARDING / NEW CONTENT / BUG FIXES RELEVANT TO THEIR ISSUE] The email should: 1. Open by acknowledging that they left — do not pretend they are still active 2. Reference what may have caused them to leave (if known) and what is different now 3. Present a specific, time-limited incentive to return: [OFFER: e.g., 2 months free, 40% off first month back, free migration help] 4. Remove friction: tell them they can [RESTORE THEIR ACCOUNT / START FRESH / KEEP THEIR DATA] 5. Include a single clear CTA with an expiration: "Offer expires [DATE]" 6. Make it easy to opt out of win-back emails permanently Subject line: 2 options. Make them feel like the email was sent by a person who noticed they were gone. Tone: honest, direct, and low-pressure. Under 200 words.

Write a new customer service agent training manual outline for [COMPANY NAME]'s support team. The team handles support for [PRODUCT/SERVICE TYPE] via [CHANNELS: email, live chat, phone, social media]. New agents are expected to handle tickets independently after [X-DAY ONBOARDING PERIOD]. The manual should cover: 1. Our support philosophy and customer experience principles (3-5 core values with what they look like in practice) 2. Product knowledge overview: the 10 most common customer issues and how to resolve each 3. Communication standards: tone of voice guidelines, what to say, what never to say 4. Ticket handling workflow: from first response to resolution and close 5. Escalation matrix: what to escalate, to whom, and how 6. Tools and systems overview: [LIST YOUR TOOLS — helpdesk, CRM, etc.] with a summary of each 7. Quality assurance: how responses are reviewed and how agents receive feedback 8. Self-service resources: where to find answers when unsure For each section, include a short "what good looks like" example. Format as a structured outline an agent can bookmark and reference during their first 30 days.

Create a quality assurance (QA) rubric for reviewing customer service interactions at [COMPANY NAME]. This rubric will be used by QA reviewers to score [CHANNEL: email responses / live chat / phone calls]. The rubric should include 6-8 evaluation criteria, each scored on a [1-5 / 1-10] scale. For each criterion, provide: - The criterion name - What it measures - What a top score looks like (describe it in concrete, observable terms) - What a failing score looks like (equally concrete) - Coaching notes: one tip a manager can give to help an agent improve on this criterion Suggested criteria (customize as needed): Greeting and tone, Issue understanding and accuracy, Solution quality, Policy compliance, Empathy and personalization, Response efficiency, Grammar and professionalism, Customer experience close. Also include: - A total score calculation method - Thresholds: what score triggers coaching, what triggers retraining, what earns recognition - A calibration note for reviewers to ensure consistent scoring across your team

Write a customer service call script for [COMPANY NAME] support agents handling [TYPE OF CALL: inbound support call / outbound renewal call / escalation callback / cancellation save call]. Common scenarios this script will cover: - [SCENARIO 1: e.g., customer calling about an unresolved ticket] - [SCENARIO 2: e.g., customer calling to cancel] - [SCENARIO 3: e.g., customer calling about a billing issue] The script should include: 1. Opening: greeting, company introduction, and how to identify the caller 2. Discovery: 3-4 diagnostic questions to understand the issue before jumping to solutions 3. Resolution branches: a decision tree for the top 3 scenarios (if X, say Y; if Z, say W) 4. Objection handling: 5 common objections and scripted responses that do not sound scripted 5. Hold language: what to say when placing someone on hold and when returning 6. Escalation handoff: exact language to use when transferring to a senior agent 7. Closing: confirmation of resolution, next steps, and sign-off Format: script lines in quotes, stage directions in brackets. Write as if for an agent who is new but confident.

Create a set of empathy training scenarios for customer service agents at [COMPANY NAME]. These will be used in role-play exercises during onboarding or team training sessions. Generate 5 scenarios of increasing emotional difficulty: Scenario 1 (Low difficulty): A frustrated customer whose package arrived late but intact. They are mildly annoyed but receptive. Scenario 2 (Medium): A customer who has been transferred three times for the same issue and is losing patience. Scenario 3 (Medium-high): A small business owner whose account was incorrectly suspended during their busiest season, causing lost revenue. Scenario 4 (High): A customer who is grieving a family loss and needs to cancel or modify a subscription under difficult emotional circumstances. Scenario 5 (Very high): A customer who has experienced repeated failures and is threatening to go public on social media. For each scenario, provide: - A customer opening statement (what the agent hears first) - The emotional state beneath the words - 2 wrong agent responses and why they make things worse - 2 right agent responses and what they accomplish emotionally - A debrief question for the trainer to ask the group

Create a product knowledge assessment for new customer service agents at [COMPANY NAME] who support [PRODUCT/SERVICE NAME]. The quiz should test: 1. Core product features and what they do 2. Pricing plans and what is included in each 3. Integrations and compatibility 4. Common error messages and their resolutions 5. Escalation procedures and when to use them 6. Policy knowledge: refunds, cancellations, SLAs, data privacy basics Format: 20 questions total across these categories. Include: - 10 multiple-choice questions (4 options each, one correct answer) - 5 true/false questions - 3 short-answer questions ("What would you say to a customer who...") - 2 scenario-based questions with a 3-4 sentence written response For each question, provide the correct answer and a brief explanation of why it matters in a real customer interaction. Also suggest: a passing score threshold, what happens if an agent fails (retake process), and how often the quiz should be updated as the product evolves.

Build an escalation decision tree for the customer service team at [COMPANY NAME] supporting [PRODUCT/SERVICE TYPE]. The team has the following tiers: [TIER 1: frontline agents], [TIER 2: senior support], [TIER 3: engineering / legal / account management]. The decision tree should answer the question: "Should I escalate this ticket, and if so, to whom?" Cover these escalation triggers: 1. Technical issues beyond Tier 1 resolution capability 2. Billing disputes above [THRESHOLD AMOUNT] 3. Requests for data deletion or privacy-related requests 4. Legal language or threats in customer communication 5. VIP or enterprise account complaints 6. Social media crises or PR risk situations 7. Repeat contacts on the same unresolved issue 8. Safety or urgent business-impact situations For each trigger, specify: - Who receives the escalation - What information must be included in the escalation note - Target response time from the receiving tier - Whether the customer should be notified and what to tell them Format as a flowchart-style outline an agent can scan in under 30 seconds while on a live interaction.

Help me analyze customer support ticket data for [COMPANY NAME] supporting [PRODUCT NAME]. Here is a summary of our ticket volume and categories for the past [TIME PERIOD: week / month / quarter]: Total tickets: [NUMBER] Breakdown by category: - [Category 1]: [NUMBER] tickets ([PERCENTAGE]%) - [Category 2]: [NUMBER] tickets ([PERCENTAGE]%) - [Category 3]: [NUMBER] tickets ([PERCENTAGE]%) - [Category 4]: [NUMBER] tickets ([PERCENTAGE]%) - [Other]: [NUMBER] tickets ([PERCENTAGE]%) Average first response time: [TIME] Average resolution time: [TIME] CSAT score: [SCORE] Top agents by volume: [LIST] Analyze this data and provide: 1. The top 3 insights a support leader should act on this week 2. Which ticket category represents the highest leverage for reduction (and how to reduce it) 3. Any concerning trends to investigate further 4. One process change that would have the biggest impact on resolution time 5. A 3-sentence executive summary suitable for sharing with leadership

Create a CSAT improvement plan for [COMPANY NAME]'s customer support team. Our current CSAT is [SCORE]% and our target is [TARGET SCORE]% within [TIMEFRAME]. Here is the breakdown of our low CSAT feedback: - Common themes in negative comments: [LIST 3-5 THEMES] - Ticket categories with lowest CSAT: [LIST] - Agents with lowest CSAT scores: [OPTIONAL — describe patterns, not names] - Average resolution time for low-CSAT tickets: [TIME] Create a plan that includes: 1. Root cause analysis for each negative theme 2. Three quick wins we can implement in the next 2 weeks 3. Three systemic improvements that take 1-3 months 4. Agent coaching focus areas based on the patterns 5. How to measure progress weekly (leading indicators, not just lagging CSAT) 6. What to communicate to agents about the improvement initiative to build buy-in, not defensiveness Format as an actionable plan, not a general framework. Be specific about what to do, who should do it, and in what order.

Help me optimize first response time (FRT) and average resolution time (ART) for [COMPANY NAME]'s support team. Current metrics: - First response time: [CURRENT] vs. target [TARGET] - Average resolution time: [CURRENT] vs. target [TARGET] - Peak ticket hours: [TIME RANGES] - Team size: [NUMBER OF AGENTS] - Channels: [EMAIL / LIVE CHAT / PHONE / ALL] - Current SLA commitments: [DESCRIBE] Analyze these constraints and provide: 1. The most likely causes of FRT exceeding target (be specific, not generic) 2. A staffing coverage analysis: are we over- or under-resourced at peak hours 3. 5 specific process changes to reduce FRT without adding headcount 4. Template or automation opportunities that would reduce handle time 5. How to triage and prioritize tickets to ensure SLA compliance during high-volume periods 6. A 90-day roadmap to hit target FRT and ART with milestones at 30 and 60 days Prioritize recommendations that require no additional budget.

Generate a "Common Issues Report" template for [COMPANY NAME] to be shared across the support, product, and engineering teams on a [WEEKLY / MONTHLY] basis. The report will be built from support ticket data for [PRODUCT NAME]. The report template should include: 1. Executive summary (3 bullet points maximum): top issues, volume trend (up/down vs. last period), one critical item requiring immediate attention 2. Top 10 issues by volume: issue name, ticket count, trend (new / increasing / stable / decreasing), and who owns the resolution 3. Issues by impact severity: categorized as [Critical: blocks core workflow], [Major: significant friction], [Minor: cosmetic or edge case] 4. Issues introduced by recent product changes: flag any issue that spiked after a release 5. Issues pending engineering fix: status, expected resolution date, and customer communication status 6. Issues resolved this period: what was fixed and whether ticket volume dropped as expected 7. Cross-functional asks: specific requests for product, engineering, or docs teams Format as a template with [PLACEHOLDER] markers. It should take an analyst under 45 minutes to fill in each period.

Help me synthesize Voice of Customer (VoC) insights for [COMPANY NAME] from the following data sources: Data available: - CSAT survey responses with open-text comments: [PASTE A SAMPLE OF 10-20 COMMENTS, OR DESCRIBE THEMES] - NPS survey responses with detractor and passive comments - Support tickets tagged as feature requests - Social media mentions or reviews (summarize if you have them) Analyze this feedback and provide: 1. The top 5 recurring themes across all sources — what customers are consistently saying 2. The most emotionally charged feedback: what issues are generating the strongest negative or positive reactions 3. Unmet needs: what customers are asking for that we do not currently offer or communicate well 4. Quotes: pull the 3-5 most representative customer quotes that capture the key themes 5. Product implications: what 3 changes would address the most feedback with the least development effort 6. How to present these findings to leadership in a 5-minute briefing Format the output as a shareable one-page brief with section headers. Use the customer quotes as evidence, not as decoration.