Skip to main content
Simio tracks consent per channel, per messaging account, per contact. A contact who opted in on one of your WhatsApp Business numbers has not opted in on a different WhatsApp number. This page explains the consent model and how it is applied when you send. Every contact carries a set of opt-in records, one per (channel, messaging account) pair they have interacted with. Each record stores:
  • Channel (for example, WhatsApp).
  • Messaging account (the specific connected account on that channel, such as a WhatsApp Business number).
  • Opt-in status (opted in, opted out, or never opted in).
  • Source of the opt-in (CSV import, wa.me link, chatbot, ad, checkout, integration, API).
  • Opt-in timestamp and, if applicable, opt-out timestamp.
When you send a campaign or automation, Simio filters the audience against the opt-in records for the specific messaging account you selected as the sender. Contacts without an opt-in on that account are silently skipped.

​
Why per-account, not per-company

A contact may:
  • Have opted in on your customer-service WhatsApp number but not on your marketing number.
  • Have opted out of one brand’s WhatsApp account without wanting to leave a sister brand’s.
Tracking consent per account keeps each of these situations correct. It also matches how Meta enforces consent on the WhatsApp side. Each (channel, messaging account) record is independent of the others:
  • Opting in on one account does not opt the contact in on another account.
  • Opting out on one account does not opt the contact out on another, and vice-versa.
  • A send uses only the opt-in records for the account it is sent from; it ignores the consent state on every other account.

​
Opt-out sources

A contact can be marked opted-out on a given (channel, account) through several paths, all of which produce the same result:
  • Clicking a message button that leads to an opt-out step in the flow.
  • Being manually unsubscribed by a Simio user from the contact detail view.
  • Being unsubscribed programmatically through an integration (Brevo sync, Shopify, and future connectors) or through the Simio API.
Once opted out, the contact is excluded from all future sends on that (channel, account) until an explicit re-opt-in.

​
Channel-specific opt-in rules

Each channel has its own legal and platform requirements for how consent must be obtained and worded. Simio does not enforce those on your behalf; you must collect opt-ins in a compliant way.

WhatsApp opt-in rules

What Meta requires, opt-out handling, and the collection methods Simio supports today.

Contacts & Segments

The full contact model, fields, tags, and segments.

Channels overview

The messaging channels available in Simio.