WISMO Tickets at Black Friday Volume: A Playbook

Every Q4, the same thing happens. Orders go out, carriers get overwhelmed, and your inbox fills up with some version of 'where is my order?' You already know the answer most of the time. The tracking link is right there. But you are answering the same email 200 times while the rest of your support queue piles up. This is the setup I would use to handle that without hiring anyone.

Why WISMO Breaks Small Teams Every Q4

WISMO (where is my order) is the single highest-volume support category for any team shipping physical goods. The math is brutal. If you ship 1,000 orders over Black Friday weekend, expect somewhere in the range of 15-25% of them to generate a support contact within 7 days - that is 150-250 emails before you have even dealt with the wrong-item and damaged-goods tickets underneath them.

Most teams I have talked to try to hire one or two seasonal agents and still fall behind by Cyber Monday. The ramp time alone kills you. A new hire typically needs a week or two before they are useful, which means you needed to hire in October. Most people do not think about it until the first week of November.

The real problem is not volume alone. It is that WISMO tickets are repetitive enough to automate but high-stakes enough that a wrong reply destroys trust. A customer who got a generic bot response when their package was lost is not coming back. So you cannot just turn on auto-reply and walk away. You need a triage system that handles the easy stuff automatically, drafts the medium stuff for quick approval, and flags the real problems for a human.

This post is a step-by-step operational setup. Not a tool comparison. If you want a comparison of helpdesk tools, I wrote one at /blog/gorgias-alternatives-for-shopify. This is about the specific workflow I would build before November 1.

What Counts as a WISMO Ticket (and What Does Not)

Before you build any automation, you need to be precise about what you are actually automating. Not all order-status emails are the same.

Tier 1 is standard WISMO: the customer is asking where their order is, there is no carrier exception, and the package is in transit. Tracking exists. This is safe to auto-send.

Tier 2 is carrier exception WISMO: tracking shows delayed, stuck in transit, or returned to sender. The package is still moving or recoverable. Draft and approve before sending anything.

Tier 3 is delivered-not-received: tracking says delivered, customer says they never got it. Never auto-send. Human eyes only, every time.

Then there is everything that is not WISMO at all: refund requests, wrong item shipped, damaged goods. These need a human regardless of volume. Do not let them fall into your WISMO automation rules.

The distinction matters because auto-send is safe for tier 1, risky for tier 2, and wrong for tier 3. Build your rules around this and you will not accidentally send a cheerful tracking-link reply to someone whose package has been sitting in a Memphis facility for 11 days.

Build Your Knowledge Base Before November 1

The AI answers from your docs. That is the whole model. If your docs are vague, your replies will be vague. If your policy says 'ships fast,' the AI will draft replies that say 'ships fast.' That is not useful to anyone. So before you touch any automation rules, get the knowledge base right.

Here is what needs to be in there before peak season. First, paste in your full shipping policy with specific processing times and transit windows by carrier. 'Ships within 1 business day, USPS Priority 2-3 days, UPS Ground 3-5 days' is useful. Vague language is not. Second, add a carrier delay FAQ covering what happens when USPS or UPS shows a delay, what the customer should do, and when to contact you versus the carrier directly. Third, add your holiday shipping cutoff dates - exact dates for guaranteed pre-Christmas delivery by carrier. Customers ask this constantly in December. Fourth, if your carrier tracking page is public, import the URL directly.

One formatting tip that makes a real difference: write your shipping policy in plain Q-and-A format, not legal prose. 'Q: How long does processing take? A: We process orders within 1 business day, Monday through Friday.' The AI pulls cleaner answers from that structure than from a wall of paragraph text.

The Four Route Actions: Auto-Send, Draft, Human Review, Skip

Trigli's automation rules give you four route actions for incoming messages: auto_send, draft, human_review, and skip. Here is how I would map those to WISMO categories.

Auto-send is for standard in-transit WISMO where tracking exists and no exception is flagged. The AI replies with the tracking link and estimated delivery window. No human reads it first. This is only safe when your confidence floor is set correctly - below that threshold, nothing auto-sends regardless of what the category match says.

Draft is for when a carrier delay is flagged but the package is still moving. The AI writes the reply with the appropriate delay language, and you approve before it goes out. Takes 30 seconds to review. You stay in control without writing from scratch.

Human review is for delivered-not-received, returned to sender, or any email where the customer mentions a specific date they needed the package for (wedding, gift, event). A human checks the address, checks if a neighbor signature was captured, and decides whether to reship or refund.

Skip is for internal notifications, your own test emails, and known spam patterns. No action taken.

Draft-and-approve is the right default for most small teams during peak. You are not reading every email from scratch. You are reading a draft that is already 80% right and approving it or making a quick edit. That is a fundamentally different workload.

How to Set Up Automation Rules for WISMO (Step by Step)

Start by creating a WISMO category in your automation rules. This is the parent bucket everything routes into. Then set sub-categories: in_transit, carrier_delay, delivered_not_received, return_to_sender. Each gets its own route action.

Next, assign route actions by sub-category with priority ordering. carrier_delay should sit above generic in_transit in the rule order so the more specific rule wins when both could match. After that, set a confidence floor. Below that threshold, nothing auto-sends regardless of category match. This is your safety net.

Finally, test with 10-15 real past WISMO emails before going live. Check that routing is correct and that the drafts look right before November hits. Do not skip this step. Routing errors at peak volume are painful.

A concrete example: a rule that matches subject contains 'where is my order' OR 'tracking' AND sender is not an internal address routes to draft with your WISMO reply template. Simple. Specific. Works.

Writing the Three Replies You Will Actually Use

You need three core replies. Write them before October 31 and add them to your knowledge base so the AI has them as reference when drafting.

Reply 1 is for auto-send: in-transit, no exception. Short. Direct. Includes the tracking link. Sets a realistic delivery window. No apology theater. Something like: 'Your order is on its way. Here is your tracking link: [link]. Based on your location, you should see delivery by [date range]. Let us know if anything looks off.' That is it.

Reply 2 is for draft: carrier delay. Acknowledge the delay without being defensive. Give the customer the carrier exception language. Tell them what you will do if the package does not move in 48 hours. Honest. Not a wall of apology. Something like: 'Your package hit a delay with [carrier] - tracking shows it is still in transit but behind the original estimate. If it does not update in the next 48 hours, reply here and we will sort it out.'

Reply 3 is for human review: delivered-not-received. Do not write an auto-reply for this one. A human needs to check the delivery address, check if a neighbor signature was captured, and decide whether to reship or refund. This is where trust lives or dies. No template is going to save you here.

One thing that helps with tone: the AI learns from your past sent emails before drafting. So if your brand voice is casual and direct, the drafts will sound like you, not like a corporate support bot. Worth making sure you have at least 50-100 past sent replies loaded before peak so the AI has enough to calibrate tone from.

What to Do When Carriers Melt Down

Every Q4, at least one major carrier has a regional meltdown. USPS holiday delays. UPS surcharges causing reroutes. FedEx ground network backups. It happens every year and it will happen this year.

Pre-write a carrier delay bulletin and add it to your knowledge base before peak. Something that explains what customers should expect during high-volume periods, what your policy is when packages are significantly delayed, and what the process is for filing a claim if a package is lost.

Set a temporary rule for November 15 through December 31: all WISMO tickets route to draft instead of auto-send. A human glances before anything goes out. It adds maybe 20 minutes to your morning queue review, but it means you are not auto-sending 'your package is on the way' replies when half the network is backed up.

The One-Person Workflow for 300+ WISMO Emails

Here is what the actual day looks like when this is set up correctly.

Morning triage: review the draft queue, approve or edit in batches. If your rules are set correctly, this takes 20-30 minutes. You are not writing replies. You are reading drafts that are already 80% right and hitting approve or making a quick edit.

Midday check: scan the human review queue for anything flagged overnight. Delivered-not-received tickets, return-to-sender issues, anything with a hard date mentioned. These need real decisions. Budget 20-30 minutes.

End of day: check SLA alerts for anything approaching the overdue threshold. Nothing should be sitting unanswered for more than your stated response time. The SLA tracking will surface it before it becomes a problem.

The math: in my experience, most teams I have talked to see auto-send handling roughly 60% of WISMO volume and draft handling another 30% - though that split depends on how conservative you set your confidence floor. If those numbers hold, you are reading and approving roughly 90 emails instead of 300. Only 30 need real decisions. One person managing a 300-email WISMO flood in 1-1.5 hours per day instead of 6-8 hours. That is the difference between surviving Q4 and drowning in it.

Where This Setup Breaks Down (Be Honest With Yourself)

I am not going to pretend this handles everything. Here is where it falls short.

No live carrier data. The AI answers from your docs. If your docs do not have current carrier status, the AI cannot reference it. It will flag for human review, which is the right failure mode, but it still adds work. You have to update the docs when conditions change.

No native Shopify actions. The AI can reference your refund and shipping policies, but it cannot pull live order status from Shopify or process a refund inside Shopify. You still do that manually. If you want deeper Shopify integration context, the Trigli Shopify use case page at /use-cases/shopify covers what is and is not possible.

Reply threads. If a customer replies to an auto-sent email with a follow-up, that follow-up routes through your rules again. Make sure your rules handle reply threads correctly, or you will end up auto-sending a second reply to someone who just said 'thanks.'

Phone and SMS. If customers are calling or texting you, this setup does not touch that channel. Email and chat only. If a significant portion of your WISMO volume comes in via phone, you need a different solution for that piece.

Multi-carrier complexity. If you use four carriers with different tracking formats and different delay patterns, your knowledge base needs to cover all four. Gaps in the docs mean gaps in the replies. Write the docs once and write them thoroughly.

How This Compares to Hiring Seasonal Staff

A seasonal CX rep costs roughly $3,000-4,000 per month all-in when you factor in wages, onboarding time, and management overhead. They also need 1-2 weeks to ramp before they are useful. If you hire in early November, you are paying for a week of ramp time right when you need them most.

The automation setup described here takes a few hours to configure and is ready before peak. The math at Trigli's Growth plan ($149/month) covers 2,500 emails, which is more than most small teams will see even at Black Friday volume. The math is pretty one-sided, but I will let you run it for your own numbers. I wrote a more detailed breakdown at /blog/cost-of-support-rep-vs-ai if you want to do that.

Where a seasonal hire wins: if you are getting a lot of delivered-not-received claims that require judgment calls and negotiation, a good human rep handles those better than any automation. Same goes for situations where your product is complex and customers need real back-and-forth to resolve issues. And if a significant chunk of your support comes in via phone, a human is the only option - this setup does not touch that channel. The honest answer for most small teams is automation handling the repetitive 60-70% and one human handling the rest. That is not a knock on the technology. It is just accurate.

Quick Setup Checklist Before Black Friday

1. Knowledge base: paste in your full shipping policy with specific processing times and transit windows by carrier.
2. Knowledge base: add a carrier delay FAQ covering what customers should do when tracking shows an exception.
3. Knowledge base: add holiday shipping cutoff dates by carrier.
4. Automation rules: create a WISMO category with sub-categories (in_transit, carrier_delay, delivered_not_received, return_to_sender).
5. Automation rules: assign route actions by sub-category with priority ordering so specific rules win over generic ones.
6. Automation rules: set a confidence floor so nothing auto-sends below threshold.
7. Reply drafts: write three core WISMO replies (in-transit for auto-send, carrier delay for draft, delivered-not-received placeholder for human review).
8. SLA tracking: configure an overdue alert so nothing sits unanswered past your stated response time.
9. Test run: send 10-15 real past WISMO emails through the system to verify routing and draft quality.
10. Assign one person to the morning draft review queue with a 30-minute block on their calendar.

Honest Summary: What This Gets You and What It Does Not

What it gets you: WISMO volume handled at scale without seasonal hires, reply tone that matches your past sent emails because the AI learned from them before drafting, faster response times, and one person staying sane through Q4. The setup described here is not magic. It is just a well-configured triage system that stops you from reading every email from scratch.

What it does not get you: live order data from Shopify, phone or SMS coverage, automatic refund processing, or real-time carrier status. If those are hard requirements, be honest with yourself about whether this is the right fit.

Who this is right for: 1-30 person teams shipping physical goods who get hammered with WISMO every Q4 and cannot justify a seasonal hire. If that is you, the setup is straightforward and the cost is predictable. See the full pricing breakdown at /pricing.

Who should look elsewhere: teams needing deep Shopify integration with automated refund actions, or teams where most support comes in via phone. This setup does not solve those problems.

If the workflow described here sounds like what you need before November hits, the free tier at trigli.com is no commitment and takes about 5 minutes to connect your inbox. Worth getting it configured before the first wave lands.