.png)
A useful WhatsApp marketing campaign starts with a specific customer need and one clear next action. Decide what the recipient should be able to do, confirm that they have agreed to hear from the business on WhatsApp, choose a message format that explains the offer, test the complete journey, and measure only outcomes the business can actually observe. The campaign is ready when the message is expected, relevant, easy to understand and connected to a working next step.
This guide is about planning. It does not promise a particular response rate or replace current platform or legal requirements. WhatsApp’s own policy says businesses may contact people only when they have their number or username and opt-in permission; platform rules also govern business-initiated templates, replies and opt-outs. Check the current WhatsApp Business Messaging Policy before launch. If your team needs a permission-led campaign workflow, SMSNiti’s WhatsApp marketing service is the relevant service path; confirm the current scope before planning delivery.
1. Choose one customer action before writing
Start with the moment that makes the message useful. A retailer may want a customer to view a new collection; an event organiser may need an RSVP; a service team may want a customer to select an appointment slot. These are examples of possible workflows, not promises of results. Write the action as a verb and a destination: “choose a time on the booking page” is more useful than “engage with our brand.”
Then answer four questions in a short brief:
What situation makes this message relevant now?
What information does the recipient need to act confidently?
What exact button, reply, link or human contact will complete the action?
What evidence will show that the action happened?
If the team cannot identify a useful reason for contacting this audience today, pause. A calendar slot or unused content asset is not, on its own, a customer benefit. The campaign should solve a real information or decision problem for the recipient.
2. Define the audience and its permission record
Build the audience from a documented source, not from every phone number the organisation has collected. Record how each person entered the list, what they agreed to receive, when and where permission was captured, which business or brand it covered, and how the person can stop future messages. Remove anyone whose permission or identity is uncertain. A customer relationship does not automatically mean that every later promotional message is expected.
WhatsApp’s policy requires businesses to have the person’s number or username and opt-in permission for subsequent messages or calls. The policy also says businesses must respect requests to block or discontinue communication, including requests made outside WhatsApp. Keep the opt-out path visible and make the suppression process available to campaign operators. Do not treat a reply to one service question as blanket permission for unrelated marketing.
Where a team is combining WhatsApp with SMS or voice, keep the channel rules separate. TRAI’s sender guidance describes Indian telecom requirements for bulk SMS and calls, including sender registration and other applicable setup. Confirm the exact workflow with the responsible access provider; do not apply SMS rules by assumption to WhatsApp or assume WhatsApp permission satisfies a separate channel’s requirements. See TRAI’s advice to senders when a telecom channel is part of the plan.
3. Pick the right WhatsApp workflow
Choose the operating route only after the audience and action are clear. A small team answering individual incoming conversations may have different needs from a team coordinating campaigns, templates, shared inboxes or connected systems. The WhatsApp Business app and WhatsApp Business Platform are different products with different operating models. Evaluate the actual number of staff, message types, approval steps, integrations, reporting requirements and available support rather than selecting a platform because the campaign is labelled “large.”
For the Business Platform, the current policy says businesses may initiate conversations only with approved message templates, and that outside the customer service window, business-initiated messages must use approved templates. The policy describes a 24-hour customer service window that opens or resets when the user messages the business. Check the live policy and current product documentation before designing an automation; product rules can change.
If the campaign requires several teams to handle replies, design an escalation path before sending. Decide which questions can receive an automated acknowledgement, which need a trained person, how quickly someone should take ownership, and what happens outside working hours. A campaign with a reply button but no staffed destination can create a worse experience than a simple message with a clear self-service link.
4. Write for the screen and the decision
Structure the message in this order: identify the business, explain why the recipient is receiving it, state the useful information, then show one primary action. The first sentence should make the context clear even if the recipient does not read every line. Avoid vague openers such as “Big news!” when the reader needs to know what changed or why it matters.
Keep the choice small. If there are multiple products, eligibility conditions or dates, link to a page that explains them rather than compressing complex terms into a chat bubble. Use a button label that describes the destination or action, such as “View available slots,” instead of “Click here.” If a reply is expected, tell people what response is useful and ensure someone is responsible for reviewing it.
Before sending, compare the message with the landing page. Confirm that the price, offer, dates, stock or eligibility statements are accurate and consistent. Check that the link opens on a phone, the page loads without a login surprise, and the requested action can be completed. Do not use false urgency, invented scarcity or unsupported outcome claims.
5. Set a sensible schedule and frequency
Choose timing based on the event and the recipient’s ability to act, not simply on a claimed “best time” statistic. A booking reminder must arrive while there is still time to change the booking. A launch announcement should be sent only when the destination is ready. A follow-up should add information or answer a likely question; repeating the same pitch is not a useful sequence.
Set a campaign-level contact rule before sending. Check how many other messages the person may receive from the business through the same channel, including service notifications and messages from other teams. Define a quiet period, a maximum number of marketing touches for this campaign, and a stop rule for people who have already completed the action. Keep channel preferences and opt-outs current across the workflow.
6. Test the whole journey before release
Prepare a test checklist that covers the actual audience segment, approved message version, template status where relevant, button labels, links, tracking, business identity, language variants and escalation path. Preview the message on a phone. Review names and variable fields for blanks, unusual lengths, punctuation, regional language and incorrect personalisation. A test message should go only to authorised test recipients.
Assign clear owners: the campaign owner confirms purpose and audience; the content approver checks the message and landing page; the platform operator checks configuration and template status; and a named release owner makes the final go or no-go decision. In a small business, one person can hold several roles, but the checks should still be explicit.
Use a stop condition. Pause if the opt-in evidence is incomplete, the selected audience differs from the approved group, the message is not approved, the destination is broken, the offer changed after approval, or no one owns replies. Write down the correction and rerun the affected checks before launch.
7. Measure the action, not a vanity number
Decide what will be measured before the campaign begins. Depending on the systems used, a team may be able to observe sends, delivery status, button interactions, link visits, replies, completed bookings or sales. Each metric means something different. A message marked delivered does not prove that it was read, understood or acted on. A click does not prove that a purchase or booking was completed.
Use a tagged destination link only if the business has a valid way to analyse it and the setup respects its data practices. Agree on the reporting owner, time window and definition of success. If attribution is incomplete or other channels contributed, say so in the review rather than assigning all change to the WhatsApp campaign.
After the campaign, compare the observed outcome with the original objective. Record what recipients asked, where they dropped out, whether the action path worked, whether opt-outs or complaints changed, and which operational step should change next time. Do not invent a benchmark when no reliable comparison exists. Keep the learning specific: for instance, “the booking page lacked a clear reschedule path” is actionable, while “WhatsApp works better” is not.
A practical campaign planning checklist
One customer need and one primary action are written down.
The audience source and WhatsApp opt-in are documented; uncertain contacts are excluded.
The product route, template or customer service workflow is checked against current WhatsApp documentation.
The message identifies the business, explains the context and uses one clear action.
The linked destination is accurate, mobile-friendly and ready to receive the visitor.
Frequency, quiet periods, opt-outs, monitoring and human escalation have named owners.
Tests cover message rendering, links, variable fields and the reply path.
Success measures are defined with limitations before release.
Frequently asked questions
Can a business message anyone whose number it has?
No. WhatsApp’s policy requires the business to have the person’s number or username and opt-in permission for subsequent messages or calls. A number in a CRM is not proof of permission for this WhatsApp campaign.
Can every campaign start with a free-form message?
Do not assume so. WhatsApp’s current policy says business-initiated conversations on the Business Platform use approved message templates, and messages outside the customer service window require approved templates. Confirm the current rules and template status before launch.
Should every WhatsApp campaign include a button?
No. Use an interactive control only when it makes the next step clearer and the selected route works. A simple link or reply instruction may be more suitable for some messages.
How often should a business send marketing messages?
There is no single frequency that fits every audience. Set a conservative contact plan, consider the customer’s expectations and other messages from the business, monitor feedback and reduce or stop messages when people opt out or the content is no longer relevant.
Plan the channel around the customer journey
For details of SMSNiti’s current WhatsApp campaign service, confirm the current scope with the provider. For a second-channel planning comparison, see the existing bulk SMS campaign planning guide; the channel-specific permissions and setup differ, but both workflows benefit from a clear brief, test and measured review. Use the service pages to confirm current scope, then build the brief around your own audience permissions, customer action, response ownership and measurement plan. For the product decision behind an API-led workflow, read our WhatsApp Business App versus Platform guide. If the campaign needs to qualify enquiries through a conversation, see the WhatsApp lead qualification conversation map.
