Set expectation before confirmation
State the sender, program purpose, frequency context, and applicable message/data-rate notice before asking for confirmation.
AUDIENCE PERMISSION GUIDE
Make subscription intent clear before the next message.
Double opt-in adds a deliberate confirmation step after an initial signup, helping teams document intent and route only confirmed subscribers into the intended messaging audience.
- Clear confirmation state
- Better audience quality
- Recorded subscription step
- Safer follow-up routing
OPERATING MODEL
One extra confirmation, a much clearer audience state
The confirmation can follow a keyword, signup form, or limited campaign. It supports stronger permission records, but it does not replace the legal and carrier requirements for the specific program.
Keep the action unambiguous
Use a clear response such as YES or a short code, and distinguish a one-time interaction from ongoing messaging permission.
Preserve the event trail
Keep the signup source, confirmation event, timestamp, program, and audience routing visible for operations and support.
Honor opt-outs everywhere
A confirmation flow must not override a valid user-level, global, or sender-level opt-out.
FROM DECISION TO WORKFLOW
Keep every audience state explicit
The flow should distinguish an initial action, a pending confirmation, an accepted subscription, and a later opt-out without collapsing them into one status.
Initial signup
A person texts a keyword, submits a form, or completes another clearly presented signup action.
Confirmation request
The system sends the next instruction, such as replying YES or entering a short confirmation code.
Confirmed state
Only the completed confirmation moves the contact into the intended confirmed audience state.
Relevant follow-up
The confirmed audience receives the program messages described during signup, with HELP and STOP context.
NEXT STEP
Build the confirmation into your first audience flow
Start free to explore keywords and audience routing, then review consent language and program requirements for your use case.