The Response Skill: How Your Team Should Handle the Hard Customer Emails
It is 4:55 on a Friday. A customer emails, annoyed. Half their order shipped, the other half is backordered three weeks, and nobody told them. Your newest rep wants to make it right. So they reply fast.
They apologize. Then they promise the backordered items will ship Monday. They waive the freight to smooth it over. And they cc nobody, because it is Friday and they want this closed.
Three things just went wrong. The backorder cannot ship Monday, so now you have broken a second promise on top of the first. Freight is not the rep's to waive on this account. And the one person who needed to know, the account owner, is in the dark.
Here is the part that should worry you. The customer probably will not complain again. They will just start sourcing elsewhere. Qualtrics XM Institute surveyed more than 20,000 people in late 2025 and found that fewer than one in three customers give a company any feedback after a bad experience. They do not argue. They reduce what they spend, and you find out next quarter when the orders are smaller.
Now picture the same Friday, except the rep pastes the customer's email and their draft reply into one place first. And before it sends, they see this.
📫 RESPONSE CHECK
Re: Where is the rest of PO #88231?
Customer: Midwest Manufacturing Co. | Rep: new hire, week 3 | Checked before send
🔴 STOP. THIS WILL BACKFIRE.
• You promised Monday. The ERP shows this SKU on a vendor backorder through July 7. You are about to break a second promise. Give the real date.
• You waived freight. This account is on contract pricing. Freight concessions here need manager sign-off. Do not offer it in writing yet.
🔵 LOOP IN BEFORE YOU SEND
• Dana R. owns this account. She has a standing note on the file: any service issue over $5k, cc her. This order is $11,400.
• This is the third short-ship in 90 days for this customer. That is a pattern worth flagging, not a one-off to smooth over.
🟡 TONE CHECK
• Your draft opens with four sentences of apology. One is enough. This customer runs a plant floor and wants the fix, not the grovel.
• Drop the phrase “unfortunately our system.” We own the miss. We do not blame the software.
🟢 WHAT WE ACTUALLY DO HERE
• Give the real ship date, even when it is worse than they hoped. We have learned a true date beats a hopeful one every time.
• Offer the concession we can actually authorize: expedited freight on the backordered half once it is in stock, manager approves same day.
📝 SUGGESTED REWRITE
“Hi Mike, you're right, and I'm sorry. Half of PO #88231 shipped and the rest sat on a backorder we should have flagged. Straight answer on timing: the remaining items are due in our warehouse July 7, and I'll have them on a truck to you the same day. I've looped in Dana, who handles your account, so this is on both our radars. Once the second half is in, I'll cover expedited freight to make up for the wait. I'll confirm in writing once my manager signs off, which I expect today.”
Same rep. Same Friday. The difference is a reply that holds up on Monday.
The skill did not write the reply. The rep did. What the skill did was catch the three things a fifteen-year veteran would have caught on instinct, and a three-week hire could not have known.
Here is what I actually think, having watched a lot of teams try to fix this. The instinct is to write a policy doc and make everyone read it. That never works. Nobody opens the 14-page response guide at 4:55 on a Friday. The reason a skill works where a PDF fails is not that the AI is smarter. It is that the guidance shows up at the one moment a person is actually deciding what to write, instead of sitting in a shared drive nobody visits. Point of decision beats point of training. That is the whole trick.
The Day Your Best Rep Quits
Every distributor has one. The account manager who has been there fifteen years and just knows things. Knows that Henderson Supply always claims urgency but never actually needs it Friday. Knows which customers you never put a price in writing for without checking. Knows that when the Tulsa branch says “rush,” they mean it, and when Phoenix says it, they do not.
“Oh, don't worry about that customer, Sharon always handles them.”
“We don't really put that in writing, but I'm not sure why.”
“Sharon retires in March.”
None of that is written down. It lives in one person's head. And the day they give notice, you have roughly two weeks to extract fifteen years of judgment, which is not going to happen. So the new hire who replaces them starts from zero, makes the Friday-afternoon mistake, and learns the rules one angry customer at a time.
A response skill is how you get that judgment out of one head and into a form the whole team can use. You are not replacing your veteran. You are cloning the part of them that knows how you handle things. And you are doing it while they are still around to tell you what the rules actually are.
What a Skill Actually Is
If you have used AI at all, you have written prompts. A skill is the next step up. It is a saved set of instructions, examples, and rules that you build once and reuse every time, so you are not re-explaining your company from scratch on every request. In Claude you build it as a Project. You load it with the context once, and everyone you share it with gets the same trained judgment.
A response skill for your team holds four things:
- Your real replies. A dozen or two emails your best people actually sent to tricky situations. This is the part that captures the judgment. The AI learns your style from your own work, not from a generic idea of “professional.”
- The hard lines. What a rep can promise alone and what needs a manager. Freight waivers, ship dates, pricing, credits. The stuff that gets a company in trouble when a new hire guesses.
- Who to loop in, and when. Account owners, dollar thresholds, the standing notes that currently live in one person's memory.
- Your tone. How much you apologize, whether you blame the system (you do not), how direct you are with a plant manager versus a procurement lead.
The rep pastes in the customer email and their draft. The skill reads both against everything above and flags what is off before anything sends. The person still writes the reply and still owns it. They just stop walking into the obvious traps.
Build Your Own: The Response Skill Prompt
Set this up as a Claude Project. Paste the instructions below into the project's custom instructions, then upload your example replies and your rules as project files. Once it is built, any rep you share it with can use it. Here is the instruction block to start from:
You are a response coach for our sales and account
management team. When a rep gives you a customer message
and their draft reply, your job is to catch problems
BEFORE the reply is sent. You do not send anything and
you do not rewrite without showing your reasoning.
YOU HAVE BEEN GIVEN (as project files):
- example_replies: real emails our best people sent to
hard situations. Match this voice and judgment.
- authority_rules: what a rep can promise alone vs. what
needs manager sign-off (ship dates, freight, pricing,
credits, returns).
- escalation_rules: which accounts have owners, dollar
thresholds for looping someone in, standing account notes.
- tone_guide: how we talk to customers.
WHEN I GIVE YOU A CUSTOMER MESSAGE + A DRAFT REPLY,
RESPOND IN THIS ORDER:
1. STOP, THIS WILL BACKFIRE
- Anything in the draft that breaks a rule, makes a
promise we can't keep, or commits something the rep
can't authorize. Quote the specific line. Say why.
- If nothing, say "Nothing blocking."
2. LOOP IN BEFORE YOU SEND
- Who needs to be cc'd or told, based on escalation_rules
and the dollar amount or account involved.
- Flag if this looks like a repeat issue worth escalating.
3. TONE CHECK
- Where the draft is off from tone_guide: over-apologizing,
blaming our system, too stiff, too casual for this contact.
4. SUGGESTED REWRITE
- A full replacement draft the rep can edit and send.
- Use real specifics from the customer message. Match the
voice in example_replies. Give true dates, not hopeful ones.
RULES:
- If you are missing a fact you need (a real ship date, an
account owner), say what you'd need rather than guessing.
- Never invent a policy. If the rules don't cover it, say
"not covered, check with a manager."
- Keep the rewrite about as long as the rep's draft. We are
fixing it, not writing an essay.
Step 1: Gather the Raw Material
The skill is only as good as what you feed it. None of this requires writing a policy manual. You are collecting things you already have:
- 15 to 20 real replies. Pull them straight from the sent folders of your two or three best people. Aim for the messy ones: complaints, backorders, pricing pushback, a customer who threatened to leave. Strip out anything sensitive, keep the wording.
- Your authority lines. A half-page is fine. What can a rep approve on their own, and what needs a manager. If it only exists in someone's head, this is the moment to get it down. A 20-minute conversation with your veteran covers most of it.
- Account flags. Who owns which accounts, any dollar threshold that triggers a cc, and the handful of customers everyone “just knows” to treat a certain way.
- A few tone notes. Even just “one apology, not five” and “never blame the ERP” goes a long way. The example replies carry most of the tone on their own.
Step 2: Build It and Hand It Out
Build it once. Use it forever. The setup runs about 30 minutes:
Create a Claude Project called something like “Customer Reply Check.” Paste the instruction block above into the project's custom instructions.
- Upload your four files from Step 1: the example replies, the authority rules, the escalation flags, the tone notes. The project reads them on every request.
- Test it on five real situations you already know the right answer to. Tune the rules where it gets one wrong. This is the step people skip, and it is the one that matters.
- Share the project with your sales and account team. They paste in a customer email and their draft, and the check runs in seconds. No one else has to set anything up.
One note on rollout. Tell your team this checks the email, not them. The fastest way to kill adoption is to make it feel like surveillance. Framed right, reps like it, because it covers them on the Friday calls they were nervous about anyway.
The Bottom Line
Most companies handle this exactly backward. They hire a junior rep, hand them a login and a phone, and let them learn the hard rules by breaking them on live customers. The veteran who knows better is three desks away, slammed, and only finds out about the bad reply after it has gone out.
A response skill does not replace the veteran, and it does not replace the judgment of the person sending the email. It just puts the veteran's experience in the room at the moment the junior rep is deciding what to write. That is the whole value. Right place, right second.
And it has a second payoff most people miss. The act of building it forces you to write down rules that currently live nowhere. So when Sharon does retire in March, the judgment does not leave with her.
30 minutes to build. Zero extra headcount. Fewer Friday-afternoon mistakes.
Pull the examples. Write down the rules. Build the project before your next new hire starts.
👇 👇 👇
Your team spent time this week getting better at responding to hard customer emails. The response skill in this week's newsletter was designed to capture tribal knowledge before it walks out the door.
Y Meadows applies the same philosophy to order processing.
Instead of relying on individual employees to manually read, interpret, and enter orders, Y Meadows automates the process from intake through ERP.
Faster processing. Fewer errors. Less operational risk.