On this channel, permission shapes the conversation before copy does. Message volume is rarely the real cause of a block or poor quality rating.1 The greater risk is contacting people who never gave clean, provable consent, then collecting blocks and reports that throttle the sender.2 Treat the channel as a permissioned conversation with an easy exit. The work is to qualify the right to message, preserve that decision, and make the exchange useful enough to continue.
Run the workflow
Use this sequence to decide whether you may message, preserve the decision, and run a useful conversation.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Permission | whether the person took affirmative action to receive communications3 | Did you actively choose to hear from us? |
| Identity | whether you have the mobile phone number and permission for later messages or calls4 | Do we have both the number and permission for later messages? |
| Proof | whether the agreement can be shown if challenged | "If a complaint lands, can we show the person actively agreed?"5 |
| Message | whether the exchange helps the person self-serve and get an answer6 | What resource or answer would help you move forward? |
| Exit | whether the recipient can opt out at any time7 | How can you stop receiving messages? |
Confirm permission
Make permission a hard gate. If the record fails, stop messaging and create a permission path before contacting the person.
The sender chooses the opt-in method and is responsible for obtaining consent in line with the laws that apply to the communication.8 Meta will not validate that consent for you.9 A list of phone numbers is not enough. Look for an active action from the person and a record that connects the action to your business.
Before sending, check the contact record for three things: the number, the action that expressed consent, and the wording the person agreed to. If one is missing, move the contact back to permission collection. Use the record rather than a salesperson's confidence.
Collect permission cleanly
Give the person a clear action and enough context to understand what follows. The collection channel can fit the buying journey when the action and wording are clear.
You can collect permission on a website, app, checkout page, in-store tablet, text reply, or QR code.10 Use the place where the person is already choosing how to hear from the business, then make the opt-in easy to find and complete.
Write the consent line so it names the business and clearly says that the person will receive messages from it. For a clean operational record, state that those messages will arrive through WhatsApp and require an active action.11 Keep the wording beside the action, so the person can see what they are agreeing to when they agree.
After collection, inspect the path as a recipient would. Can they tell who will message them? Can they tell that later communication will follow? Can you show the action they took? A yes to each question gives you a usable handoff into outreach.
Choose the confirmation path
Use the lightest path that leaves a clear record of the person's choice. Add a confirmation step when you want another deliberate signal before messaging.
Single opt-in uses one affirmative action, such as ticking a box, tapping a button, or sending a keyword.12 Double opt-in adds a confirmation step after that action.13 The sender asks people to confirm, then adds only contacts who confirm.14
Double opt-in is recommended as a best practice; Meta does not require it.15 Use single opt-in when the initial action is clear and the record is easy to retrieve. Use double opt-in when the extra confirmation will help filter uncertain contacts or make the permission trail easier to explain.
An extra confirmation does not fix weak wording. Before the request arrives, the person still needs to understand which business will communicate and what they are agreeing to.
Reuse permission across channels
Permission can carry across channels when the original request covers the communication you plan to send. Check its scope before treating it as a handoff.
An existing customer opt-in from another messaging channel can also be valid for WhatsApp, so an additional opt-in is not required under that platform rule.16 A general opt-in for marketing or service messages, collected on any channel, can satisfy the platform requirement when it meets the stated conditions and local law.17 A valid marketing opt-in does not become a blocker solely because it leaves out the word WhatsApp.18
That platform rule does not override data protection law.19 Review GDPR requirements before relying on a fully generic opt-in.20 Build the collection process so it can meet applicable law whenever required, then keep the wording and action available for review.21
For the workflow, ask what the person originally agreed to receive, who they agreed to hear from, and whether the intended message fits that permission. When the answer is unclear, collect a fresh, specific opt-in instead of stretching an old permission record.
Make the conversation useful
Once permission is settled, help the person make progress so they have a reason to reply. Make the message a useful buying interaction that lets the person continue without starting a sales process from scratch.
People want to self-serve. Salespeople still need to guide them to resources and answer questions.6 The channel can guide prospects quickly and answer questions when it is positioned appropriately for the buyer.22 Give a clear reason for writing, point to the resource that matches it, and leave room for the person to ask for help.
Recipients essentially receive direct customer support through the channel.23 Set your internal handoff accordingly. When a person replies with a question, answer it before adding another request. When they ask for a resource, send the relevant resource and let them decide whether to continue. Permission to start a conversation still requires you to address what the person asks for.
Keep exit and monitoring separate
Engagement tells you how a message was received. It does not replace the permission decision.
The channel lets salespeople see whether recipients opened and read messages.24 Use that signal to understand message reach. Attention does not establish consent. Keep the opt-out route visible in the message flow and act on it when the person uses it. A person who ends permission leaves the workflow, even if the message was previously opened.
Check the rules before launch
Review policy before launch. Recheck the exact wording, collection path, and exit process before the team starts sending, rather than waiting for a blocked account.
Policies and guidelines can evolve, so consult the current official business documentation for the latest opt-in requirements.25 Record the version of the process your team is using and revisit it when the policy changes.
What not to do
These shortcuts leave you with a number and no permission record.
- Do not treat a pre-checked box that the person must undo to decline as valid consent.26
- Do not treat a number collected from an order as permission to send WhatsApp messages.27
- Do not bury consent in Terms of Service acceptance when the wording says nothing about WhatsApp.28
- Do not use a number that was scraped, purchased, or imported from another platform as proof of consent.29
- Do not use generic wording such as "subscribe for updates" without naming the business.30