20 ChatGPT Prompts for Customer Service Teams (Copy-Paste Ready)
Customer service teams spend hours drafting the same emails over and over — apology responses, refund denials, escalation paths. ChatGPT can generate a polished draft in seconds if you give it the right prompt. Here are 20 ready-to-run prompts organized by the situations your team faces every day.
Every support team has a stack of ticket types that show up on repeat: the angry refund email, the late-delivery apology, the policy-exception negotiation. Writing each one from scratch is slow. Writing them quickly produces inconsistent tone. And inconsistent tone erodes customer trust over time. ChatGPT solves the drafting problem — but only when you give it a prompt that assigns a role, specifies the output format, and fills in the relevant context. Vague prompts produce vague drafts that need as much editing as writing from scratch. The 20 prompts below are built to be specific: role-assigned, outcome-focused, and bracket-formatted so your team can fill in the details and fire.
Section 1: Handling Complaints & Apologies
The most common ticket types — and the ones where tone matters most. These five prompts cover the situations that show up in every support queue, from frustrated customers to service outages.
1. Frustrated Customer Response
Acknowledges the customer's frustration, takes ownership, and maps out the next step — without over-apologizing or making promises you can't keep.
Act as a senior customer service representative for a [COMPANY TYPE, e.g. e-commerce retailer / SaaS platform / subscription box brand].
Write a professional email response to a frustrated customer who is unhappy about [ISSUE, e.g. a delayed order / a broken product / poor service experience].
Customer's name: [CUSTOMER NAME]
What happened: [BRIEF DESCRIPTION OF THE ISSUE]
What we can do to resolve it: [RESOLUTION OPTION — refund / replacement / credit / escalation]
Output format:
- Subject line
- Opening: acknowledge the frustration directly (no generic "sorry for the inconvenience")
- Body: brief explanation if appropriate, clear ownership statement
- Resolution: what we're doing right now to fix this
- Closing: next step and response timeframe
- Tone: empathetic, professional, no corporate jargon
- Length: under 150 words2. Service Outage Apology
Communicates a service outage with transparency and a clear resolution timeline — the kind of message that turns a bad experience into a trust moment.
Act as a senior customer service representative for a [COMPANY TYPE, e.g. SaaS platform / hosting provider / app-based service].
Write a customer-facing email about a [OUTAGE TYPE, e.g. planned maintenance / unexpected downtime / data sync issue] that affected [AFFECTED FEATURE OR SERVICE].
Outage window: [START TIME – END TIME or "ongoing"]
What was affected: [LIST AFFECTED FEATURES]
Root cause (if shareable): [BRIEF EXPLANATION OR "under investigation"]
Current status: [Resolved / In progress / Monitoring]
Next update: [DATE/TIME OR "when resolved"]
Output format:
- Subject line (clear, factual — not alarming)
- Status summary (2–3 sentences)
- What customers should do in the meantime
- What we're doing to prevent recurrence
- Apology line (sincere, not excessive)
- Tone: transparent, calm, accountable3. Late Delivery Apology
Addresses a delayed shipment with empathy and a clear resolution path — the response that keeps a customer instead of losing one.
Act as a senior customer service representative for a [COMPANY TYPE, e.g. e-commerce brand / subscription service / retail store].
Write an email response to a customer whose order [ORDER NUMBER] has not arrived by the expected delivery date of [EXPECTED DATE].
Customer name: [NAME]
Original order date: [DATE]
Current status: [e.g. in transit / delayed at carrier / lost]
New estimated delivery: [DATE OR "we're investigating"]
What we're offering: [e.g. expedited reshipment / refund / store credit / discount on next order]
Output format:
- Subject line
- Apology with specific acknowledgment (not generic)
- Status update on their order
- What we're doing to resolve it
- What they can expect next and when
- Tone: warm, proactive, solution-focused
- Length: under 130 words4. Billing Error Acknowledgment
Handles a billing discrepancy with clarity and accountability — covering the issue, the fix, and the timeline without triggering more frustration.
Act as a senior customer service representative for a [COMPANY TYPE].
Write an email response to a customer who was incorrectly charged [AMOUNT] on [DATE] for [REASON, e.g. duplicate charge / wrong plan tier / unexpected renewal].
Customer name: [NAME]
Charge amount: [AMOUNT]
Date of charge: [DATE]
Reason for error: [BRIEF EXPLANATION]
Resolution: [e.g. full refund issued / credit applied / corrected invoice sent]
Timeline: [e.g. 3–5 business days to reflect / immediate]
Output format:
- Subject line: acknowledge the error directly
- What happened (plain language, no blame-shifting)
- What we've done to fix it
- When they'll see the correction
- What to do if they have further questions
- Tone: straightforward, accountable, no over-explaining5. Product Defect Response
Responds to a reported product defect or quality issue — validating the customer's experience and presenting the clearest path to resolution.
Act as a senior customer service representative for a [COMPANY TYPE, e.g. physical product brand / electronics retailer / food and beverage company].
Write an email response to a customer who reported a defect or quality issue with [PRODUCT NAME].
Customer name: [NAME]
Order number: [ORDER NUMBER]
Reported issue: [DESCRIBE THE DEFECT — e.g. item arrived broken / wrong color / missing pieces]
Verification needed: [Yes — ask for photo / No — take their word for it]
Resolution we're offering: [e.g. full replacement / refund / store credit]
Output format:
- Subject line
- Empathetic opening (acknowledge the defect, not just the inconvenience)
- Clear resolution offer with no hoops
- Any next step required from the customer (photo, return, nothing)
- Timeline for resolution
- Tone: apologetic but efficient, not defensiveSection 2: Refunds, Returns & Policy Questions
Policy communications need to be clear, firm, and human — all at once. These five prompts handle every refund and return scenario, including the uncomfortable ones.
6. Refund Request Approval
Approves a refund request cleanly and professionally — communicating what happens next without unnecessary friction.
Act as a senior customer service representative for a [COMPANY TYPE].
Write an email confirming a refund has been approved for customer [NAME].
Order number: [ORDER NUMBER]
Product/service: [NAME]
Refund amount: [AMOUNT]
Refund method: [Original payment method / store credit / check]
Processing time: [e.g. 5–7 business days]
Reason for refund: [e.g. customer request / defective item / service cancellation]
Output format:
- Subject line: confirm the refund clearly
- Confirmation of what's being refunded and how much
- Method and timeline
- Any action required from the customer (return item / nothing needed)
- Brief, warm closing
- Tone: efficient, reassuring, no excessive apology
- Length: under 120 words7. Refund Denial with Empathy
Declines a refund request without being dismissive — explaining the policy clearly while acknowledging the customer's perspective.
Act as a senior customer service representative for a [COMPANY TYPE].
Write an email declining a refund request from customer [NAME] for [PRODUCT/SERVICE].
Order number: [ORDER NUMBER]
Reason for denial: [e.g. outside return window / digital product policy / used/opened item]
Policy reference: [e.g. our 30-day return policy / terms of service section X]
Alternative we're offering instead: [e.g. store credit / partial refund / free exchange]
Output format:
- Subject line (neutral, not adversarial)
- Acknowledge their request and frustration without validating the refund
- Explain the policy clearly in plain language (no legalese)
- Offer the alternative with genuine framing
- Provide a way to escalate if they still disagree
- Tone: firm but empathetic, never dismissive
- Length: under 150 wordsSection 3: Escalation & De-escalation
Escalations handled poorly become public complaints. These prompts give your team the language to de-escalate and close the loop cleanly.
11. Escalating to a Manager
Acknowledges an escalation request professionally and sets expectations for what happens next — without making the customer feel passed off.
Act as a senior customer service representative for a [COMPANY TYPE].
Write an email to customer [NAME] confirming their request to escalate has been received and is being transferred to a senior team member or manager.
Issue being escalated: [BRIEF DESCRIPTION]
Who they'll hear from: [e.g. our Customer Success Manager / senior support specialist]
Timeline: [e.g. within 24 hours / by end of business today]
What to include: any case details you've already provided
Output format:
- Subject line acknowledging the escalation
- Confirmation it's been escalated (specific, not vague)
- Who owns it now and when they'll be in touch
- Case reference number if applicable
- Brief apology for the experience requiring escalation
- Tone: accountable, reassuring, professionalGet all 20 prompts
Unlock the full list — plus 54 automation templates including full support workflow chains — for just $29
Unlock Now — $29Instant download · Digital product — no shipping or physical delivery.