Claude for Customer Service: Two Ways to Answer Faster

I’ve trained a lot of support reps, account managers, and inside sales people over the years, and the complaint is never really about the customers. It’s about the typing. The same dozen questions arrive every week, and every one of them still gets answered from a blank box, in a hurry, at 4:45 on a Friday.

That’s exactly where Claude for customer service work earns its keep. Not as a robot that talks to your customers — I don’t recommend that for most small teams — but as the thing that sits beside you and does the first draft, the summary, and the “what did we promise this person in March” lookup that nobody has time for.

Here are two setups you can build today. Neither one takes more than ten minutes, and you don’t have to attend anything to use them.

Set Up Claude for Customer Service Replies That Sound Like You

The reason most AI-written replies get deleted is that they sound like a press release. The fix isn’t a better prompt every single time — it’s a Project, so you stop re-explaining your company every morning.

In Claude, look at the left sidebar and click Projects, then New project. Give it a name like “Customer Replies.” Inside the project you’ll see Project knowledge — that’s the important part. Add three things to it:

• Your refund, shipping, or cancellation policy, pasted in as plain text.
• Ten to twenty of your own past replies that you were happy with. Real ones, with names and account numbers removed.
• A short list of house rules: “We never say ‘unfortunately.’ We always give a specific date, never ‘soon.’ We sign off with ‘Thanks — Tom.'”

Then set the project’s custom instructions to something like:

You are drafting replies for our support inbox. Match the tone of the sample replies in project knowledge. Always state a specific next step and a date. Never invent a policy — if the answer isn't in project knowledge, say so and flag it for a human. Keep replies under 150 words.

From then on, your daily work is just pasting the customer’s email into that project and typing Draft a reply. The output comes back already in your voice, already inside your policy, and usually needs one line changed instead of a full rewrite.

The gotcha: project knowledge is read fresh every single time, so an out-of-date policy document is worse than no document. If you change your return window from 30 days to 14, go update the file that day. Claude will quote the old number confidently and your customer will hold you to it.

Turn a Messy Email Thread Into a Two-Line Situation Brief

The other pile of work is the forty-message thread that lands on your desk with “can you take this one?” at the top. Reading it takes fifteen minutes. You don’t have fifteen minutes.

Copy the whole thread — oldest message to newest, quoted junk and all — paste it into Claude, and put this above it:

Below is a customer email thread. Give me: (1) the situation in two sentences, (2) a bullet list of every commitment we made, with who made it and the date, (3) what the customer is actually asking for right now, (4) anything we promised and have not delivered. Quote the exact line for each commitment. If something is unclear, list it under "Open questions" instead of guessing.

What comes back beats skimming, because the “quote the exact line” instruction forces the answer to point at real text instead of producing a vague summary. The unfulfilled-promises list is the one that saves you — that’s the thing that turns a routine ticket into an angry escalation when it gets missed.

Do this with a PDF or a Word attachment too. You can drag the file straight into the message box rather than copying text out of it.

The gotcha: the brief is only as complete as what you pasted. If half the story happened on a phone call or in a CRM note, Claude has no way to know that, and the summary will read as if the thread is the whole history. Add a line of your own context at the bottom — “we also called her on the 3rd and offered a credit” — before you hit send.

Plenty more on the calendar

If you want to see both of these built live, with questions answered as we go, I’m running Claude for Customer Facing Teams on Thursday, September 17. We’ll set up a support project from scratch, write reply templates that don’t sound automated, handle thread summaries and escalation briefs, and talk through what you should and shouldn’t put into an AI tool when customer data is involved.

The full current schedule is on the front page of PCWebinars.com, and new dates go up as they’re confirmed. Register for this one if the topic fits, or browse the rest — there’s usually something on Excel, Power BI, Copilot, or Claude within the next week or two.

About your trainer

I’m Tom Fragale. I’ve been a computer trainer and consultant for more than 30 years, and I’ve taught well over 30,000 people how to get more out of the software they already own — Excel, Access, Power BI, Word, Outlook, and now the AI tools that sit on top of all of it: Claude, ChatGPT, and Microsoft Copilot. My background is applied, not theoretical. Alongside teaching, I build real databases and reporting systems for clients in Excel, Access, and Power BI, so the examples I use in class are the problems I ran into last week, not textbook exercises. I also publish free tutorials on YouTube and longer courses online.

If any of that sounds useful to your team, come see what’s coming up at PCWebinars.com.