Quiet-hours handling should be disclosed for promotional programmes
The requirementstatement
A promotional campaign should indicate that sending respects recipient-local quiet hours.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.description + 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
- FCCstate law
- When it appliesapplicabilityText
- Applies when the use case is MARKETING, MIXED, SWEEPSTAKE and LOW_VOLUME.
Why this rule existsrationale
How to fix itremediation
State that promotional sends are restricted to daytime hours in the recipient's local time zone, and configure your platform to enforce it per-recipient rather than per-server.
A compliant exampleexample
Promotional messages are sent between 9am and 8pm in the recipient's local time zone, and are suppressed in states with stricter windows.
Notesnotes
Rules you will hit next
2 other rules read campaign.description + 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.
OPS-QUIET-HOURS-DISCLOSED is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.