agentleFS
ReplAi-NowReplAi-Now/shopify-skills/skills/support/angry-customer-reply/SKILL.md

angry-customer-reply

Skill1 starsChanged 20 days agoMITView on GitHub

Reply to an angry or upset store customer. Use when the user pastes a complaint, rude email, chat message or bad review, or mentions a chargeback threat.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write one reply the store owner can send as it stands: it de-escalates, fixes what can be fixed, and stays inside what the owner has …

    line 8
  2. Very specific:

    If the user wants a draft straight away, write it with square-bracket placeholders such as [ORDER NUMBER] or [DELIVERY DATE] for every fact …

    line 19
  3. Distinctive:

    Before writing, work out:

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Angry Customer Reply

Write one reply the store owner can send as it stands: it de-escalates, fixes what can be fixed, and stays inside what the owner has approved.

1. Get the facts

You need four things. Take what the user already gave you, then ask for the rest in one message:

  • The customer's message, word for word.
  • The order: what they bought, when, and where it is now (tracking status, delivered, returned).
  • The policy that applies: returns window, refund rules, delivery promises.
  • The offer: what the owner is willing to do (refund, replacement, discount, store credit, or only what the policy says).

If the user wants a draft straight away, write it with square-bracket placeholders such as [ORDER NUMBER] or [DELIVERY DATE] for every fact you lack. Every date, number, tracking status and policy term in the reply comes from the user or sits in a placeholder.

Done when: you hold all four, or each gap is a placeholder.

2. Read the message

Before writing, work out:

  1. What went wrong, as a fact ("parcel stuck at the depot for 9 days"), separate from how the customer feels about it.
  2. What they want: money back, the item, an apology, or to be heard.
  3. Which case applies, from Cases below.

3. Write the reply

Four parts, in this order:

  1. Name the problem in their terms, in one sentence, so they know you read it.
  2. Own the store's part plainly. The store chose the courier and the supplier, so the store owns the delay: say what you will do about it, and leave out whose fault it was.
  3. The fix: a concrete action and when it happens. When the owner approved more than one option, offer a choice. A choice hands control back to the customer, and that is what de-escalates.
  4. Sign off with a person's first name and the store name.

Style:

  • Under 120 words. An angry reader skims.
  • Plain, warm and direct, like the owner talking across a shop counter. Short sentences.
  • The same language the customer wrote in.
  • One plain apology ("I'm sorry"), early, then straight to the fix.
  • Specific words in place of stock phrases: "your parcel hasn't moved since 3 June" in place of "we apologise for any inconvenience", and "our returns window is 30 days" in place of "as per our policy".

Done when: every fact comes from step 1 or a placeholder, every promise is one the owner approved, and the reply is under 120 words.

4. Hand it over

Give the reply, then a Before you send list of two or three lines: placeholders to fill, facts to double-check, and any assumption you made about the offer.

Cases

  • Store at fault (late, damaged, wrong item): apologise, fix, done. Most complaints are this case.
  • Customer is mistaken (outside the returns window, misread the listing): state the fact once, kindly, with the date or wording that shows it. Then offer whatever goodwill the owner approved, or say what you can do.
  • Chargeback or bank threat: answer the problem and leave the threat alone. A fast fix is the best chargeback defence. Add to Before you send: reply today, and keep a copy of the thread.
  • Legal threat, injury or product safety: draft only a short holding reply ("Thank you for telling us. I'm looking into this now and will reply in full by [DATE].") and tell the owner to get advice before saying more. The holding reply carries no admission and no offer.
  • Abuse (slurs, threats against a person): draft a short, calm reply that sets a boundary and still offers the fix if one is owed. Tell the owner they can decline to serve this customer.
  • Public review: under 60 words. Thank them, apologise for the specific problem, and invite them to email [SUPPORT EMAIL]. Keep order numbers, names and addresses out of public replies.

Example

User: Email from Sam: "Ordered 3 weeks ago and STILL nothing. Your tracking hasn't moved in 9 days. This is a scam and I want my money back NOW or I'm calling my bank." Order #1042, stuck at the courier depot since the 14th. If a parcel is lost we refund or resend. Happy to resend by express or refund, their choice.

Reply:

Hi Sam,

You're right: your tracking hasn't moved in 9 days, and three weeks is far too long to wait. I'm sorry.

Two options, your choice:

  1. I send a replacement today by express delivery, arriving by [DELIVERY DATE].
  2. I refund you in full today.

Reply 1 or 2 and I'll get it done.

[YOUR NAME] [STORE NAME]

Before you send:

  • Fill in the express delivery date from your courier.
  • They mentioned their bank: send this today, and keep a copy of the thread.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.