Support slop is apology boilerplate that avoids saying what went wrong or what happens next. It can read as automated because it is evasive, especially when a customer already feels frustrated.
The phrases, and what to write instead
| Avoid | Write instead |
|---|---|
| Dear valued customer | Use their name. |
| We apologize for any inconvenience this may have caused | "Your order is four days late. That is our mistake." |
| I sincerely apologize for any inconvenience | Apologise for the specific thing, once. |
| Rest assured | State the next step and when it happens. |
| As per our policy | Explain the reason in plain words. |
| Unfortunately, we are unable to accommodate your request | "We can't refund this, because X. Here is what we can do." |
| Thank you for reaching out | Open with their issue. |
| Great idea! I'll pass that along to the team | Say whether anything will happen. If it will not, say that. |
| We take your feedback very seriously | Delete. Show it instead. |
| Your call is important to us | Delete. |
| I completely understand your frustration | Show it: repeat the specific problem back. |
| We are working diligently to resolve this | Say who is working on it and when you will update. |
| enthusiastically, flawlessly, efficiently | Cut the adverbs and state the fact. |
| Please don't hesitate to reach out with any further questions | "Reply here if it happens again." |
Complete example
Before
We sincerely apologize for any inconvenience. Rest assured that our team is looking into this matter: your replacement shipped without the charger, and we sent the charger today with tracking link [link].
After
Your replacement shipped without the charger. We sent the charger today, and the tracking link is [link].
We apologize for any inconvenience can fit a broad service notice. A one-to-one reply works better when it names the fault and next step.
Your [order or case] has [specific fault]. We [action] today. You can expect [next step] by [verified date].
Use only details you can verify.
Check this draft in the anti-slop editor
The editor checks general writing patterns. This guide includes context advice that the general checker does not test. Your draft stays in the browser; you choose each change.
Open the editor →The rule underneath all of them
Every replacement above does the same thing: it swaps a claim for evidence. That is the whole method, and it is why no tool can finish the job for you. A model can delete results-driven. Only you know the number that belongs there.
Density matters more than any single word. One phrase may be ordinary. Several nearby tells can make a draft feel templated. The full 200+ tell list covers vocabulary, sentence patterns and machine artifacts that apply across many drafts.
Questions
Why do customers react badly to AI-written support replies?
A reply can frustrate customers when it avoids the two things they often want to know: what went wrong and what happens next. Boilerplate apology may read as a brush-off. A reply that names the fault and the fix gives the customer something useful to act on.
What makes a support reply sound like a bot?
Apology without a subject ("any inconvenience"), policy citations without reasons, and the word "valued". All three avoid the specific issue. Name the issue and the next step instead.
Can we use AI drafts for support without sounding robotic?
You can use a draft if the agent replaces placeholders with the actual fault, fix and date. Review the message before sending, because a rushed workflow can leave the generic apology intact.