SMS consent, blocking, and opt-out (STOP / HELP)
How LeadLock records consent, when outbound SMS is allowed, and how recipients opt out or get help.
Overview
LeadLock enforces SMS rules on the server: a message is not sent unless there is a valid consent record, an active inbound SMS conversation with that lead, a qualifying recent inbound voice call for callbacks, or a regulatory confirmation (for example after someone texts STOP or HELP). This protects your business and LeadLock from misuse.
Collecting consent
- 1
Use hosted or embedded forms with the SMS checkbox visible next to the phone field (unchecked by default).
- 2
If your chat widget captures a phone for SMS, pass explicit opt-in from your UI before treating the number as subscribed.
- 3
Keep a paper trail: consent history appears on the lead under SMS consent.
Why a send might be blocked
- 1
No consent and no qualifying conversation or voice context yet.
- 2
The lead has opted out (STOP and related keywords) or consent was manually revoked.
- 3
The workspace is suspended for security or abuse reasons.
Opt-out and help keywords
- 1
Standard opt-out keywords include STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, and REVOKE.
- 2
HELP and INFO receive a short assistance message where your flow supports it.
- 3
Recipients can text START to opt back in after opting out; that creates a new consent record.
Quick actions
In this topic
Related articles