Building a WhatsApp Opt-In List the Right Way
The fastest way to get a WhatsApp number into trouble isn't sending too many messages — it's sending them to people who never asked to hear from you. One "who is this?" is harmless. A hundred of them, plus a few "Report" taps, and WhatsApp's spam signals start treating your number like a stranger blasting strangers. Deliverability drops, then the number does.
The fix is upstream of any send tool: a WhatsApp opt-in list built from people who actually chose to be on it. Get consent right and your broadcasts land in chats that are already warm, your block rate stays low, and your number stays healthy. Get it wrong and no amount of clever copy saves you.
This guide is for anyone planning to broadcast — D2C, real estate, clinics, coaching, agencies — who wants a list that performs and keeps them out of trouble. We'll cover what counts as a real opt-in, where to collect it, how to keep it clean, and the consent records worth holding onto.
What "opt-in" actually means on WhatsApp
An opt-in is a clear, specific yes: the person knowingly agreed to receive WhatsApp messages from your business about a stated thing. BLUF — if you can't point to the moment someone said yes, you don't have consent, you have a phone number.
Three things separate a real opt-in from a scraped contact:
- It's affirmative. They took an action — ticked a box, sent the first message, typed a keyword. Silence and "they didn't object" are not consent.
- It's specific. They agreed to WhatsApp messages, not just "marketing". A newsletter signup three years ago is not a WhatsApp opt-in.
- It's scoped. They know roughly what they're signing up for — order updates, offers, class reminders — and your sends stay inside that scope.
The contacts you bought, scraped from a directory, or pulled from a group you're a member of are not opted in. Messaging them cold is exactly the pattern WhatsApp's filters are built to catch, and the one that gets numbers restricted. If you're unsure whether your sending plan is safe, our guide on whether bulk WhatsApp is safe walks through the line between fine and risky.
Where to collect opt-ins (ranked by signal quality)
Not all yeses are equal. The strongest opt-ins come from people already in motion toward you. Use several of these so the list grows from genuine intent, not a single scraped dump.
| Source | Why it's strong | Watch out for |
|---|---|---|
| Customer at checkout / signup | Highest intent — they're already transacting | Make the WhatsApp opt-in separate from the purchase tick |
| Click-to-WhatsApp button | They started the chat = clear inbound consent | Set expectations in your first reply |
| "Send START to subscribe" keyword | Explicit, logged, self-selecting | Confirm the subscription so it's unambiguous |
| Website form with a WhatsApp checkbox | Captures intent before they're a customer | Box must be unticked by default |
| In-store QR / event signup | Warm, in-person consent | Note where/when it was collected |
| Lead ads (Meta) | Inbound and pre-qualified | Still confirm the WhatsApp opt-in on first contact |
Let them start the conversation
The cleanest opt-in is the one they initiate. A click-to-chat link on your site, a "Chat on WhatsApp" button under a product, a QR at the till — when someone taps it and messages you first, that inbound is consent you can stand behind. Reply with a one-line note on what they'll get ("We'll send order updates and the occasional offer — reply STOP anytime") and you've closed the loop honestly.
Use a keyword to make it explicit
"Send JOIN to 98xxxxx to get launch alerts" turns a vague interest into a logged, deliberate action. The person typed the word; you have a timestamped message proving it. Keyword opt-ins are the easiest to defend later because the consent is a message in the thread.
Add a checkbox where they already are
On checkout, signup and lead forms, add a separate, unticked WhatsApp consent box — never pre-checked, never bundled into the terms-of-service tick. "Yes, send me order updates and offers on WhatsApp" is one box doing one job. Bundled or pre-ticked consent isn't consent, and it's the first thing that falls apart when someone complains.
Building the list without poisoning your number
A clean list is a living thing, not a spreadsheet you fill once. Three habits keep it healthy.
Confirm new opt-ins. When someone subscribes, send a single confirmation that states what they'll receive and how to leave. This double-checks the number is real, sets expectations, and gives you a clean first interaction before any broadcast.
Make leaving effortless. Every promotional broadcast should make opt-out obvious — "Reply STOP to unsubscribe." An easy exit is your single best defense against blocks and reports, which hurt your number far more than a quiet unsubscribe ever will. The moment someone says STOP, they come off the list — immediately, not next week.
Segment so sends stay relevant. A list isn't one audience. New leads, repeat buyers, and dormant contacts want different things, and a message that's irrelevant to half your list drives the blocks that drag deliverability down. Group by source, stage or interest before you broadcast — our guide to segmenting your WhatsApp audience goes deep on this.
And pace your sends. Even a fully opted-in list will trip spam signals if you fire a thousand identical messages in sixty seconds — that burst pattern looks automated because it is. Human-paced sending matters as much as consent; see sending WhatsApp without getting banned.
Keeping consent records you can actually use
If a complaint ever lands, "we had their number" is not an answer. "Here's the timestamped JOIN message / the form submission with the WhatsApp box ticked / the inbound click-to-chat" is.
For each contact, it's worth being able to point to:
- The source — keyword, form, checkout, click-to-chat, event.
- The timestamp — when they opted in.
- The scope — what they agreed to receive.
- The opt-out state — and the moment they left, if they did.
You don't need a legal department for this; you need a system where the consent and the conversation live in the same place, attached to the contact, instead of scattered across a form tool, a spreadsheet, and someone's phone. That's where a real CRM under your WhatsApp earns its keep.
Where Tenashi fits
Tenashi is the WhatsApp workspace for teams, and it runs on your existing WhatsApp number — linked with a QR scan, no new SIM, no porting. That matters for opt-ins in two ways. First, every contact sits in a real CRM with custom fields, so you can tag opt-in source, store consent state, and segment your list before you ever hit send — order-update subscribers in one slice, offer subscribers in another. Second, the inbound consent itself lives right there in the thread: the JOIN keyword, the click-to-chat first message, the reply that says "yes, send offers" — all attached to the contact, not lost in a separate tool.
When you broadcast to a segment, sends are ban-protected — human-paced with jitter, typing presence, warm-up for newer numbers, and duplicate/burst guards that pause a risky blast before it ships, all written to a safety log. Because it's your own number rather than the official API, there are no template approvals and no per-message fees — you broadcast to the people who opted in and pay a flat price from $18/mo. On Growth & Scale only, AI can also draft replies and summarize long threads, which helps when a broadcast sparks a wave of responses.
Consent done right plus paced sends is the whole game: it keeps your broadcasts landing and reduces the risk to your number (risk reduction, not a guarantee — WhatsApp's policies can change). For the full picture on sending, see our complete guide to WhatsApp broadcasts, and once your list is clean, broadcast message examples for copy that earns replies instead of blocks.
There's a 3-day Growth trial, no card.
Start your free trial → · See every feature
FAQ
What counts as a valid WhatsApp opt-in?
A valid opt-in is an affirmative, specific yes — the person took an action (ticked an unticked box, sent a keyword, or messaged you first) agreeing to receive WhatsApp messages from your business about a stated topic. Pre-checked boxes, bought lists, and "they didn't object" don't count as consent.
Can I broadcast to contacts I didn't get opt-in from?
You shouldn't. Messaging people who never agreed to hear from you is the exact pattern that triggers blocks, reports, and WhatsApp's spam filters — the leading cause of restricted business numbers. Build your list from real opt-ins instead; cold blasting a scraped list puts the number your whole business runs on at risk.
How do I collect WhatsApp opt-ins?
Use sources where intent already exists: a click-to-WhatsApp button or QR people tap to message you first, a "send JOIN to subscribe" keyword, and a separate unticked WhatsApp checkbox at checkout or on a form. Confirm each new subscriber with a one-line message stating what they'll get and how to opt out.
Do I need to keep records of WhatsApp consent?
Yes — keep the source, timestamp, scope, and opt-out state for each contact. The strongest record is the opt-in action itself: a keyword message in the thread or a form submission. In Tenashi the consent lives on the contact alongside the conversation, so you can point to exactly when and how someone joined.
How do I avoid getting banned when broadcasting to my list?
Two things together: only message people who opted in, and pace your sends like a human instead of blasting. Tenashi adds ban-protection — jitter, typing presence, warm-up, and duplicate/burst guards that pause risky sends — which reduces the risk, though no tool can guarantee against WhatsApp's evolving policies.
A great broadcast starts long before you write it — with a list of people who chose to be there. Start a free trial, tag every opt-in to a real contact, and send to an audience that's glad to hear from you.