35 ChatGPT Prompts for Customer Support Representatives (Resolve Faster, Respond Better)

Write a first response to a customer complaint about [issue: e.g., delayed shipment / billing error / product not working / rude experience with staff]. The customer's tone is: [frustrated / upset / neutral / threatening]. Our response should: acknowledge the issue with empathy, apologize appropriately, explain what we know about the situation, and state the next concrete step. Brand voice: [describe: warm / professional / casual].

Write an apology email to a customer for [what went wrong: service outage / wrong item shipped / billing mistake / wait time]. The apology should: be direct and genuine (not corporate), acknowledge the specific inconvenience, explain briefly what happened (if appropriate), state what we're doing to fix it, and offer a resolution [describe: refund / credit / replacement / expedited handling]. Avoid excessive hedging.

Write a customer-friendly response explaining our refund policy to a customer who is asking for a refund outside our standard policy window. The situation: [describe briefly]. Our policy: [describe in plain terms]. The response should: be honest about the policy, acknowledge why the customer might feel the policy is unfair, and either explain a one-time exception or offer an alternative resolution. Tone: empathetic, not robotic.

Write a response explaining [complex technical or process issue] to a customer who is not technical. The issue is: [describe what happened]. The response should: explain what happened in plain language, avoid jargon, be transparent about the root cause (to the extent we can share), and give a clear timeline or next step. Tone: clear and reassuring.

Write a response declining a customer's request for [describe: a feature that doesn't exist / a refund beyond our policy / a discount we can't offer / access they're not entitled to]. The decline should: be direct without being cold, explain the reason briefly (without over-explaining), acknowledge their frustration, and offer an alternative or workaround if one exists. Avoid "unfortunately" as the opening word.

Write a response to a customer who is visibly angry in their message — using aggressive language or all caps. The underlying issue: [describe]. The response should: not match the emotional energy, acknowledge their frustration specifically, avoid defensive language, and redirect toward solving the problem. Tone: calm, professional, and genuinely caring about the outcome.

Write a response to a customer who says they are going to cancel or take their business elsewhere if we don't resolve [issue]. The response should: take the threat seriously without panicking, acknowledge the frustration, make a concrete offer to resolve the situation, and give them a clear path to staying. Don't be sycophantic — be direct and solution-focused.

Write a response to a customer who has contacted us multiple times about the same unresolved issue and is now escalating their frustration. The history: [describe what's happened so far]. The response should: acknowledge the repeated contact specifically (not generically), take ownership of the failure to resolve sooner, and commit to a definitive action with a clear timeline.

Write a response to a customer making a request that crosses a reasonable boundary — [e.g., demanding a personal employee's contact information / requesting special treatment that would be unfair to other customers / making an inappropriate demand]. The response should: maintain a professional and respectful tone, decline clearly without sounding dismissive, and redirect to what we can offer.

Write a de-escalation script for a phone support rep dealing with a customer who is raising their voice and not letting the rep speak. The script should include: an opening interruption technique, an empathy statement, a redirect to problem-solving, and a clear path to resolution. Format as a spoken script with stage directions.

Write an FAQ article for our help center on the topic: [topic: e.g., how to reset your password / how billing works / what happens when your subscription expires / how to initiate a return]. Include: 5–7 common questions with clear, concise answers. Each answer should be under 100 words. Tone: helpful, direct, and plain-language. Format for a help center article.

Write a step-by-step tutorial for [task: e.g., setting up an account / connecting a third-party integration / updating payment information]. Target audience: a customer with no technical background. Include: numbered steps, what to expect at each step, common failure points and how to handle them, and a "you're done" confirmation step. Keep sentences short.

Write a troubleshooting guide for customers experiencing [issue: e.g., login problems / payment failures / app crashes / sync errors]. Format: problem statement, 5–7 numbered troubleshooting steps (in order of simplicity), a "if none of these work" escalation path, and a "what to tell us" section if they need to contact support.

Write a customer-facing release notes summary for a product update. Changes made: [list features added, bugs fixed, anything removed]. Audience: non-technical customers. Focus on: what changed from their perspective, how it benefits them, and anything they need to do. Keep it positive and clear. Under 300 words.

Write a customer-facing communication about a known issue or outage affecting [feature/service]. Currently known: [describe what happened and the status]. The message should: be transparent without over-explaining, acknowledge the impact on customers, give the expected resolution timeline (or state that it's unknown), and tell them what to do in the meantime.

Convert these rough customer interaction notes into a clean ticket summary: [paste notes]. Format: customer issue (1 sentence), steps taken, resolution or current status, and next action. This will be read by the next agent handling the ticket — make it scannable in under 20 seconds.

Write an escalation note for this ticket to pass to [Tier 2 / engineering / billing / management]. Include: customer summary (1 sentence), the issue in plain English, what has already been tried, why escalation is needed, and what the customer has been told so far. Make it easy for the receiving team to act without reading the full thread.

I've noticed a recurring issue in my support queue this week: [describe the pattern — what type of issue, how many customers, what they're saying]. Write a brief internal memo to my team lead or product team describing: what the pattern is, how many customers are affected (estimate), what the customer impact is, and what action might resolve it.

Write a canned response (macro) for the common support scenario: [describe scenario: e.g., "customer asking for an ETA on their order" / "customer wants to change subscription plan" / "customer forgot password"]. The macro should: be warm but efficient, have blanks I can personalize (mark with [brackets]), and avoid the 5 most common robotic phrases (e.g., "I hope this email finds you well," "I understand your frustration").

Help me write a root cause analysis (RCA) summary for a support issue that was reported by multiple customers. The issue: [describe]. Root cause identified: [describe]. Write the RCA summary for internal sharing with product/engineering teams: what happened, why it happened (not just the symptoms), how it was detected, what the customer impact was, and what's being done to prevent recurrence.

Create a quality assurance scorecard for evaluating customer support interactions. Include criteria for: greeting and tone, issue identification accuracy, solution quality, empathy and de-escalation, communication clarity, response time/efficiency, and documentation. Each criterion should have a 1–4 rating scale with behavioral anchors. Include a comment field for each.

Help me analyze and summarize these customer satisfaction survey responses: [paste anonymized responses or describe themes]. Identify: top strengths (what customers consistently praise), top friction points (what they consistently criticize), any surprising patterns, and 3 actionable recommendations for the support team based on the data.

Create a weekly self-assessment framework for a customer support representative. Include: key performance metrics to review (CSAT, resolution rate, first-contact resolution, AHT), behavioral reflection questions (what interactions went well / what felt off), a skill gap identifier, and an action item for the week. Format as a 10-minute weekly ritual.

Write a guide for a team lead conducting a 1:1 coaching session with a support rep who received a low CSAT score on [type of interaction: e.g., refund denial / technical escalation / billing dispute]. Include: how to open the conversation without blame, specific questions to ask, how to review the interaction together, and how to close with a concrete improvement action.

Create a 2-week onboarding checklist for a new customer support representative. Week 1: product familiarization, tool access, shadowing, reading SOPs. Week 2: supervised handling, first solo interactions, feedback sessions. Include: specific activities, responsible parties, and checkpoints for both the new hire and their manager.

Create a weekly team meeting agenda for a customer support team. Include: wins and recognition (5 min), top issues from the past week (10 min), policy or product update (10 min), skill-building topic (10 min), and open Q&A (5 min). The goal: team cohesion, knowledge sharing, and issue awareness — not just status reporting.

Write a shift handoff notes template for a support team with overlapping shifts. Include: open ticket summary (priority/status), any ongoing escalations, known product issues or outages active right now, team capacity notes, and one "heads up" for the incoming shift. Format: scannable in 2 minutes.

Write an internal document explaining our response time SLAs to new support reps. Include: what our SLA commitments are by channel (email / chat / phone), how priority levels are determined, what happens when an SLA breach is approaching, and how to escalate a high-urgency ticket outside normal flow.

Write a status page update for a [partial / full] service disruption affecting [feature/service]. The update should: describe the impact clearly, give the current status, estimate resolution time (or acknowledge it's unknown), and commit to a next update time. Tone: transparent and calm. Avoid corporate hedging.

I'm interviewing for a [Customer Support Rep / Senior Support Specialist / Support Team Lead] role. Generate 10 behavioral interview questions I should expect, 3 scenario-based questions, and the key frameworks to demonstrate (e.g., STAR method for situations, empathy-first de-escalation, metrics awareness). Help me prepare — don't script my answers.

I want to improve my CSAT score over the next 30 days. My current score: [X]. The common negative feedback themes: [describe]. Create a 30-day improvement plan with: specific behavioral changes to make, response patterns to avoid, one skill to practice each week, and how to self-assess weekly progress.

Write a short pitch for why I should be promoted to Team Lead. My experience: [describe — years, ticket volume, CSAT, any projects or improvements I've led]. The pitch should highlight: track record, leadership behaviors I've already demonstrated, specific contributions to the team, and what I'd bring to the role. Keep it to 1 page. I'll adapt for the conversation.

I want to develop [skill: technical writing / data analysis / project management / customer success] skills alongside my support role for career growth. My current experience: [describe]. Create a 90-day skill-building plan that fits within a 30-minute daily commitment: resources, exercises, and a milestone portfolio project.

Create a set of 5 practice scenarios for building customer empathy as a support rep. For each scenario: describe the customer situation and emotional state, give the rep a starting script, and include a reflection question about what the customer is really experiencing underneath the surface complaint. Format for team training or self-practice.

Write a genuine thank-you message to send to a customer who had a difficult experience but was patient and cooperative throughout the resolution process. The situation: [describe briefly]. The message should: acknowledge their patience specifically, thank them for their loyalty, and close with something that makes them feel valued — not just a generic closing. Under 100 words.