What to Automate First in Customer Support (Ecommerce Tier List)

Pick the wrong category to automate first and you'll burn customer goodwill before you build trust. Refunds are the canonical wrong answer (everyone wants to "prove" automation by tackling them; everyone gets stuck on judgment and exceptions). WISMO is the canonical right answer (high volume, fully data-driven, low downside if the AI is slightly off).

Sequence matters. The tier list below is the order to tackle categories in. Ensoras ships starter workflows for Tier 1 the moment you connect Shopify or WooCommerce, so the first batch of automation is automatic.

How to read this

Each tier has three dimensions:

• Volume: how much of your inbound this category represents
• Difficulty: how hard the category is for AI to handle
• Risk: cost of getting it wrong

The optimal sequence is high-volume + low-difficulty + low-risk first, decreasing volume and increasing difficulty over time.

Tier 1: Start here

These are the slam dunks. Live the moment you connect Ensoras.

WISMO ("Where is my order?")

• Volume: typically the largest single category in any ecommerce inbox. Often higher right after holidays.
• Difficulty: Low. Pure data lookup.
• Risk: Very low. Worst case is "the AI sent stale tracking info" — easy to fix.

The canonical first category. Connect to Shopify, pull tracking, send the customer a clean reply with carrier name, status, ETA. Your team will immediately notice the relief.

Order status questions

• Volume: significant (often counted with WISMO).
• Difficulty: Low.
• Risk: Very low.

Variations on WISMO that don't quite fit ("did my order ship", "is my order processed", "when will it arrive"). Same playbook.

Address changes pre-shipment

• Volume: small but high-value to the customer.
• Difficulty: Low. Single rule with a clear data check.
• Risk: Low. Worst case is a customer's package goes to the wrong place, recoverable via rerouting.

If the order hasn't been picked up by the carrier, update the address. If it has, escalate. The rule is simple and the customer benefit is huge — fixing an address mistake instantly is the kind of thing that earns CSAT points.

Order modifications within a defined window

• Volume: small.
• Difficulty: Low to medium depending on the action.
• Risk: Low.

Adding a note, swapping a size on a pre-fulfillment order, applying a coupon retroactively (within reason). Bound the window tightly — for example, "before payment is captured" — and let the AI handle it.

Tier 2: Add as you grow

Once Tier 1 is humming, expand into the next layer.

Returns initiation

• Volume: a meaningful share of inbound on most ecommerce stores.
• Difficulty: Medium. The AI generates a label, sends an email, updates the order.
• Risk: Low. Worst case is the customer returns something not eligible, recoverable via inspection.

The mechanical part of returns is rule-bound: generate label, email it, mark the order. The judgment part (whether to refund or replace, exception handling) stays in Tier 3.

Refunds within policy

• Volume: a steady share of inbound.
• Difficulty: Medium. Strict policy rules with clear data checks.
• Risk: Medium. Bad refunds are recoverable but visible.

Within your refund window, unshipped, under your dollar threshold, no fraud signals → refund. Anything outside those bounds → escalate. Our refund automation walkthrough has the full pattern.

Subscription pause / skip / swap / change frequency

• Volume: significant for subscription brands.
• Difficulty: Low to medium.
• Risk: Low. Pauses and skips are reversible.

Customers love instant subscription edits. The AI checks active status, no failed payments, and applies the change. Pause for the duration the customer asks, skip the next cycle, swap product flavor — all rule-bound. Recharge, Skio, and Chargebee tools handle the actions.

Account questions (password, login, email)

• Volume: a steady share.
• Difficulty: Low to medium.
• Risk: Low for password resets, slightly higher for email changes (security).

Password resets are dead simple. Login issues sometimes need investigation. Email changes need verification (security risk if automated naively). Build in proper verification flows.

FAQ-style policy questions

• Volume: substantial if your KB is good.
• Difficulty: Low if KB is comprehensive, high if it isn't.
• Risk: Low.

"What's your shipping policy?" "How long do refunds take?" "Do you ship internationally?" If these are well-documented, the AI handles them flawlessly. If they're not, fix the docs first.

Promo code and pricing questions

• Volume: small but recurring.
• Difficulty: Low.
• Risk: Low.

"Is X on sale?" "Can I use this code?" "Why am I being charged $Y?" Mostly data lookups against your active promotions and the customer's cart.

Tier 3: Augment, don't fully automate

These categories benefit from AI assistance but humans should still be in the loop.

Refunds outside policy

• Mode: AI drafts, human approves.
• Why hybrid: Outside-policy refunds are judgment calls. The AI can recommend ("approve goodwill refund of $X based on customer history") but a human should sign off.
• Path to full automation: Once you've watched the AI's drafts on outside-policy refunds and you trust the recommendations, automate the cleanest sub-cases (e.g., slightly outside the window for repeat customers). Keep the more ambiguous ones with human approval.

Sizing and fit complaints

• Mode: AI answers the data part, hybrid for emotional part.
• Why hybrid: A sizing complaint often combines a data question ("the size chart says X") with disappointment ("but it doesn't fit"). The AI can answer the first part; humans handle the second.

Damaged or wrong item complaints

• Mode: AI gathers info and starts the workflow, human decides resolution.
• Why hybrid: Customers want acknowledgment first ("oh no, that's awful"). AI can express sympathy but humans do it more credibly. The AI's job is to gather photos, document the issue, and start the replacement workflow, leaving the resolution decision to a human.

Cancellations from upset customers

• Mode: AI offers retention path, hybrid if customer pushes through.
• Why hybrid: Cancellation is a moment of friction. AI offers the standard retention options (pause, discount, swap). If the customer accepts, AI completes it. If the customer rejects and insists, escalate to a human who might find a better answer.

Loyalty / VIP issues (lower-tier VIPs)

• Mode: AI drafts replies, humans send.
• Why hybrid: VIP customers expect a personal touch. Even good AI feels transactional. The AI can prepare a perfect reply with full context; the human reviews and personalizes before sending.

Tier 4: Don't automate (yet)

Some categories should stay with humans permanently, or at least for the foreseeable future.

VIP-tier customer issues

• Why: VIP relationships are about feeling known. Automation breaks that feeling.
• Threshold: Define VIP explicitly. Common: top 5% by LTV, or named accounts, or lifetime spend > $X.
• Exception: VIPs can opt into AI handling for routine questions. Some prefer instant response.

Legal, regulatory, fraud language

• Why: Cost of getting it wrong is too high (legal liability, reputation, fraud losses).
• Detection: Keyword-based escalation. Words like "lawyer", "lawsuit", "fraud", "chargeback dispute", "regulator" trigger immediate human routing.

Wholesale, B2B, partnership inquiries

• Why: Different conversation style, longer cycles, often relationship-driven.
• Routing: Tag and route to the appropriate team (sales, partnerships, BD).

PR and media inquiries

• Why: A wrong answer here ends up in print.
• Routing: Tag, route to founder or PR contact.

Customers explicitly asking for a human

• Why: Always honor this. The cost of refusing is huge; the cost of routing is minimal.
• Detection: Keywords ("speak to a human", "real person", "agent please") plus repeated frustration patterns.

Sequencing in practice

The order to roll out, in plain steps:

1. Connect Ensoras to your store (Shopify App Store, WordPress plugin, or direct sign-up). 10 minutes. The auto-provisioned Order & Shipping, Returns & Refunds, Product Information, and Order Actions workflows go live immediately, covering most of Tier 1.
2. Add address-change and order-modification workflows in plain English. Each is a single form save.
3. Add Tier 2 workflows — subscription edits via Recharge/Skio/Chargebee, account help, FAQ-style policy questions backed by your knowledge base.
4. Add Tier 3 with AI reply approval on — outside-policy refunds, damaged items, sizing complaints. The AI drafts, a human signs off.
5. Tune as patterns emerge. Watch the analytics dashboard, add knowledge base items for any "I don't know" patterns, sharpen workflow instructions for any escalation that should have been handled.

Each step is independent. Move at the pace your team is comfortable with — there's no calendar to follow.

What can go wrong

The most common derailment points:

• Skipping Tier 1. Teams think WISMO is "too easy" and jump to refunds first. Start where the wins are easy and obvious; Ensoras's auto-provisioned workflows make this the default anyway.
• Adding too many Tier 2 workflows at once. Add one, watch a handful of tickets in the audit trail, then add the next.
• Forgetting Tier 4 boundaries. Define VIP and legal escalation rules from the start. Ensoras escalates legal-language tickets by default.
• Skipping the metrics review. The Ensoras dashboard surfaces autonomous resolution rate, sentiment, escalation reasons, and per-workflow stats. Glance regularly so you catch any category dragging the average.

If you remember three things

1. Sequence beats vendor choice. Skipping Tier 1 to start with refunds is the single most common reason rollouts struggle.
2. Tier 4 is permanent. The list of categories not to automate isn't a temporary state — it's the floor under which routing always goes to humans.
3. Tier 1 compounds. A clean WISMO deployment is the foundation that makes Tier 2 easy.

What to do next

1. Install Ensoras free — Shopify App Store, WordPress plugin, or direct sign-up. 10 minutes. 30 tickets/month free, no credit card. Tier 1 workflows ship pre-built.
2. Add Tier 2 workflows in plain English as patterns emerge in your inbox.
3. Layer in Tier 3 with AI reply approval on so a human signs off on the judgment-heavy categories.
4. Keep Tier 4 routed to humans by default.

For the full playbook see Customer Support Automation Playbook. For the workflow rule format, see The When/If/Then Framework.

Sources

• Bank of America, A Decade of AI Innovation: Erica Surpasses 3 Billion Client Interactions, customer-side reference for what Tier 1 categories look like at sustained scale (50M users, 58M monthly interactions on routine financial queries).