Preparing WhatsApp automation for peak season
Peak season does not break your automation. It reveals what was already broken, at ten times the volume.
Everything that goes wrong at peak season was already wrong in October. The volume does not create the problems; it removes your ability to absorb them by hand.
Which makes preparation mostly a matter of doing ordinary things early. This is the list, in the order the dependencies run.
Start with templates, because they gate everything
Approval is not instant and cannot be rushed on the day. Anything you intend to send during peak needs to exist and be approved well before it.
Meta caps templates at 250 per WhatsApp Business Account for an unverified business portfolio and up to 6,000 once verified, per its template documentation, so the constraint is rarely the number — it is the lead time.
| Template | Category | Have it ready because |
|---|---|---|
| Order confirmation | Utility | Volume goes up; manual confirmation stops being possible |
| Shipping notification | Utility | "Where is my order" scales with orders |
| Delay notice | Utility | Something will be late. Saying so first is the difference |
| The campaign itself | Marketing | Needs opt-in and approval, both in advance |
| Internal alert | Utility | Reaches your team's phones with no open window |
The delay notice is the one nobody prepares and everybody needs. Write it while you are calm.
Then check your reach
Your messaging tier caps how many unique recipients you can reach in a rolling 24 hours, and it runs 250 → 2,000 → 10,000 → 100,000 → unlimited under Meta's messaging limits documentation.
If your list is larger than your tier, discovering that on the morning of your campaign is a bad morning. Two things to do in advance:
- Check which tier you are on, rather than assuming.
- Build volume gradually beforehand with the ordinary utility messages you send anyway, so the ramp is not a single spike.
Tiers respond to sustained, good-quality sending. They do not respond to a plan to send a lot next week.
Protect the quality rating
This is the risk that carries past the season. Blocks and reports feed your quality rating; a poor rating can cut your tier, and the enforcement ladder runs from short restrictions to indefinite ones.
Peak season is exactly when stores send more marketing than usual to lists that opted in for something else, which is exactly the behaviour that produces blocks. Marketing templates also carry a per-user frequency limit that Meta adjusts and deliberately publishes no number for — so "how many is too many" is not a question with a documented answer, and the safe approach is a budget you set yourself.
Decide it before the season, in writing, and make every campaign respect it. The method is in a message frequency budget for stores.
Make the service side carry the load
The cheapest capacity you have is the conversation the customer starts. Service conversations have been free and unlimited since 1 November 2024 under Meta's pricing documentation, so every question your automation answers is capacity you did not have to buy or staff.
Three flows worth having live before peak:
- Order status answering, which absorbs the single largest category of peak questions.
- A knowledge base answer step covering delivery times, returns and your peak-season policies.
- Clear after-hours handling, because peak traffic does not respect your opening times.
All three exist to keep your team available for the conversations that need a person.
Write the peak-season answers now
Your standard replies stop being true during peak: delivery takes longer, the returns window may be extended, some things sell out. If your knowledge base says otherwise, your automation will confidently give customers the wrong answer at scale.
Update it before the season and diary a reminder to change it back. Stale peak-season copy running in February is its own small embarrassment.
Test everything, on a real phone
- Place a real order and follow it through confirmation, shipping and delivery.
- Ask your bot the five questions you expect most, and read the answers as a customer would.
- Try to reach a human. Time how long it takes.
- Send yourself the campaign template and check every variable resolves.
- Have a colleague reply mid-flow and confirm the bot stops talking.
An hour, and it catches the things that turn into a hundred conversations a day when volume arrives.
Have a plan for when something breaks
Because it will. The useful preparation is knowing in advance:
- Who can turn an automation off at 9pm on a Saturday.
- Which flow you would disable first if messages started going out wrong.
- What your delay message says, already approved.
- Where you look — each automation's activity view names the step that failed.
A store that can answer those four is in a materially better position than one that has more flows but no plan.
After the season
Two jobs, and both are easy to skip. Turn off anything seasonal, so no Black Friday message goes out in January. And read what happened: which questions spiked, where flows stopped, what your team ended up handling by hand.
That review is the cheapest source of next year's roadmap, and it is worth an hour while it is fresh — the mistakes it surfaces are usually the ones in the ten mistakes that cost stores sales.
Frequently asked
How far ahead should I submit templates?
Weeks, not days. Approval times vary and a rejection costs you another round.
Can I raise my tier quickly?
Not on demand. Tiers move with sustained sending and a healthy quality rating, which is why the ramp starts before the season and not during it.
Should I message my whole list?
Only the part that opted in, and only within a frequency budget you decided in advance. See opt-in rules for online stores.
What is the single highest-value preparation?
An approved delay-notice template and a working order-status flow. Between them they handle most of what peak season actually throws at a store.
A timeline that works backwards from the date
| When | What |
|---|---|
| Six weeks before | Submit every template you will need, including the delay notice |
| Four weeks before | Start sending your ordinary utility messages consistently, so the tier ramp is under way |
| Three weeks before | Update the knowledge base with peak-season delivery and returns answers |
| Two weeks before | Test every flow end to end on a real phone |
| One week before | Agree the frequency budget and who can turn things off |
| After | Disable seasonal flows, restore the knowledge base, read what happened |
Six items, none of them difficult, and the ordering matters because templates gate the campaigns and the tier ramp takes weeks rather than days.
What actually breaks under volume
- Manual steps. Anything a person does per order stops working at 10 times the orders.
- Flows with no failure path. A lookup that fails once a week fails hourly at peak.
- Free-form messages sent late. Outside the 24-hour window they silently do not arrive, and at peak nobody notices.
- Your team's patience. The bot that was mildly annoying in October becomes the reason a colleague turns it off.
Three of those four are design problems you can fix in an afternoon. The fourth is a reason to make sure the agent-message rule is installed, so a human reply always wins.
Marketing restraint, stated plainly
Peak season is when the temptation to message everybody is strongest and the consequences are largest. A blocked customer is not just this season's lost sale — blocks feed the quality rating that governs your reach for months afterwards.
The discipline that survives contact with a sales target: one campaign message per customer per week as a ceiling, sent only to people who opted in, and every send checked against the same budget. Nothing about that is novel, and almost every store that gets into trouble broke one of the three.
Capacity, honestly assessed
The question nobody asks until it is too late: how many conversations can your team actually handle in an hour, and what happens to the ones beyond that?
Automation raises the ceiling but does not remove it. Some proportion of peak conversations need a person — complaints, exceptions, anything about money — and that proportion is roughly stable however good your flows are. If your volume triples, the human share triples with it.
- Count what a normal week produces in conversations needing a person.
- Multiply by your expected peak factor.
- Compare against who is actually working those days.
- Close the gap with hours, not with more automation, because the gap is the part automation cannot take.
The alternative is discovering it live, which is how a good season becomes a bad reputation.
Seasonal flows need an off switch
Anything built for the season should be easy to disable, obvious in the list, and owned by somebody. The failure mode is a peak-season flow that nobody turned off, quietly greeting customers with a Black Friday message in February.
Name them so they stand out, and put the switch-off in the same diary entry as the post-season review. It takes a minute and it removes a whole class of small embarrassments — the kind catalogued in how many automations should a store run.