Opt-in and GDPR on WhatsApp Business: how to write without burning the number
What counts as consent to message people on the WhatsApp Business API, sample wording to ask for it, how to store it, how to handle opt-outs and what not to do.
The WhatsApp Business API is not a channel for dumping the sales rep's spreadsheet. Consent is the difference between a campaign that arrives and a number limited within three days.
This guide is practical, not a legal opinion. If you send at volume or handle sensitive data, have your lawyer or data protection officer review it. The legal references are European and, where noted, Spanish.
Two layers you must not mix
- Meta's rules. To message someone on WhatsApp, that person must have agreed to receive messages from your business on this channel. Meta also measures how recipients react: blocks and reports lower the number's quality rating.
- The law. In the EU, GDPR governs how you process the data, and e-privacy rules govern electronic marketing. In Spain those are the LOPDGDD and the LSSI.
You can pass one and fail the other. Perfect consent does not stop Meta limiting you if people block your messages, and a template approved by Meta is not a legal basis in front of a regulator.
Service and marketing are not the same
| Message type | Examples | What it needs |
|---|---|---|
| Service or utility | Confirming an appointment, a shipping notice, answering an enquiry | A prior relationship: the customer asked for or bought something |
| Marketing | Offers, news, win-back, cross-selling | Specific consent for commercial messages |
Spanish law (LSSI) has an exception for existing customers and products similar to those they already bought, always with an opt-out in every message. It is a narrow exception. If you are unsure whether a send fits, treat it as marketing and ask for consent.
What counts as opt-in
- An unticked checkbox on a form: "I want to receive news and offers on WhatsApp".
- A reply in the chat itself: "Reply YES if you want us to tell you about new intakes".
- A voluntary sign-up from a QR code or link that explains what they are joining.
What does not count: a generic mention in the terms and conditions, a bought database, numbers scraped from the internet, or the business card someone handed you at a trade fair years ago.
Someone writing to you on WhatsApp lets you reply to them. It does not authorise you to add them to campaigns.
Sample wording to ask for it
On a web form
I agree to receive commercial information from [Company] on WhatsApp. I can unsubscribe at any time by replying STOP.
A separate checkbox from the privacy policy, unticked by default.
In the chat, after resolving an enquiry
Would you like us to let you know here when we have news about [topic]? Reply YES and we will add you. You can unsubscribe whenever you like.
On a QR code in store
Scan and send JOIN to get our offers on WhatsApp. Two messages a month at most.
Stating frequency and topic helps twice: the consent is clearer and there are fewer blocks later.
How to keep the proof
Consent you cannot demonstrate does not exist. Each contact record should show:
- Date and time of sign-up.
- Source: form, chat, QR, ad.
- The wording they accepted.
- Scope: which kind of messages.
If you work with HubSpot or Pipedrive, that data has to travel to the CRM in its own field, separate from email consent. In ManyContacts it is stored with tags and custom fields, and the conversation itself is the proof when sign-up happened in chat.
Opt-outs that work the same day
- Marketing templates should offer a clear way to unsubscribe: a button or a keyword.
- The opt-out applies immediately, not "at the next database update".
- Opting out of marketing does not stop service messages: if they have an appointment, they still get the reminder.
- The rep does not write again "just in case". That is the message that ends in a complaint.
The 24-hour window is not permission
When a customer writes to you, the 24-hour window opens and you can reply in free text. It is a technical Meta rule about how you reply, not consent for campaigns. After that, any message you start is a template, and if it is commercial, it needs opt-in.
Checklist before a campaign
- Does every recipient have a recorded marketing opt-in, with date and source?
- Is the template approved in the right category?
- Does it include a way to opt out?
- Is the segment relevant to the message?
- Is someone ready to answer the people who reply?
If the first answer is "I don't know", stop. A campaign to a list without consent is the fastest way to lose the number. How to plan sends is in WhatsApp marketing campaigns.
Frequently asked questions
Can I message my existing customers on WhatsApp?
For matters related to what they have bought, yes. For offers, the safe route is to have their consent. The similar-products exception in Spanish law is limited and requires an opt-out in every message.
Does my email consent cover WhatsApp?
No. Agreeing to commercial emails is not agreeing to WhatsApp. You have to ask for this channel.
Can I use a bought database?
No. It breaches Meta's policy and you are unlikely to have a valid legal basis. It is also the kind of send that generates the most blocks.
What happens if I send without opt-in?
On Meta's side, blocks and reports lower the number's quality and can end in limits or restrictions. On the legal side, you are exposed to complaints to the data protection authority.
Next step
Review your last campaign: can you point to the opt-in for every number? If not, it is time to tidy the database before the next send. You can create an account or book a demo to keep consent next to each conversation.