Contents
At a glance
- Category
- Voice and messaging
- Record five things
- Which number, when, by what mechanism, for what purpose, and the wording shown
- Transactional vs marketing
- Marketing requires a higher consent standard in most regimes
- Not transferable
- Consent to email is not consent to text; consent to one purpose is not consent to all
- Not the same as
- A2P 10DLC registration - that is a carrier requirement, not legal consent
- Check consent
- In the workflow immediately before sending, and log the check
What opt-in means
Opt-in is permission, given by the recipient, before you contact them. It is the foundation of every messaging regime in the world - the US TCPA, the UK and EU rules under GDPR and PECR, Canada's CASL - and although the details differ enormously, the shape is consistent: you need consent, the consent must be informed, and you must be able to prove it.
For an automation this is not a legal footnote, it is a data model requirement. Your system has to store, per contact, what they consented to, when, and by what mechanism. If you cannot produce that record, you cannot demonstrate consent, and an automation that texts everyone in a spreadsheet is a liability regardless of how well it is built.
What a good opt-in record contains
Five fields. Who - the specific phone number or email, not the person in general. When - a timestamp. How - the exact mechanism, such as a checkbox on a named web form, a reply of START, or a signature on a job sheet. What for - the specific purpose consented to. And the wording shown at the time, stored as text, because the disclosure they actually saw is what matters.
Capture these at the source and carry them through to whatever sends the messages. The common failure is consent recorded in a form tool and never synced to the CRM the automation reads from, so the sending system has no idea who agreed to what.
The standard varies by message type
This is the distinction that catches people out. Transactional messages that a customer expects as part of a service they requested - an appointment confirmation, a job update, a delivery notification - are treated more permissively in most regimes. Marketing messages - promotions, offers, reactivation campaigns - require a higher standard, and in the US the TCPA has historically required prior express written consent for marketing texts, with rules in this area under active revision.
Two practical rules follow. Consent must not be bundled: a tick box that says "I agree to the terms and to receive marketing texts" is weak consent in most jurisdictions and clearly non-compliant in some. And consent to one channel is not consent to another - an email opt-in does not authorise texting.
Where it interacts with the rest of the stack
Opt-in sits alongside A2P 10DLC registration in the US, and the two are frequently confused. Registration is a carrier requirement about who you are; consent is a legal requirement about the recipient's permission. Meeting one does not satisfy the other, and your 10DLC campaign submission will ask you to describe your opt-in flow accurately.
It also implies the reverse: honouring opt-out immediately and permanently, which is STOP handling, and treating that suppression as authoritative across every system that can send.
What you should know
Rules in this area change, and this page is orientation rather than legal advice - get advice for your jurisdiction and your message types, and re-check it, because the US position in particular has moved repeatedly in recent years.
The design that ages well is straightforward: separate consent by channel and by purpose, store the evidence with the contact, check it in the workflow immediately before sending rather than assuming it was checked upstream, and log the check. That last step is what lets you answer a complaint with a record rather than a recollection.
Opt-in FAQ
What does opt-in mean in messaging?
The recorded permission a person gives before you may text, call or email them. Every major regime requires consent that is informed and provable, so the practical requirement is a stored record of who consented, when, how, and to what.
What should I store when someone opts in?
The specific number or address, a timestamp, the exact mechanism such as a named web form checkbox or a reply of START, the purpose consented to, and the wording they were shown at the time. The last one matters because the disclosure they saw is what counts.
Is consent for appointment reminders the same as for marketing?
No. Transactional messages a customer expects as part of a service they requested are treated more permissively in most regimes, while marketing requires a higher standard - historically prior express written consent under the US TCPA. Store the two separately.
Can I text customers who gave me their email address?
No. Consent is channel-specific and purpose-specific. An email opt-in does not authorise texting, and consent to service updates does not authorise promotions. Bundled consent - one tick box covering terms and marketing - is weak at best and non-compliant in several jurisdictions.
Is A2P 10DLC registration the same as consent?
No, and confusing them is common. Registration is a US carrier requirement that verifies who you are as a sender. Consent is a legal requirement about the recipient's permission. You need both, and your 10DLC campaign submission will ask you to describe your opt-in accurately.
Where should the consent check happen in an automation?
Immediately before sending, in the workflow itself, rather than assuming it was verified upstream. Check the current consent record, log that you checked it, and skip anyone suppressed. That log is what lets you answer a complaint with evidence rather than a recollection.
Primary source
Twilio - opt-in and opt-out handling
Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what opt-in means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
