What Not to Automate: Five Replies That Should Stay Human

Description and use

Automating support replies can cause costly mistakes when messages involve disputes, money, safety, anger, or legal rights. The article outlines a workflow that identifies five categories requiring human handling and provides a handoff and alert system.

Problem

Automating customer support replies can lead to costly mistakes when the conversation involves disputes, money, safety, anger, or legal rights.

Outcome

The new workflow reduces costly automation errors by ensuring that high‑risk messages are handled by humans, while low‑risk repetitive queries remain automated, improving customer trust and operational efficiency.

Workflow

• 1. Define five handoff categories: dispute escalation, price disputes, safety/product‑hazard, angry review threat, and legal rights.
• 2. Create a handoff keyword list (e.g., refund, dispute, chargeback, lawyer, unsafe, "report you").
• 3. Set permission thresholds so money‑related requests exceed automation authority.
• 4. Implement a one‑click manual mode for any chat that goes sideways.
• 5. Use a neutral line such as "Let me check this and come back to you" when unsure.
• 6. Spot‑check daily for the first weeks, then weekly, to confirm alerts fire correctly.
• 7. Maintain and refresh the keyword list against real threads.
• 8. Log all threads and keep records of what was promised.
• 9. Route the conversation to a human agent for substantive responses.

Evidence

Once a customer names a dispute — "I'll open a case," "this is the third time," any mention of the platform, a chargeback, or consumer rights — the conversation is no longer about the parcel.

Source

Any reply that commits money — a discount, a price match, a goodwill credit — is a business decision, not an information lookup.

Source

These need a human immediately, because the next message may come from a hospital, a lawyer, or a regulator.

Source

Anger is a trigger, not a query. Keyword matching fails in both directions... Keep automation to logging the thread and, at most, a neutral holding line.

Source

Warranty claims, statutory returns, personal‑data deletion requests, accessibility accommodations. The wording of these replies can create obligations the store did not intend... The safer pattern is acknowledgment plus routing.

Source

Maintain a handoff keyword list — refund, dispute, chargeback, lawyer, unsafe, "report you" — and refresh it against real threads

Source