Express written consent must name the specific number and bear a signature
The requirementstatement
The retained consent agreement must identify the specific telephone number consented for and bear the consumer's signature.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.message_flow
- Where it liveslayer
- OperationalOPERATIONAL
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- What the fix involvesfailureClass
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- FCC
- When it appliesapplicabilityText
- Applies when the use case is MARKETING, MIXED, SWEEPSTAKE and LOW_VOLUME.
Why this rule existsrationale
TCPA express written consent is a signed agreement naming the number, and an electronic signature under E-SIGN qualifies — a ticked box with a stored identity and timestamp satisfies it. What does not satisfy it is a record that cannot tie a signature to a specific number.
How to fix itremediation
Ensure the consent record ties an identifiable signature — including an E-SIGN electronic one — to the specific number, and describe that linkage in the message flow.
A compliant exampleexample
The checkbox action, the entered phone number, the consenting account identity and the timestamp are stored together as the signed agreement.
Rules you will hit next
6 other rules read campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-073Message flow must state message frequencyBlockingBLOCKING
OPS-215 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.