Customer Service Response Drafting
Faster replies that still sound like a person read the ticket
The goal isn’t to sound like a bot answered faster
Customers can tell when a reply is generic. The point of using Claude for support isn’t to auto-respond at scale with copy-paste answers — it’s to skip the blank page. You still read every ticket, you still make the actual decision (refund, replacement, escalation), and you still send the message yourself. Claude just gets you from “empty reply box” to “draft I mostly just need to check” in seconds instead of minutes.
The five situations that eat the most support time
| Situation | What the reply needs to do |
|---|---|
| Shipping delay | Acknowledge the wait, give a real update or timeframe, offer something if it’s badly delayed |
| Wrong/damaged item | Apologize without over-explaining, offer replacement or refund clearly, make next steps easy |
| Sizing/fit question (pre-purchase) | Answer directly, reference your size guide, reduce their uncertainty so they buy confidently |
| Return/refund request | State the policy clearly, avoid sounding defensive, keep the process simple |
| General “where is my stuff” check-in | Fast, factual, reassuring — doesn’t need much warmth, just clarity |
The pattern for a good support prompt
Give Claude the situation, the facts, the tone, and the specific resolution you’re offering — the same “facts first, format second” approach from Lesson 5 applies here too.
Draft a reply to a customer support ticket for my store.
SITUATION: Customer's order (a wool sweater, $85) arrived with a small
hole near the seam. They're upset but not aggressive — they just want
it fixed.
RESOLUTION I'M OFFERING: Free replacement, shipped today, they can
keep or donate the damaged one (not worth the return shipping cost).
TONE: Warm, apologetic without being groveling, confident — this is a
normal thing we handle well, not a crisis.
Keep it under 120 words. Sign off as "The Northfield Team."Because you stated the exact resolution, Claude isn’t guessing at what you’re willing to offer — it’s just finding the clearest, warmest way to say it.
Building a personal FAQ / macro library
Most stores see the same 10-15 questions repeatedly. Instead of drafting from scratch every time, build a short reference doc of your standard policies (shipping windows, return window, exchange process) and paste the relevant policy into your prompt so Claude never has to guess at details like your return window.
Reference: Our return window is 30 days from delivery, we cover
return shipping for defective items only, exchanges take 5-7 business
days once we receive the item.
Using this policy, draft a reply to: "I ordered the wrong size 3
weeks ago, can I still exchange it?"Warning: Never let Claude state a policy detail (return window, refund timeline, warranty length) that you haven’t explicitly provided — it will produce a plausible-sounding number if you don’t, and a wrong policy stated to a customer becomes a real commitment you may have to honor.
Matching tone to the customer’s tone
A frustrated, all-caps message and a polite, confused question both need replies — but not the same reply. Tell Claude how the customer came in so the response matches, rather than defaulting to the same even-keeled tone for every ticket.
The customer's message was short and clearly frustrated ("this is the
SECOND wrong order, unacceptable"). Draft a reply that leads with a
direct, sincere acknowledgment of the frustration before getting to
the resolution — don't sound falsely cheerful.What to always double-check before sending
- Order-specific details (order number, item name, dates) — Claude only knows what you told it
- Any policy number (days, dollar amounts, percentages)
- That the tone actually matches how upset or calm the customer sounded
- That you’re not promising something (expedited shipping, a specific date) you can’t actually guarantee
Key principle: A drafted reply is a first draft, not a send-ready message. The habit that matters most here is reading it once, fully, with the original ticket next to it, before it goes out.
Try it: Pull your last three “annoying to answer” support tickets. Draft replies using the facts-resolution-tone pattern above, and time how long it takes versus writing from scratch.