TCPA SMS Consent and Suppression Standard
Purpose
Defines the consent, suppression, timing, and content rules that govern every marketing SMS Symphony Core sends on a client's behalf. A2P 10DLC registration (a2p/a2p-10dlc-registration-guidance.md) gets the carrier to deliver the message; this standard keeps the send legal under the TCPA. Both gates must clear before any batch.
This is the rule the CLAUDE.md trigger table points at whenever you plan, build, or send an SMS campaign.
Scope
All outbound SMS classified as marketing (promotional, re-engagement, offers, announcements). It does not govern transactional/service notifications (appointment confirmations, order/pickup status, one-time codes), which are a separate, TCPA-exempt class handled inside the relevant service workflow. When a message mixes a service purpose with a promotion, treat the whole message as marketing.
1. Consent tiers
| Class | Example | Consent required |
|---|---|---|
| Transactional / service | tune-up ready for pickup, appointment reminder, OTP | Established relationship; recipient can still reply STOP. TCPA-exempt from prior-express-consent. |
| Marketing | pre-season offer, sale, re-engagement, "reserve your slot" | Prior express written consent from the recipient, captured and stored, before the first send. |
Marketing SMS with no stored prior express written consent is not sendable. There is no "existing customer" exception that converts a transactional phone number into a marketing-consented one. A number collected at point of sale for a receipt or a pickup text is not marketing consent.
2. Valid opt-in
A marketing opt-in is valid only if all of these are true and recorded:
- The person took an affirmative action to opt in (texted a keyword, submitted a consent form, checked an unchecked-by-default, optional consent box). Consent is never a condition of purchase.
- The consent disclosure named the sender, stated message type + frequency ("recurring"), and included "message and data rates may apply" and STOP/HELP. Use the approved language in
../../08-reference/templates/a2p/terms-of-service-template.md. - A record exists: contact ID, timestamp, opt-in source/method, and the exact disclosure text/version shown. In the platform, tag the contact
sms-opted-inand set theSourcefield so the consented cohort is a reportable segment (see../../08-reference/standards/sc-tagging-standard.md).
Approved opt-in mechanisms: inbound keyword to the sending number; a consent form / consent landing page (see a2p/a2p-consent-form-url-guide.md); an unchecked optional checkbox on a lead form; verbal-then-confirm only if the confirmation opt-in is itself captured.
3. Suppression — scrub before every batch
Maintain a per-client never-send set and re-apply it immediately before every send. Suppress:
- Guessed / inferred numbers — any number a client "filled in" by assuming an area code or pattern (e.g., an "Assumed Phone Numbers" column). These are do-not-send: no consent, high wrong-number and litigation risk.
- Malformed numbers — anything not a complete, valid 10-digit US number (7-digit fragments with no area code, etc.). Do not send until enriched and re-validated.
- STOP / unsubscribe — anyone who replied STOP, to any campaign, ever. The platform maintains this; never re-add them manually.
- DND / do-not-contact — contacts flagged DND on the SMS channel. See §3.1: DND records two different things and only one of them is consent.
- Non-consented — anyone without a stored §2 opt-in (for marketing sends).
Suppression is subtractive and cumulative: a number leaves the sendable set permanently once suppressed, and re-entry requires a fresh opt-in. The one exception is a DND flag that never carried consent in the first place — see §3.1.
3.1 Consent-set DND versus machine-set DND
The DND flag is written by two very different kinds of event, and treating them alike is a mistake in both directions: it strands reachable people forever, and it dilutes the meaning of a real opt-out.
Consent-set DND is permanent and is never cleared. A person asked not to be contacted. Evidence, read from dndSettings.<channel>:
messagecontainsSTOP_KEYWORD, orstatusispermanent- an email unsubscribe or spam complaint
- a human recorded the request, e.g.
messagebeginsUpdated by '<name>'
Machine-set DND is a deliverability signal, not consent. No person expressed a preference. Evidence:
messagecontainsTWILIO_ERROR_CODE: <n>— the message failed to delivermessagecontainsCarrier Lookup— the number was guessed to be a landline or non-SMSmessagebeginsUpdated from workflow_<id>— an automation set it
Machine-set DND still suppresses sending while it stands, because a number that cannot receive SMS should not be texted. But it may be cleared on evidence that the underlying signal was wrong: the contact replies on another channel, a person confirms the number, or the flag traces to an automation that was itself in error. Clearing requires a named reason recorded against the contact, and never applies to a contact that also carries any consent-set evidence.
Classify on dndSettings, never on the flat dnd field. The top-level dnd boolean reads false on contacts whose per-channel dndSettings.SMS.status is active. Anyone checking the flat field will conclude a suppressed contact is reachable.
When in doubt, treat it as consent. The cost of leaving one reachable contact suppressed is a lost lead. The cost of the reverse is $500 per text, $1,500 if willful.
4. STOP / HELP handling
The platform auto-appends the opt-out line ("Reply STOP to unsubscribe") and the location/sender name to every SMS. Do not hand-write a STOP line in message copy — it double-prints and wastes segment length. See the operational note in ../../04-operations/sops/meta-lead-capture-and-nurture-ghl-sop.md. HELP must return sender identity + contact info; STOP must send one confirmation and then suppress.
5. Quiet hours and send window
- Never send before 8:00 or after 21:00 in the recipient's local time (TCPA floor). Use the contact's timezone, not the sender's.
- SC tighter default: send marketing SMS only during local business hours (roughly 9:00–18:00 ET for US-Eastern clients), on business days, avoiding early mornings, late evenings, and holidays. A message that lands at a friendly hour reads as a neighbor, not a spammer.
- Schedule and throttle batches; do not fire thousands of segments in one burst.
6. Sender identity
- Send from a single, consistent, recognizable number per client. Prefer a local-area-code number the recipient associates with the business; avoid area codes with a heavy regional spam reputation.
- Keep marketing and transactional sender identity coherent so recipients recognize the business.
- Every message must clearly identify the business (the platform's appended location name usually satisfies this; confirm it is set correctly at the sub-account level).
7. Content rules
- Identify the business, state the offer plainly, one clear call to action, one link.
- Follow client brand voice and
../../.claude/working-rules.md#marketing-copy-punctuation(no em-dashes, at most one "!"). No misleading or urgency-manufacturing copy. - No third-party white-label platform names in customer-facing copy (no "GHL"/"GoHighLevel"/"LeadConnector"); use the client's own domain/number. See CLAUDE.md §White-Label Branding.
- Keep to one segment (~160 GSM-7 chars) where practical; the appended STOP line counts toward length.
8. Acquired and purchased lists
An acquired customer/POS list is not a marketing SMS audience. Do not marketing-blast it. Reach it consent-first: invite opt-in through owned channels (direct mail/postcard QR, in-store signage, website, existing transactional touchpoints), and send marketing SMS only to the resulting sms-opted-in segment. Document the consent posture and get client sign-off before the first customer batch.
9. Regulatory basis and penalties
Independently confirmed 2026-07-15 (three research passes, cross-checked). General information, not legal advice — recommend a one-time review by TCPA counsel, which is inexpensive relative to the exposure below.
The rule
- TCPA — 47 U.S.C. § 227; implemented at 47 CFR § 64.1200. Text messages are treated as "calls." Marketing/telemarketing texts to a wireless number sent with an autodialer require prior express written consent (PEWC).
- PEWC definition — 47 CFR § 64.1200(f)(9): a signed written agreement, with clear and conspicuous disclosure, authorizing autodialed advertising/telemarketing to that number, and stating the person is not required to consent as a condition of purchase. The operative prohibition is (a)(2).
- Transactional vs marketing — purely informational/transactional texts use the lower "prior express consent" (a number given for the transaction can satisfy it). Any promotional content converts the whole message to marketing and triggers the written standard.
- No relationship shortcut — the EBR (existing business relationship) exemption was eliminated for wireless telemarketing in 2012. A phone number collected at point-of-sale for a receipt or service is not marketing consent.
- Carrier / industry layer — the CTIA Messaging Principles (May 2023) and the A2P 10DLC regime (The Campaign Registry, aggregators like Twilio) independently require documented per-recipient opt-in and prohibit purchased, rented, or transferred lists (Twilio Messaging Policy: consent cannot be bought/sold/transferred and applies only to the recipient and subject who gave it). A2P registration is not consent.
- Recent change (does not help) — the FCC "one-to-one consent" overlay was vacated (11th Cir., Jan 2025) and formally repealed (Sept 2025). That loosened an added restriction; the baseline PEWC-for-marketing requirement is unchanged.
- State mini-TCPAs (Florida FTSA, Oklahoma, Washington CEMA, others) add stricter consent rules, curfews, and their own private rights of action.
- Florida FTSA section 501.059(5) reaches business recipients and is not gated on autodialers. It bars contacting a "consumer, business, or donor" who has previously said they do not wish to be contacted. Remedy is actual damages or $500, trebled for willful, with mandatory fee-shifting. This is why the suppression list in section 3 is company-wide and permanent rather than per-channel.
The risk (two systems apply at once)
- Legal: $500 per text (negligent), up to $1,500 per text (willful/knowing) — 47 U.S.C. § 227(b)(3). No actual harm required; the sender's own logs prove each violation, making class certification easy. Damages multiply across recipients (30,000 texts = $15M–$45M theoretical). Real settlements include a pizza chain at $750k for texting opted-out customers. The business is the primary defendant even when a platform runs the send; provider terms push liability and carrier fines back to the business account.
- Carrier / technical: silent filtering, number blacklisting, A2P campaign suspension/deregistration, throughput throttling, T-Mobile non-compliance fines of $500–$2,000 per violation billed to the sender, and permanent loss of the texting channel. Rotating to a new number to evade a suspension ("snowshoeing") escalates to account termination. Opt-out rates above ~3–5% draw carrier scrutiny.
No lawful no-consent path
Every shortcut fails: EBR (eliminated for SMS), transactional-reframe (pretext for marketing = marketing), a single "opt-in invitation" text to a non-consented list (itself a solicitation), opt-out/implied consent (marketing SMS is opt-in only), and A2P/vendor "permission" (registration is not authorization; purchased lists are prohibited). The only compliant ways to reach an acquired list are email (CAN-SPAM, opt-out), postal mail, and in-store/website opt-in capture to collect consent going forward, plus a genuinely non-promotional operational notice if ever needed.
Related Documents
- A2P 10DLC Registration Guidance — carrier-side brand/campaign registration
- A2P Funnel Implementation Guide — legal pages + consent form build
- A2P Legal Pages SOP — Privacy / ToS / Consent page build
- SMS Campaign SOP — the end-to-end campaign process this standard gates
- SMS Message Template Library — reusable SMS copy
- SC Tagging Standard —
Source-field segmentation for the consented cohort