Your first 30 days on WhatsApp, in order
Four weeks, in order, with the reasoning for each step — and the things that look urgent and are not.
The commonest way to waste your first month on WhatsApp is to start with a campaign. It is the most visible thing you can do, it costs money on every send, and it is the flow most likely to damage the account health everything else depends on.
This is the order that works instead. It front-loads the free, welcomed flows, leaves the paid ones until you have something to send them to, and puts the two slow administrative tasks at the very start so they are finished by the time they would otherwise block you.
Day one: the two things that take days
Both of these run in the background while you do everything else, and both block you later if you leave them.
- Start business verification. It lifts your template ceiling from 250 to 6,000 and is the fastest route from a 250-recipient messaging tier to 2,000, per Meta's template and messaging limits documentation.
- Submit your two core templates — an order confirmation that asks Confirm or Cancel, and a shipping notification. Approval takes anywhere from minutes to more than a day.
Also decide, before connecting, whether anyone needs to keep replying from a phone — that choice is made inside Meta's signup window and cannot be changed afterwards. See keeping your number and your chats.
Week one: the free flows
Everything here runs on free-form messages inside the 24-hour customer service window, so none of it costs a per-message fee. Meta's pricing documentation confirms service conversations have been free and unlimited since 1 November 2024.
| Build | Why first | Effort |
|---|---|---|
| Stop the bot when a human replies | Prevents the worst experience your bot can create | 2 minutes |
| Welcome message with a three-option menu | Routes everything else | 20 minutes |
| After-hours reply naming a reopening time | Removes the "is anyone there?" follow-up | 15 minutes |
| Keyword flows for your top three questions | Built from your own inbox, not guesses | 1 hour |
The first one is genuinely two minutes and it is the single highest-return thing on this page — without it, a customer's reply to your colleague gets captured by a bot waiting for an answer.
Week two: answer the repeated questions
By now you have a week of watching the inbox, which tells you what to automate far better than any list would.
- Build a knowledge base from your existing policy pages — shipping, returns, sizing — plus written answers for anything your site does not cover. Wire the "unanswered" branch to a person.
- Add order-status answering. "Where is my order?" is the most repeated question in ecommerce and it is answerable from a Google Sheet on day one.
- Read your keyword lists again and add the phrasings customers actually used, including transliterated ones if that is your market.
Week three: the order flows
Your templates should be approved by now. This is where the money starts.
- Order confirmation that asks rather than announces. In cash-on-delivery markets this is the highest-value automation that exists, because it catches a bad order before you pay a courier. Everywhere else it still earns its place, because the customer's tap opens a free 24-hour channel.
- Address verification in that same conversation — free, and it catches a failure mode nobody sees coming.
- Shipping notification with tracking, written so it still sends correctly when a fulfilment has no tracking number.
Watch each one's activity view for the first day rather than your inbox. A flow that never runs is far commoner than one that misfires.
Week four: measure, then and only then market
- Tag every link your flows send with UTM parameters, or your store analytics will file WhatsApp traffic as "direct" and tell you the channel earns nothing.
- Check your quality rating and your messaging tier.
- Now consider your first campaign or a cart-recovery flow — with marketing consent collected separately from order-update consent.
What to deliberately leave alone in month one
| Leave | Why |
|---|---|
| Broadcast campaigns | Charged per recipient, and account health is not established yet |
| Abandoned cart recovery | Marketing: charged, capped, and undeliverable to US numbers |
| Importing an old contact list | The fastest route to blocks and a damaged quality rating |
| Chasing the green tick | Meta grants it on its own assessment; it cannot be applied for |
| Building one template per product | Variables exist so you do not have to |
| A ten-option menu | WhatsApp allows three buttons; three options covers most enquiries |
What good looks like at day 30
- Business verified, so your tier and template ceiling are no longer the constraint.
- Five or six flows live, four of which cost nothing to run.
- The repeated questions answered without a person.
- Order confirmations catching problems before you ship.
- Links tagged, so next month's numbers mean something.
- Quality rating green, and one marketing flow at most.
That store is in a far better position than one which spent the month building campaigns, because it has the free half working and an account healthy enough to scale the paid half onto.
Why this order and not another
Three principles underneath it, worth stating because they generalise beyond the first month:
- Free before paid. Utility and service messages are free inside an open window, welcomed by customers, and deliverable everywhere. Marketing is charged, capped and regionally restricted.
- Slow tasks first. Verification and template approval take days. Starting them on day one means they are never the thing blocking you.
- Measure before you scale. A month of sending with untagged links produces no usable information about what worked.
The wider argument for how many flows to run at all is in how many automations a store should run, and the first build itself in building your first automation.
A one-page checklist
| When | Do | Cost to run |
|---|---|---|
| Day 1 | Start business verification | Free |
| Day 1 | Submit order-confirmation and shipping templates | Free to submit |
| Day 1 | Complete your business profile — logo, description, website, hours | Free |
| Week 1 | Cancel-pending-question flow | Free |
| Week 1 | Welcome menu, three options | Free |
| Week 1 | After-hours reply with a real reopening time | Free |
| Week 2 | Knowledge base from your policy pages | AI usage only |
| Week 2 | Order-status answering | Free |
| Week 3 | Order confirmation that asks Confirm / Cancel | 1 template per order |
| Week 3 | Address check, in the same conversation | Free |
| Week 3 | Shipping notification | 1 template per order |
| Week 4 | Tag every link with UTM parameters | Free |
| Week 4 | Review quality rating and tier | Free |
Nine of those thirteen cost nothing to run. That ratio is the point of the sequence.
If you only have one afternoon
- Start business verification — it runs in the background.
- Build the cancel-pending-question flow. Two minutes.
- Build the after-hours reply with a real reopening time.
- Complete your business profile.
Those four remove the worst experiences a new setup produces, cost nothing, and leave the slow administrative task already running.
Month two, briefly
Once the free half is working and your rating is green, the natural additions are a review request after delivery, cart recovery if you sell prepaid, and your first segmented campaign. Add one at a time and watch the effect — how many automations a store should run covers the budget, and Meta's template documentation the ceilings you are working inside.
The three mistakes that cost a first month
- Leaving business verification until it blocks you. It takes days, and it is the constraint behind both your template ceiling and your messaging tier. Starting it on day one costs nothing and removes the commonest launch-week surprise.
- Building a campaign before a confirmation flow. The campaign costs money per recipient and depends on account health you have not built yet. The confirmation flow is nearly free and catches problems before you ship.
- Not watching the activity view. A new flow that never runs is far commoner than one that misfires, and the cause is almost always a keyword list built from imagination rather than from your own inbox.
How to tell it is going well
Four signals, none of which is message volume:
- Your team is answering fewer repeated questions than a month ago.
- Order confirmations are getting responses — and some cancellations, which is the flow working rather than failing.
- Quality rating is green and your tier has moved.
- Your message spend is small, because most of what you send sits inside open conversation windows — which Meta's pricing documentation makes free.
If all four are true at day 30, the foundation is right and month two can safely add the paid flows.
And resist adding a flow just because you read about it. Every automation you publish is another message a customer may receive and another thing you have to maintain — the stores that do well on this channel in month one are the ones running five flows properly rather than fifteen approximately.
If you follow nothing else here, follow the ordering principle: build the free flows before the paid ones, start the slow tasks on day one, and tag your links before you need the numbers. Those three decisions shape month two more than anything you actually build in month one.
Frequently asked questions
What should I automate first on WhatsApp?
The two-step flow that stops the bot when a human replies — it takes two minutes and prevents the worst experience your bot can create. Then a welcome menu and an after-hours reply, both of which are free to run.
When should I send my first campaign?
Week four at the earliest. Campaigns are charged per recipient and depend on account health you have not established yet, so the free utility flows should be working first.
What should I do on day one?
Start business verification and submit your two core templates. Both take days, and both block you later if left — verification alone lifts your template ceiling from 250 to 6,000.
Should I import my existing customer list?
No. Messaging people who did not meaningfully opt in produces blocks and reports, which damage the quality rating that caps how many people you can reach at all.