How to set up opt-in on the WhatsApp Business API
Opt-in is the permission a customer gives you to message them on WhatsApp — and Meta requires it before your business initiates any conversation. Getting it right is what protects your quality rating, keeps templates approved, and stops your number from being blocked. This guide walks you through collecting valid opt-in, recording it, and firing your first template message on the official WhatsApp Business API with InfiQ, plus the specific mistakes that get Indian businesses into trouble.
What you'll do
Collect explicit opt-in on any channel that names your business and WhatsApp, store a timestamped record of it, then send an approved utility or marketing template. InfiQ handles the API plumbing; you keep a clean consent trail so your quality rating and deliverability stay healthy.Step 1 — Understand what a valid opt-in actually is
Before you build anything, be clear on what Meta counts as consent. An opt-in is an affirmative action where the customer agrees to receive WhatsApp messages from your specific business at a specific number. It has three non-negotiable ingredients: the customer took a clear action, your business name is visible at the moment of consent, and it is obvious the messages will arrive on WhatsApp. A pre-ticked box, a buried line in your terms, or a phone number you scraped from an order form do not qualify. You do not have to collect opt-in inside WhatsApp itself — a website checkbox, a missed-call flow, an SMS reply, or a point-of-sale question are all acceptable as long as those three ingredients are present.
- Clear action: a ticked checkbox, a typed 'YES', a tapped button, or a signed form.
- Your business is named: the customer knows exactly who will message them.
- WhatsApp is named: the wording says messages come via WhatsApp, not just 'notifications'.
Step 2 — Choose where you will collect it
Pick the collection point that matches how customers already reach you, because that is where consent feels natural and conversion is highest. Most InfiQ customers use more than one. A website or checkout checkbox is the workhorse for e-commerce; a WhatsApp click-to-chat link or QR code turns an inbound message into implied opt-in for that thread; a keyword like 'START' over SMS suits offline and print campaigns; and a staffed counter or IVR prompt captures walk-in and phone customers. Whichever you choose, the wording must stay explicit — swap generic phrasing such as 'stay in touch' for something concrete like 'Yes, send me order updates and offers on WhatsApp from [Your Business]'.
- Website / checkout: an unchecked box next to explicit WhatsApp wording.
- Click-to-chat link or QR: the customer's first message is their consent for that conversation.
- SMS/keyword: 'Reply START to get WhatsApp updates from [Your Business]'.
- In-store or IVR: a staff member or voice prompt confirms and logs consent.
Step 3 — Record and store the consent
Consent you cannot prove is consent you do not have. For every opt-in, capture the phone number, a timestamp, the source (which form or channel), and the exact wording the customer agreed to. This record is what you fall back on if Meta reviews your account or a recipient reports your messages. Inside InfiQ you can tag contacts with their opt-in source and date, so segments you later message are provably permission-based. Just as important, wire up an equally easy opt-out: honour any 'STOP' reply, unsubscribe tap, or block instantly, and never message a number that has opted out — repeated messages to unwilling recipients are the fastest way to sink your quality rating.
Step 4 — Prepare and submit your first template
You can only start a conversation with a pre-approved template message, so the opt-in and the template go hand in hand. Draft the message that the customer expects based on what they opted into, then submit it in the right category — utility for transactional messages like order and appointment updates, marketing for promotions and offers, or authentication for one-time passcodes. Category matters twice over: the wrong category is the most common reason templates get rejected, and it also sets what you pay, because WhatsApp bills per delivered message by category. Keep the copy honest to the opt-in wording; a template that reads like a promo while filed as utility will be flagged.
- Utility: order confirmations, shipping updates, appointment reminders, account alerts.
- Marketing: launches, offers, re-engagement, seasonal campaigns.
- Authentication: one-time passwords and verification codes only.
- Match tone to category — promotional language in a utility template invites rejection.
Step 5 — Test end-to-end before you scale
Never let a real campaign be your first live test. Add your own number to InfiQ as a test contact, run it through the actual opt-in flow you built, and confirm the record lands with the correct source and timestamp. Then send your approved template to that number and check three things: it arrives, it renders correctly (variables filled, buttons working), and the delivery and read status report back in InfiQ. Reply from your test number to confirm the free 24-hour service window opens, letting you respond with free-form messages. Only once this full loop works cleanly should you point it at your live audience.
Step 6 — Go live, then watch quality and deliverability
With testing passed, enable the flow for real customers — but start measured, especially on a new number. Sending high volume to a cold number on day one triggers spam heuristics; ramp gradually so WhatsApp learns your number sends wanted messages. From launch, keep an eye on your quality rating in InfiQ and on delivery, read, and block signals. A dip usually traces back to messaging people who did not clearly opt in, sending the wrong category, or ignoring opt-outs — all of which the steps above are designed to prevent. Healthy opt-in hygiene is not a one-time setup; it is what keeps your messaging capacity and per-message costs predictable over time.
- Warm up new numbers — grow volume over days, not all at once.
- Watch quality rating; a drop is an early warning, not a verdict.
- Track delivery, read and block rates per campaign in InfiQ.
- Re-confirm consent periodically for older or dormant lists.