Automating support without making customers angry

Sort by answer shape, not by volume

The usual approach is to automate the most frequent tickets. The better filter is whether the question has exactly one correct answer that your systems already know.

Where is my order, what is your return window, does this ship to my province — one answer, verifiable, safe to automate.

My order arrived damaged and I need it before Friday — not one answer. That is a judgement call with an upset person attached.

Make the exit obvious

The fastest way to make automation hated is to hide the path to a human. Put it in the first reply. Customers who can see an exit are far more willing to try the automated path first.

Carry the context across

If a conversation escalates, the agent should receive the transcript and what the assistant already checked. Asking the customer to repeat everything is the moment the automation turns into a net negative.

Watch the right number

Deflection rate looks good and hides damage. Track resolution rate and repeat contacts within a few days. An assistant that closes conversations without solving anything shows up as a great deflection number and a growing pile of second contacts.