WhatsApp opt-in rules and consent tracking in Simio

How WhatsApp opt-in works: what Meta requires, per-account consent tracking, opt-out handling, and the collection methods Simio supports today.

WhatsApp requires businesses to obtain explicit consent from a contact before sending them any business-initiated message. Simio enforces this consent model on every send. This page explains the rules, how Simio tracks opt-in status, and how you can collect opt-ins.

Consent is tracked per channel and per messaging account in Simio. For the shared consent model, see Consent and opt-in status.

What Meta requires

Before you can send a business-initiated WhatsApp message to a contact, you must:

• Obtain explicit consent from the contact for WhatsApp messaging, in a written or clickable form they can trace back.
• State clearly that they are opting in to receive messages from your brand on WhatsApp.
• Provide an easy way to opt out at any time, and honor opt-outs immediately.

Meta does not verify the opt-in source itself, but if too many contacts report your account as unwanted, quality drops and the account may be flagged or suspended. See Account quality.

Consent tracking in Simio

Simio tracks opt-in status per WhatsApp Business account per contact, not per company. A contact who opted in on WhatsApp number A has not automatically opted in on WhatsApp number B, even if both numbers belong to the same company. When you send a campaign or automation on a specific account, only contacts opted in on that account are targeted; opted-out contacts are silently skipped.

The consent history recorded on each contact includes:

• Opt-in source (CSV import, wa.me link, Shopify checkout, Meta ad, chatbot, API).
• Opt-in and opt-out timestamps.
• The WhatsApp Business account the opt-in applies to.

See the contact model in Contacts and segments and the cross-channel view in Consent and opt-in status.

Opt-out handling

A contact can opt out in several ways, all of which mark the contact as opted-out on the relevant account:

• Clicking a WhatsApp template button that leads to an opt-out step in the flow.
• Being manually unsubscribed by a Simio user.
• Being unsubscribed programmatically from an integration (for example, Brevo sync).

Once opted out on an account, the contact is excluded from all future sends on that account until they explicitly opt back in.

Collecting opt-ins

Simio supports multiple methods for collecting WhatsApp opt-ins today:

Method	How it works
CSV import	Upload up to 100,000 phone numbers per file and mark them opted in on a specific WhatsApp account at import time. See Contacts and segments.
wa.me link and QR code	Share a WhatsApp deep link; contacts who message you opt in through a Simio chatbot flow.
Meta Click-to-WhatsApp ads	Run Meta ads that open a WhatsApp conversation; capture opt-in through a chatbot flow.
Shopify checkout	Add an opt-in checkbox on your Shopify checkout, wired to a Simio-provided text and consent description.
Shopify chat bubble	Embed a floating WhatsApp widget on your Shopify store, linked to a chatbot flow.
Klaviyo popup or newsletter	Convert your email list into WhatsApp opt-ins through a Klaviyo popup or a dedicated newsletter.

Detailed step-by-step guides for each collection method will live under Guides → Collect opt-ins as they are published.

Forcing a send to non opt-ins

In specific business cases (for example, a company sending an order-confirmation Utility template to customers whose numbers they already have from another lawful source), Simio can be configured to send to contacts that are not marked as opted in in Simio. This is a per-flow decision and requires you to have a defensible lawful basis. Contact your Simio account manager to enable it on a given campaign or automation.

Related

Consent (all channels)

How Simio tracks opt-in status on every contact.

Account quality

Why reported opt-outs hurt your quality rating.