Compliance
Calling windows, consumer-local time, and staying defensible
Time-zone resolution from the dialed number sounds trivial. It's where a surprising share of compliance exposure actually originates.
Vapia Research · Compliance · June 23, 2026 · 6 min read
Calling-hour rules are expressed in the consumer's local time. Dialers frequently resolve that from the area code, which has been an unreliable proxy since number portability became normal.
Where the exposure comes from
- Ported numbers whose area code no longer matches residence
- State rules tighter than the federal window
- Schedules built in the floor's time zone, not the consumer's
Make the window a hard constraint
Any optimization layer that recommends dialing times must treat calling hours as a boundary the model cannot cross, not a filter applied afterwards. Recommendations should carry an audit trail showing the window used and why.
If a prediction can't explain which window it respected, it isn't defensible.
None of this is legal advice — work it through with your counsel — but the engineering principle holds: constraints belong inside the model, not bolted on after it.