Skip to content
POLITIFAST

SMS Consent Ledger

Per-recipient opt-in / opt-out history for every SMS contact.

Last updated 05/24/26

What this surface does

The SMS Consent Ledger is the per-recipient consent history — every opt-in (web form, paper, keyword, double-opt-in), every opt-out (STOP, manual, inferred), and every help-ack event. Sourced from `sms_consent_events` (migration 152) and the broader opt-event apply pipeline.

When to use it

  • A customer asks "did this person actually opt in" — pull their ledger.
  • TCPA / state-rule audit — prove consent provenance for any phone number we messaged.
  • Investigating a complaint or carrier escalation.

Key gotchas

  • Consent events are immutable. To "correct" a consent state, write a new event with the right type.
  • Cross-workspace propagation (migration 109) means an opt-out in one campaign suppresses the contact across all customer campaigns. Be explicit if you need to scope.
  • Inferred opt-outs (no explicit STOP but persistent non-engagement) are flagged separately — they do not carry the same legal weight.

Related