# OPS-QUIET-HOURS-DISCLOSED — Quiet-hours handling should be disclosed for promotional programmes

> A promotional campaign should indicate that sending respects recipient-local quiet hours.

- **Rule ID:** OPS-QUIET-HOURS-DISCLOSED
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.description + campaign.message_flow`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** FCC, state law
- **Applies:** Applies when the use case is MARKETING, MIXED, SWEEPSTAKE and LOW_VOLUME.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-quiet-hours-disclosed/

## Why this rule exists

Several US state mini-TCPAs impose quiet-hours windows measured in the recipient's local time, and violations are litigated rather than merely filtered. A national campaign that never mentions time-of-day handling is the profile plaintiffs' firms look for, so disclosing it is cheap insurance.

## How to fix it

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.

## Example of a compliant value

```text
Promotional messages are sent between 9am and 8pm in the recipient's local time zone, and are suppressed in states with stricter windows.
```

## Notes

Registration-side twin — we verify the disclosure, not the send-time behaviour.