WISMO Overload at Peak Season: Handle It Without Hiring

Every November, the same thing happens. Order volume spikes, WISMO emails flood in, and small support teams either hire someone they do not need in January or drown for six weeks. There is a third option. It takes about 2-3 hours to set up in October and it does not involve per-resolution fees that compound exactly when your margins are tightest.

The short version

WISMO - where is my order - is not a complicated support problem. It is a volume problem. During Black Friday and the holiday window, most small e-commerce teams see WISMO questions hit 60-70% of total support volume. Off-peak that number drops to 30-40%, which is manageable. Peak season is not manageable without a system.

Hiring a seasonal rep to handle it costs $3-4K per month loaded, plus two to three weeks of onboarding time you do not have in October. Per-resolution AI tools like Intercom Fin charge $0.99 per resolution - so 3,000 WISMO resolutions in November is $2,970 on top of your base plan. The math flips against you at exactly the wrong moment.

The alternative is automation rules plus a tight knowledge base. Build it once, tune it for two weeks before peak, and let the majority of that volume handle itself. The rest - damaged items, missing packages, refund disputes - stays with a human. That is the right split. This post walks through the exact setup.

What WISMO actually costs at peak

WISMO covers any ticket asking about order status, shipping ETA, a tracking link, or a delivery delay. It sounds like: 'Hey, I ordered three days ago and have not gotten a shipping confirmation' or 'My tracking link says it is still in the warehouse, is that right?' or just 'Where is my order?'

During BFCM and the holiday window, that category swells to the majority of everything that comes in. Your other categories - product questions, returns, billing issues - do not disappear. They just get buried under the WISMO pile.

Per-resolution pricing tools make this worse. Intercom Fin charges $0.99 per resolution. If you run 3,000 WISMO resolutions in November - not unrealistic for a mid-size Shopify store during peak - that is $2,970 in resolution fees alone, before your base plan. Compare that to a flat $149/month on Trigli Growth, which covers 2,500 emails. Your November bill is the same as your July bill. That predictability matters when you are trying to plan peak-season margins. See the full pricing breakdown at /pricing.

Why WISMO is actually the easiest problem to automate

WISMO questions are repetitive and low-stakes. The answer is almost always a tracking link or a status update. The AI does not need to make a judgment call. It needs to find the right information from your docs and send it. That is the category where auto-send - not just draft - is genuinely safe if you set the confidence floor correctly.

Contrast that with edge cases: a package that arrived damaged, an order with the wrong item, a refund dispute where the customer is already frustrated. Those need a human. Not because the AI cannot draft a reply, but because the customer is feeling something and a fast automated response is the fastest way to lose them. The automation setup I am describing routes those to human review automatically. They never touch the auto-send queue.

This is the core insight. WISMO automation is not about replacing human judgment. It is about removing the work that never needed human judgment in the first place. For more on where that line sits, /blog/automate-customer-support-without-losing-human-touch goes deeper on the two-column approach.

Before you configure anything: build the knowledge base first

The AI answers from your docs. If your shipping policy says orders ship soon, the AI will say orders ship soon. That is not a useful answer. This is the part most teams skip and then wonder why the AI sounds generic.

What to put in the knowledge base before peak season:

• Shipping policy with specific numbers. 'Orders ship within 2 business days' beats 'orders ship soon.' Include carrier names and typical transit times by region.
• Carrier SLAs and what happens when an order is delayed - who the customer should contact, what your policy is, when you consider a package lost.
• How to find a tracking link - where it is in their confirmation email, what the link format looks like, which carrier portal to use.
• Holiday cut-off dates for guaranteed delivery. Be specific: 'Order by December 18 for standard shipping delivery by December 24.'
• Edge case policies too: damaged item process, wrong item process, refund window. Even if those route to human review, the AI can pull context from them when drafting a handoff message.

PDF uploads, paste-in text, and URL imports all work. Use whatever is fastest. If your shipping policy is already on your website, import the URL. If it is in a Google Doc, paste it in. The goal is specificity, not format.

The four routing actions and when to use each

Trigli's automation rules give you four actions for each category: auto_send, draft, human_review, and skip. Here is how I think about each one for WISMO season.

Priority ordering is not optional. Set your human_review rules above your auto_send rules. An email that mentions 'damaged' or 'wrong item' should hit the human_review rule before the auto_send rule ever evaluates it. If you get this backwards, edge cases slip through to auto-send and you have a problem.

Step-by-step: configuring WISMO routing for peak season

1. Create a category called 'order_status' in your automation rules. Sub-categories: tracking_request, delivery_delay, order_confirmation. Set the action to auto_send or draft depending on your comfort level. Start with draft if you are new to this.
2. Create a separate category called 'order_issue' with sub-categories: damaged_item, wrong_item, missing_package. Route all of these to human_review. No exceptions.
3. Set priority so order_issue rules evaluate before order_status rules. This is the safety net. An email mentioning 'damaged' hits order_issue first and goes to human_review before order_status ever sees it.
4. Set your confidence floor. Below the threshold, nothing auto-sends regardless of category. The AI flags uncertain replies for review instead. This is the other safety net.
5. Test with 10-15 real past WISMO emails before going live. Pull them from your sent folder or inbox. Run them through the rules and check that they route where you expect.
6. Go live and check the draft queue after the first 48 hours. Look for anything that routed wrong. Adjust sub-categories or confidence floor based on what you see.
7. During peak week, check SLA alerts daily. The built-in SLA tracking will flag anything in human_review that has been sitting too long. Nothing falls through the cracks.

What the reply actually looks like

Before drafting anything, Trigli scans your past sent emails to learn your tone. The reply it drafts sounds like your team, not a support bot. Short sentences if that is how you write. Friendly sign-offs if that is your style. The AI picks this up from the pattern of what you have already sent.

A clean tracking request comes in. The AI pulls the tracking link template and the order reference from the email, drafts a reply in your voice, and either sends it automatically or drops it in your draft queue depending on your rule. The reply goes out from your real email address via OAuth. The customer sees no difference. They just got a fast answer that came from your actual policy docs.

For draft mode: the reply sits in your queue. You scan it in 10 seconds and hit send. That is still dramatically faster than writing from scratch, and it is faster than the 3-hour response time that happens when your team is buried. For more on how AI email drafting works in practice, /blog/ai-email-autoresponders-small-business has a detailed breakdown.

Where per-resolution pricing tools get expensive at peak

I am not going to pretend Intercom Fin is bad. It is a solid product. But the pricing model has a structural problem for small e-commerce teams at peak season.

Fin charges $0.99 per resolution. At 3,000 WISMO resolutions in November, that is $2,970 in resolution fees on top of whatever your base plan costs. Zendesk AI add-ons work similarly, roughly per-resolution or per-agent-seat pricing depending on the tier. The irony is that the tool gets more expensive exactly when your volume spikes, which is exactly when your margins are tightest after BFCM discounting.

Flat pricing means your November bill is the same as your July bill. Trigli Growth is $149/month flat, 2,500 emails included. If you are doing 10,000+ WISMO emails a month at peak, you should look at enterprise tools - be honest with yourself about scale. But most small teams are not there, and paying per-resolution at 3,000 emails a month is just a worse deal than flat pricing at that volume. The comparison at /blog/cost-of-support-rep-vs-ai runs the full numbers.

Where this setup does not help you

Worth being direct about what this does not solve. No phone or SMS - if your customers call in, this does not touch that channel. Email and chat only. No native Shopify actions - the AI can reference your refund policy and draft a reply explaining the process, but it cannot process a refund inside Shopify. The customer still has to go through your normal refund flow. More detail on that at /use-cases/shopify. No skill-based routing to specific agents - you can route damaged-item tickets to human_review, but you cannot auto-assign them to your most experienced rep based on a skill tag. You assign manually from the queue. No social DMs - Instagram, Facebook Messenger, WhatsApp - none of those are supported. If your WISMO volume comes through DMs, this setup does not help with that portion. And one brand per account - if you run multiple Shopify stores under different brand names, you need separate accounts.

If those gaps are blockers, be honest with yourself about whether this is the right fit. The free tier at trigli.com costs nothing to try, so you can see the routing setup before committing.

The honest numbers: what to expect

Most teams I have talked to see the majority of peak volume handled without human touch after this setup is tuned. The remaining portion is the edge cases that genuinely need a person - damaged items, frustrated customers, refund disputes. That is not a failure. That is the right split. The goal was never to automate everything. It was to stop drowning in the stuff that never needed a human.

Response time on clean WISMO drops from hours to minutes for the auto-send category. For draft mode, it drops from hours to however long it takes you to scan the queue - usually a few minutes twice a day.

The setup takes about 2-3 hours the first time. One hour building the knowledge base. One hour configuring rules and testing. Thirty minutes tuning after the first 48 hours of live traffic. That is a one-time cost against six weeks of peak season. The math is obvious.

A note on peak-season timing

Do this in October. Not November 25th. Give yourself two weeks of live traffic before BFCM so you can tune the confidence floor and catch any misroutes before volume spikes. The draft queue is your safety net during the tuning period - nothing auto-sends until you trust it.

During peak week, SLA tracking with overdue alerts means nothing sits in human_review too long without you knowing. Two weeks of live tuning before BFCM is what gets your confidence floor calibrated to your actual email patterns rather than a guess. You will see what is piling up, what is getting handled, and where the rules need adjustment. That visibility is what keeps the human_review queue from becoming its own version of the problem you were trying to solve.

Quick summary: the setup checklist

1. Build knowledge base: shipping policy with specific numbers, carrier SLAs, tracking instructions, holiday cut-off dates, edge case policies.
2. Create order_status category with auto_send or draft actions for clean WISMO sub-categories.
3. Create order_issue category with human_review for damaged_item, wrong_item, missing_package.
4. Set priority so order_issue rules evaluate before order_status rules.
5. Set confidence floor so uncertain replies never auto-send - they flag for review instead.
6. Test on 10-15 real past WISMO emails before going live.
7. Go live 2 weeks before peak. Tune from the draft queue after the first 48 hours.
8. Check SLA alerts daily during peak week. Nothing should sit in human_review past your threshold without you knowing.

You do not need to hire for the spike. You need to triage better. The spike is predictable. The emails are repetitive. The setup is a few hours of work in October. That is the trade.