How to Use Claude for Customer Service
(Without Losing the Human Touch)

I need to build a response library for our most common support questions. Here's the question: "[Customer question — e.g. 'How do I cancel my subscription?']" Our policy: [describe the actual policy in plain language] Our tone: [e.g. warm but direct, no corporate speak, first-person singular] What customers usually feel when they ask this: [frustrated / confused / just exploring] Write three versions of a response: 1. A short version (2–3 sentences) for email or chat 2. A longer version with step-by-step instructions for a help article 3. A version for when the customer sounds frustrated or is threatening to churn For each, flag anything I should double-check for policy accuracy.

I need to respond to a complaint from a customer who is [angry / threatening to leave / publicly frustrated]. Here's their message: "[Paste customer message]" Context: - What actually went wrong: [brief description] - Whether we're at fault: [yes / partially / they misunderstood] - What we can offer: [refund / credit / fix / explanation] - What we can't offer: [any limits] Write a response that: 1. Opens by acknowledging how they feel (don't start with "I'm sorry for the inconvenience") 2. Takes responsibility for what's ours to own — nothing more 3. Explains what happened in plain language (not excuses) 4. Offers the specific resolution we're providing 5. Closes with a clear next step Tone: direct, human, calm. No corporate filler. Under 200 words.

Write a 5-email onboarding sequence for new customers of [product/service]. Here's what they need to do to get value quickly: Step 1 (Day 0): [first action they should take] Step 2 (Day 2): [second milestone] Step 3 (Day 5): [key feature or habit to establish] Step 4 (Day 10): [social proof or advanced feature] Step 5 (Day 14): [check-in / success moment] Customer profile: [who they are, what they bought, what success looks like for them] Common reasons people don't activate: [list 2–3] Our tone: [conversational / professional / etc.] For each email: subject line, preview text, body (under 150 words), one clear CTA. No filler. Write like a helpful colleague, not a marketing department.

Write a help center article for this topic: "[Feature or process name]" Here are my rough notes on how it works: [Paste bullet points, notes, or a rough explanation] Who's reading this: a customer who [describe their situation — e.g. "just ran into an error" or "is setting this up for the first time"] What they want to accomplish: [goal] Common mistakes or points of confusion: [list them] Format: - H1 title (clear, specific — what they're trying to do, not what the feature is called) - 1-sentence intro that tells them what this article covers - Numbered steps where order matters, bullets where it doesn't - A "common issues" section at the bottom - Under 400 words Write in plain English. If something needs a screenshot, flag it with [SCREENSHOT: description].

Here is a summary of support tickets from this week: [Paste ticket list, categories, or raw ticket text — even messy is fine] Analyze this and give me: 1. The top 5 issue categories by volume (with rough counts or percentages) 2. For each category: what's causing it (product bug / user confusion / policy gap / one-off) 3. Which issues are likely to repeat and should be addressed at the root 4. Which issues could be deflected with a better FAQ or help article 5. Any single issue that seems like a signal of a bigger problem worth flagging Format as a weekly support summary I can share with the product and ops team. Plain language, no jargon.

Write a response explaining to a customer why their request falls outside our policy. Here's the situation: Customer request: [what they asked for — e.g. refund outside the return window] Our policy: [the actual policy, verbatim if you have it] Why we're declining: [the specific reason] What we can offer instead (if anything): [alternative or goodwill gesture] Customer tone: [frustrated / understanding / threatening / confused] Write a response that: - Acknowledges what they asked for - Explains the policy clearly without hiding behind it - Offers the alternative (if any) as a genuine option, not a consolation prize - Closes the loop without leaving them hanging Keep it under 150 words. No "unfortunately" as the first word. Don't apologize for the policy existing — just explain it.

Write a 3-email win-back sequence for customers who cancelled [product/service]. Here's the context: Main reasons they cancelled: [list 2–3 from exit surveys or support notes] What's changed since they left: [product updates / pricing / features / team] What we can offer to win them back: [discount / extended trial / free onboarding / etc.] How long they were customers: [short-term / long-term] Our tone: [honest and direct — not desperate] Email 1 (1 week after churn): acknowledge they left, don't oversell — ask what went wrong Email 2 (3 weeks after): share what's changed that addresses their likely reason for leaving Email 3 (6 weeks after): make the specific offer with a clear expiration Each email: under 120 words, real subject line, one CTA. Don't start with "We noticed you left." Write like a person, not a retention team.