What to automate in Shopify support — and what to never hand to a bot

Sort your inbox by two axes, not one

Most automation decisions are made on volume alone: whatever we get asked most, automate first. That's half the picture. The better sort is volume against emotional stakes — how much it costs you if the answer lands badly.

High volume and low stakes is where automation is pure gain. High stakes is where it becomes a liability regardless of volume, because the failure mode isn't an unanswered question — it's a customer who feels dismissed by a machine.

Automate these without hesitation

These are high-volume, factual, and verifiable. A correct instant answer beats a correct answer in four hours, and there is no version of these where a human adds warmth that matters.

• Order status and delivery timing, once identity is verified.
• Shipping costs, thresholds, and regional timelines.
• Return windows and how to start a return.
• Sizing, materials, care instructions, and variant availability.
• Product comparisons and recommendations from your live catalogue.
• Store basics: payment methods, invoices, opening a support ticket.

Never fully automate these

Each of these has an emotional or financial charge that makes a wrong or cold answer expensive. Automation can gather context and route them, but the resolution should carry a human name.

• A damaged, wrong, or missing item — the customer is already unhappy and wants accountability.
• Anything involving a refund decision or goodwill gesture outside policy.
• Repeated failures: if someone has asked twice, the third answer must come from a person.
• Complaints about your product's quality, safety, or a reaction to it.
• Anything with legal, medical, or regulatory weight.
• Bulk, wholesale, or press enquiries — these are revenue conversations in disguise.

Design escalation as a feature, not a fallback

The worst automated support isn't the kind that can't answer — it's the kind that won't admit it. Shoppers forgive 'I don't know, let me get someone who does' almost instantly. They do not forgive a loop.

Three rules keep escalation trustworthy: make it available at any point without a magic phrase, carry the full conversation across so nobody repeats themselves, and set expectations about timing honestly. 'Someone will reply by tomorrow morning' beats silence dressed as availability.

The confidence rule

An assistant should be configured to volunteer uncertainty rather than fill gaps. That means saying so when a question falls outside its material, declining to guess at stock or delivery it cannot verify, and never inventing a discount, exception, or policy. An assistant that hedges when unsure is more useful than one that is confidently wrong, because the first can be trusted on the answers it does give.

What good looks like after a quarter

The healthy pattern isn't a support inbox at zero. It's an inbox where the repetitive questions have gone quiet and the remaining volume is genuinely worth a person's attention — the complaints, the edge cases, the wholesale enquiry that turns into an account. Your team gets harder, better work. That's the actual return, and it shows up in resolution quality long before it shows up in headcount.