In practice, compliance rests on evidence. The question is never "did you mean well", it is "can you show, for this specific phone number, when and how consent was captured, and that STOP was honoured immediately". That means storing the timestamp, the source of the opt-in, the exact disclosure wording shown, and the full opt-out history for every contact.
Message content matters too. Carriers filter for prohibited categories regardless of registration, and every campaign should identify the sender, keep to the use case it was registered under, and honour HELP and STOP keywords. Sending marketing traffic through a campaign registered as transactional is a common and avoidable violation.
10DLC compliance checklist
Registration, the carrier layer:
- Brand registered with The Campaign Registry under the exact legal name and EIN, with the trust score checked.
- One campaign registered per use case, with sample messages and opt-in evidence attached.
- Traffic sent only through the campaign whose use case it matches; marketing never rides a transactional campaign.
- Numbers attached to their campaigns before the first send.
Consent, the legal layer:
- Prior express written consent captured before any marketing text, with the disclosure shown at opt-in (message frequency, "message and data rates may apply", how to opt out).
- For each phone number: the timestamp, the source of the opt-in and the exact wording shown, stored where you can produce them.
- STOP honoured automatically and immediately, HELP answered, and the opt-out persisted across every channel and system that can send.
- Quiet hours respected in the recipient's time zone.
Content and operations:
- Sender identified in the message, and nothing from the carriers' prohibited categories.
- Consent and opt-out history retained for the length of the programme plus the limitation period.
- A named owner for inbound replies, so a STOP or a complaint is seen by a person.
Every item above applies to the SMS fallback of an RCS programme; the RCS agent has its own verification on top, covered in what is a verified sender.
- Two layers: carrier registration (10DLC) and legal consent (TCPA). Both are required.
- Prior express written consent is required before marketing texts, with a clear disclosure at opt-in.
- STOP and HELP must be honoured automatically, and opt-outs must persist across channels.
- Traffic must match the use case its campaign was registered under.
- On SimplyRCS, STOP and HELP are handled above the AI layer, so they are always honoured, and consent records are retained with a full audit trail.