AI Customer Service Scripts: Handle Any Situation

Principles

The Customer Service Formula

Before you use the prompts, internalize these.

1. Acknowledge First, Solve Second

People want to feel heard before they want solutions. Start every response by validating their experience specifically, not generically.

2. Own What You Can

Take responsibility where appropriate. "We should have..." builds trust. Defensive responses escalate situations.

3. Be Specific About Next Steps

Vague promises frustrate people. "I'll look into this" is weak. "I'll have an answer for you by 3pm today" is strong.

4. Match Urgency, Not Emotion

If they're upset, respond quickly and thoroughly. But stay calm. Mirror their urgency, not their frustration.

Complaint Responses

When Things Go Wrong

Turn complaints into comebacks.

General Complaint Response Universal

Works for any complaint where something went wrong on your end.

Write a response to this customer complaint: [PASTE COMPLAINT] Guidelines: 1. Acknowledge their specific frustration (not generic "sorry for the inconvenience") 2. Take responsibility where appropriate 3. Explain briefly what happened (no excuses, just context) 4. State exactly what we'll do to fix it 5. Offer appropriate goodwill gesture if warranted 6. End with commitment to do better Tone: empathetic, professional, solution-focused. Don't be defensive or dismissive.

Angry Customer De-escalation High Priority

When they're really upset and using strong language.

Write a de-escalation response to this angry customer message: [PASTE MESSAGE] This customer is clearly very frustrated. My response must: 1. Not mirror their anger or get defensive 2. Acknowledge their frustration is valid (even if their approach isn't) 3. Focus on the underlying problem, not their tone 4. Offer a concrete path to resolution 5. Give them a direct contact (name/email) so they feel heard 6. Be brief - long responses feel like excuses when someone is angry Tone: calm, understanding, action-oriented. No corporate speak.

Refund Request Response Policy

When they want their money back.

Write a response to this refund request: [PASTE REQUEST] Context: - Our refund policy: [DESCRIBE POLICY] - This situation: [DOES IT QUALIFY? WHY/WHY NOT?] - What I'm willing to offer: [FULL REFUND / PARTIAL / CREDIT / NOTHING] If approving: Process quickly, confirm timeline, thank them If declining: Explain why clearly, offer alternatives, leave door open If partial/credit: Explain the reasoning, make it feel fair Don't be stingy with long-term customers. Don't be a pushover with serial refunders.

When AI Isn't Enough

Some situations need a human: legal threats, safety concerns, media involvement, or when the customer explicitly asks for a manager. Use AI for the first draft, but know when to escalate.

Proactive Communication

Before They Complain

Get ahead of problems.

Delay Notification Proactive

When something is going to be late.

Write a proactive notification email about a delay. What's delayed: [PRODUCT/SERVICE/DELIVERY] Original timeline: [WHEN IT WAS DUE] New timeline: [WHEN IT WILL ACTUALLY HAPPEN] Reason (honest): [WHY] What we're doing: [STEPS TO FIX/PREVENT] Rules: - Lead with the news, don't bury it - Be specific about new timeline - Offer something if appropriate (discount, upgrade, etc.) - Don't over-apologize (once is enough) - End with clear next steps

Service Issue Acknowledgment Proactive

When you discover a problem before customers do.

Write a proactive acknowledgment of a service issue we discovered. The issue: [WHAT HAPPENED] Who's affected: [WHICH CUSTOMERS] Impact: [WHAT IT MEANS FOR THEM] Status: [FIXED / BEING FIXED / INVESTIGATING] Resolution: [WHAT WE'RE DOING] Tone: transparent, confident, action-oriented. We're on top of this. No panic, no minimizing.

FAQ Response Generator Efficiency

Build your knowledge base faster.

Write FAQ responses for these common questions about [PRODUCT/SERVICE]: Questions: 1. [QUESTION 1] 2. [QUESTION 2] 3. [QUESTION 3] 4. [QUESTION 4] 5. [QUESTION 5] For each answer: - Lead with the direct answer (don't make them read a paragraph first) - Add context only if necessary - Include next steps if applicable - Keep under 100 words each - Use simple language (8th grade reading level) Tone: helpful, clear, no jargon.