A broadcast is usually planned down to the image and the send time, while the replies it triggers are left to whoever happens to be online. WappBlaster treats the reply as the start of a second, designed journey: buttons that route people to the right place, a bot that collects the basics, and a person who picks up with the full thread in front of them. This article walks through how to plan that journey before the campaign goes out.
Map the two-way journey before you write the template
Take a real example: a coaching institute in Kota broadcasts a new weekend batch to past enquirers. Before writing the message, the team lists what people will say back:
- "What is the fee?"
- "Is there an online option?"
- "Can I talk to someone?"
- "Not interested" or "Stop".
- Something unexpected: a question about a refund from last year, a parent asking on a child's behalf.
Each of those needs an owner and a response. The first three become quick-reply buttons on the template itself (three is the maximum), and the last two need a route to a person and a working opt-out.
Using buttons to sort intent at the first tap of a WhatsApp journey
Free text is hard to route. A tap is easy. Button labels such as "Fee details", "Online batch" and "Call me back" let the journey branch from the first interaction without anyone reading the message. Each button starts a different path in the automation builder:
- Fee details: the bot sends the fee PDF and asks whether the student wants the weekday or weekend timing, as a list.
- Online batch: the bot shares the schedule and a demo-class link, then tags the contact "online-interest".
- Call me back: the bot asks for a preferred time and assigns the chat to a counsellor.
Once the customer has replied, the 24-hour customer service window is open, so these follow-ups can be free-form messages, lists and buttons rather than more templates.
Handing over a WhatsApp journey without making people repeat themselves
The worst moment in a two-way journey is a counsellor opening with "How can I help you?" after the student has already answered four questions. Set the handover so that the bot's answers land as tags and custom fields on the contact, and the full thread stays visible in the shared team inbox. The counsellor's first message then picks up from what is known: "You asked about the weekend batch and evenings after 6 work best; I can hold a seat for Saturday's demo."
Assignment rules matter at volume. Route by city, course or language so the right person gets the chat, and use internal notes when a senior needs to step in without the customer seeing the discussion.
Finishing the two-way journey inside the window
Each customer message resets the 24-hour window. If a chat goes quiet and the window closes, the next outbound message must be an approved template, which is both a cost and a cold restart. So staff the inbox for the hours after a send, schedule campaigns when your team is on shift, and avoid launching a broadcast at 6 pm on a Friday. Meta has also announced that replies inside the window become billable from 1 October 2026; our explainer on service message pricing from October 2026 sets out what that changes. Complete answers in fewer messages are the sensible response either way.
Marking the outcome on every two-way WhatsApp thread
| Outcome | Action in the inbox | What happens next |
|---|---|---|
| Enrolled or bought | Tag "converted", resolve | Moves to onboarding drip |
| Interested, not ready | Tag with month to follow up | Enters a later trigger campaign |
| Not interested | Resolve with reason | Excluded from this offer's reminders |
| Opted out | Automatic suppression | No further marketing |
Those resolution states are what turn a campaign's replies into numbers a manager can review the next morning. The platform side is a flat ₹7999 annually for Indian businesses, $200 for others, and Meta's per-message charges come through at cost, itemised.
Two-way journeys that waste the reply
- A bot with no "talk to a person" path, so anyone with an unusual question gives up.
- Sending 5,000 messages when two people are on shift to answer them.
- A twelve-step bot menu that asks for details the CRM already holds.
- Treating "Stop" as a conversation to argue with rather than an instruction.