WhatsApp Business Automation: What to Know First

WhatsApp is the channel most businesses ask about first, and the one with the most rules attached. Before choosing a tool it is worth understanding what automation on Meta's messaging channels actually permits, because the constraints are the same whoever you buy from, and most of the disappointment comes from not knowing them in advance.

The rule that shapes everything: the 24-hour window

On Instagram, Messenger and WhatsApp, a business can message a person freely for 24 hours after that person's last message. Once the window closes, what you can send is restricted. Every automation you design sits inside that: an unanswered question at hour 25 is not a scheduling problem, it is a platform boundary.

The practical consequence is that automation on these channels is about answering quickly and completely, not about broadcasting whenever you like. Speed is the whole game: a reply inside a minute buys you the remaining 23 hours and 59 minutes to finish the conversation properly: /help/messaging-rules.

It also explains why automation and a human inbox belong together. The window does not care whether the last message came from a bot or a person, so the handover has to happen inside it rather than in tomorrow's to-do list.

Where MuChat stands today

Messenger and WhatsApp support is built, and waiting on Meta's approval. We are not going to give you a date, and you should be wary of anyone who does: approval timelines are not ours to promise, and a tool that guarantees one is describing a hope as a commitment.

What is live today

• Instagram DMs: comment-to-DM, story replies, keyword triggers, flows, sequences, broadcasts and a shared inbox.
• Telegram: connect a bot token from BotFather and run the same automations, with no 24-hour window.
• SMS: send from your own Twilio number, with buttons converted to reply options and STOP and START handled by Twilio.

TikTok is worth naming because people ask: its messaging API is partner-only, so no tool can offer you TikTok DM automation today, whatever a marketing page says.

Designing automation that survives the window

1. 01Answer the actual question in the first message, not a greeting that spends the window saying hello.
2. 02Ask at most one thing per message. Two questions in one message get one answer.
3. 03Get to the outcome inside the conversation: the booking, the link, the order lookup.
4. 04If a human needs to take over, hand off inside the window rather than promising a callback outside it.
5. 05Write the last message so the thread can end cleanly, rather than trailing off mid-process.

Opt-in is the other half

On Meta's channels the person starts the conversation. That is not a limitation to route around; it is what makes these channels work. A list built from people who messaged you is small and warm, and it behaves nothing like a bought list. Designing for that reality produces better automation than treating the window as an obstacle.

The same flow, different channels

A flow built in MuChat is not channel-specific in its logic. The differences are presentational: buttons where the channel supports them, written-out reply options where it does not. Each automation runs on one channel, but the steps are the same everywhere, so what you learn building on Instagram carries straight over when other channels open up: /product/flow-builder.

It also means you can test copy where you already have traffic. The wording that works in an Instagram DM is usually the wording that will work on WhatsApp, and you can learn it this quarter rather than after an approval lands.

What to build while you wait

If WhatsApp is where you eventually want to be, the work that transfers is the content rather than the configuration. The answers to your twenty most common questions, the qualifying question that actually sorts enquiries, the wording that gets a reply: all of that is channel-independent, and you can learn it now on a channel that is open.

Businesses that arrive at a new channel with those answers already written get value from it in days. Businesses that arrive with an empty flow builder spend the first month discovering what to say, which is the expensive part.

One inbox, whichever channel they use

However many channels you end up running, the practical constraint is human attention. Threads from every connected channel land in the same inbox, and each one says which account it came in on, so answering is one queue rather than three tabs. That matters more as channels multiply, because the window that closes first is always on the channel nobody was watching: /product/inbox.

Questions worth asking any vendor

• Which channels are live for my account today, not in general?
• What happens to my flows and contacts if a channel is not approved?
• How does the tool behave when the 24-hour window closes mid-conversation?
• Who owns the phone number or account the messages go through?

The answers matter more than a feature list, because they describe what happens when something does not go to plan, which is the part you will actually live with.

Choosing a channel honestly

Pick the channel your customers already use to contact you, rather than the one with the best automation story. A well-answered Instagram DM beats a beautifully engineered WhatsApp flow that nobody messages. If that is Instagram, start there: /product/instagram, and /templates has flows to begin from.