← Back to Blog

What to Automate in Customer Support: Shopify Ticket Guide

Learn what to automate in customer support on Shopify: a ticket-type decision table, approval thresholds by order value, and a 4-week rollout plan.

Heylio Team November 18, 2026 6 min read

Most small-store inboxes are 60-70% repetitive ticket types, but the remaining 30% carries most of the refund and churn risk. Shopify support automation works when you automate the repeatable majority, route risky tickets through approval, and keep a short list human-only. This guide gives you the rules, a decision table, and a rollout plan.

Key takeaways

  • 60-70% of tickets (WISMO, FAQ, early address changes) are safe to auto-resolve.
  • Refunds, out-of-policy returns and damaged items fit draft-and-approve.
  • Chargebacks, legal threats and VIP complaints stay human-only.
  • Set approval thresholds by order value, then audit weekly for four weeks.

Which support tickets should you automate first?

Automate tickets where the answer is factual, the data lives in Shopify, and a wrong reply costs little. Typically that means WISMO (where is my order), policy FAQs, and address changes before fulfillment. Together these often make up 60-70% of a small store's inbox, so they deliver most of the time savings.

The test is simple. Ask three questions of any ticket type:

If the answers are yes, yes, no, automate it. This is the core of any sound set of customer support automation rules: risk, not volume, decides the mode.

Which ticket types are safe to fully automate?

Three ticket types are safe to auto-resolve: WISMO, FAQ, and address changes made before fulfillment. Each has a verifiable answer in Shopify, and a mistake is cheap to correct. A WISMO reply that quotes the wrong carrier status costs one extra email, not a refund.

The guardrail is the fulfillment check. Once an order has shipped, an address change becomes a carrier problem, so it should drop to draft-and-approve.

With Heylio, each of these maps to a playbook (FAQ, WISMO) that uses the Shopify order lookup and address change tools. Auto-resolved tickets cost €0.49 each, or €0.39 with a monthly pack.

Which tickets should be AI-drafted with human approval?

Use draft-and-approve for any ticket that moves money or bends policy: refunds, out-of-policy returns, and damaged items. The AI does the reading, the order lookup, and the writing. A human spends about ten seconds approving. You keep speed without handing over the checkbook.

Typical cases:

This is a shopify ai support approval workflow in practice. In Heylio, an approved draft costs €0.10, which is less than the cost of writing the reply yourself. Edits you make are tracked, and Heylio suggests knowledge base and playbook updates from those corrections.

Which tickets should stay human-only?

Keep chargebacks, legal threats, and VIP complaints human-only. These tickets are rare, often under 5% of volume, but a single mishandled one can cost an order value, a customer for life, or a legal bill. Tone and judgment matter more than speed here.

Good ai customer support human handoff means the AI recognizes these, stops, and passes the full thread with context. In Heylio, handing over to a human is never billed, so there is no financial reason to let the AI push through a ticket it should not touch.

What is the decision table for each ticket type?

The table below assigns a risk level, a recommended mode, and the Shopify action involved to each common ticket type. Use it as a starting default, then adjust it to your margins and policies.

Ticket type Risk level Recommended mode Shopify action involved
WISMO Low Auto-resolve Look up order status and tracking
Policy FAQ Low Auto-resolve None (knowledge base only)
Address change, unfulfilled Low Auto-resolve Change address
Address change, shipped Medium Draft and approve None until carrier confirms
Order cancellation, unfulfilled Medium Draft and approve Cancel order
Standard refund Medium Draft and approve Refund
Out-of-policy return Medium-high Draft and approve Refund or discount
Damaged item Medium-high Draft and approve Refund, replacement, gift card
Discount or goodwill request Medium Draft and approve Apply discount
Chargeback High Human only None (evidence handled manually)
Legal threat High Human only None
VIP complaint High Human only Any, manually

How do you set approval thresholds by order value?

Set thresholds by order value so that the money at risk decides the level of oversight. A common starting split is: under €30 auto-approve simple cases, €30-150 draft and approve, above €150 human review. These numbers are examples, so tune them to your average order value.

A practical method:

  1. Find your average order value (AOV).
  2. Set the auto tier near 0.5x AOV.
  3. Set human-only review near 2x AOV.
  4. Everything between goes to draft and approve.

A store with a €60 AOV might auto-handle under €30 and require human review above €120. Review the thresholds after 30 days of data. If you approve 98% of drafts untouched in a tier, loosen it. If you edit 30%, tighten it or fix the playbook.

Where does Heylio fit in this setup?

Heylio is the layer that applies these rules inside your inbox. It connects to Gmail, Outlook, Instagram DMs, WhatsApp, and an embedded chat widget. It drafts replies from your knowledge base and playbooks for FAQ, WISMO, refunds, returns, and cancellations. It can also act in Shopify.

Citation capsule: Heylio prices support by outcome. Under Heylio Care, a ticket resolved by the AI costs €0.49, or €0.39 with a monthly pack. A draft a human approves costs €0.10. Handing a ticket to a human is never billed. Prices are in euros excluding VAT, with pay as you go or monthly packs that do not roll over, and there is no free trial. In practice, that means risky ticket types cost little to route through approval, and tickets the AI should not touch cost nothing to escalate. Shopify actions available to the AI include order lookup, cancellations, refunds, discounts, address changes, and gift cards. You choose which actions each playbook may take.

Honest caveat: Heylio does not remove the need for judgment. You still define the playbooks and thresholds. It makes those rules enforceable.

What does a 4-week rollout plan look like?

Roll out in four weeks, adding one risk tier per week, so you catch errors while volume is small. Starting with the lowest-risk tickets typically gives you a working automation layer by week two and a full approval workflow by week four.

After week four, audit weekly for a month, then monthly.

Start with the boring 60%

The safest first move is also the most profitable: automate WISMO, FAQ, and pre-fulfillment address changes, then put refunds behind approval and keep chargebacks, legal threats, and VIPs human. Label your last 100 tickets against the decision table this week, and you will see exactly where your 60-70% sits.

Frequently asked questions

Will AI refund things it shouldn't? ▼
Not if refunds sit in draft-and-approve mode. The AI proposes the refund and a human approves it, at €0.10 per approved draft in Heylio. Add an order-value threshold so high-value refunds always get human review.
How do I audit automated replies? ▼
Read every auto-resolved reply for the first three days, then sample 20 per week. Track the share of drafts you edit; above 20-30% edits signals a playbook or knowledge base gap.
Which support tickets should I automate first? ▼
Start with WISMO, policy FAQs, and address changes before fulfillment. They are low risk, verifiable in Shopify, and commonly make up 60-70% of small-store inbox volume.
Do I pay when a ticket is handed to a human? ▼
No. In Heylio, handing over to a human is never billed. You only pay for AI-resolved tickets (€0.49, or €0.39 with a monthly pack) and approved drafts (€0.10).
What order value should require human approval? ▼
Start near 0.5x your average order value for the auto tier and 2x for human-only review. For a €60 AOV, that is roughly under €30 and above €120. Adjust after 30 days of data.

Automate your customer support with AI

Get started