WhatsApp opt-in: collecting consent that protects your number
Blocks are the fastest way to lose a WhatsApp number. Consent is not paperwork — it is the mechanism that keeps your messages delivering.
Businesses treat consent as a legal box to tick. On WhatsApp it is closer to an operational control: it is what stands between you and the block rate that gets your number restricted.
Why blocks matter more than anything else
Meta scores your number with a quality rating driven largely by how recipients react. Blocks and "report spam" taps push it down. A low rating reduces how many people you may message per day, and sustained problems can restrict the number entirely.
The chain is short and unforgiving: message people who did not ask → they block you → your rating falls → your limit drops → the number you built your customer service on stops working.
Consent is how you break that chain at the first link.
What counts as opt-in
Meta requires that people have agreed to hear from you on WhatsApp specifically, and that you can demonstrate it. Three practical requirements:
- It names WhatsApp. Agreeing to "receive updates" is not agreeing to WhatsApp messages. Say the channel.
- It names you. The customer should know which business will be messaging them.
- It is recorded. When, where, and what wording they agreed to.
A pre-ticked box is not consent. A phone number entered to complete a purchase is not consent to marketing. A list bought from anyone is not consent, and is the fastest route to a restricted number.
Where opt-in actually comes from
In practice, four sources cover most businesses:
- The customer messages you first. The strongest form there is — they initiated it, and it opens the 24-hour window.
- A website chat widget that asks for a WhatsApp number with a clear line about what you will send.
- Checkout, with an unticked box: "Send my order updates on WhatsApp."
- In person, a QR code that opens a chat. Scanning and sending is unambiguous.
Note the separation worth keeping: consent to order updates is not consent to promotions. Record them as two permissions. It costs a checkbox and saves your rating.
Wording that works
Weak: "Sign up for updates."
Strong: "Send me order updates and offers from Al Noor Electronics on WhatsApp. You can reply STOP at any time."
It names the channel, names the business, says what will arrive, and shows the way out. That last clause reduces blocks measurably, because a customer who knows they can leave easily reaches for STOP rather than Block.
Honour the exit immediately
When someone opts out, stop — that day, not at the end of a campaign. If your system cannot suppress a contact instantly, that is a defect worth fixing before your next send.
Keep the record of the opt-out too. Being able to show when someone left is as valuable as showing when they joined.
Data protection sits on top
Meta's rules are the operational layer. The legal layer depends on where your customers are — the UAE, Saudi Arabia, the EU and India all have their own regimes, and several require a lawful basis for processing, a retention period, and a route for someone to request deletion.
The overlap is convenient: the record that satisfies Meta — who consented, when, to what, and when they left — is broadly the record a regulator expects. Keep it once, properly.
A workable standard
- Never message someone who has not asked, on any channel.
- Store the timestamp, the source and the exact wording shown.
- Track marketing consent separately from service messages.
- Put an opt-out in every marketing template and honour it same-day.
- Watch your quality rating weekly; treat a drop as a message-quality problem, not a bad-luck problem.
None of this is expensive. It is considerably cheaper than losing the number your customers already have saved.
Run all of this from one inbox
Flas CRM gives your team a shared WhatsApp inbox, template management, lead capture and invoicing in one workspace. One month free.