Skip to content
nitrodialer

Compliance

Calling hours and do-not-call rules, enforced by the dialer itself

Calling hours in each lead's local time, national do-not-call lists, internal opt-outs and holidays, with presets for the US, Canada, the UK and Australia and a record of every call.

The problem

Compliance that depends on reps remembering

Calling a Los Angeles number at 7:30 a.m. because it's 10:30 in New York, missing a do-not-call request, or dialing off a stale registry file are easy mistakes. Each one can cost a business a penalty per call.

How NitroDialer handles it

Calls that break the rules can't be placed

Every lead passes a compliance check on the server before a call is placed. If it's outside the lead's calling hours, on a do-not-call list, or your national list copy is too old, the dialer simply doesn't call.

How it works

Pick the rules for where your leads are

Each workspace chooses a calling region. The preset fills in calling hours, the national do-not-call list and how fresh it must be, how long opt-outs are kept, and a holiday calendar. Every value can be edited.

  • United States: 8 a.m.–9 p.m. every day, National Do Not Call Registry no older than 31 days, opt-outs kept 5 years
  • Canada: 9 a.m.–9:30 p.m. weekdays and 10 a.m.–6 p.m. weekends, National DNCL no older than 31 days, opt-outs kept 3 years
  • United Kingdom: suggested 8 a.m.–9 p.m. Monday to Saturday, TPS and CTPS screened at least every 28 days
  • Australia: 9 a.m.–8 p.m. weekdays, 9 a.m.–5 p.m. Saturday, no Sundays or national public holidays, Do Not Call Register wash valid 30 days
  • Custom: your own hours, list freshness and retention — for example, to match the strictest US state you call

How each rule is enforced

The checks run on the server, so they apply to every agent, every campaign and every API-created lead.

  • Calling hours are checked in the lead's local time, worked out from the state or province on the record, then the area code
  • Consumer campaigns pause automatically when your national list upload is older than the region allows
  • Do not call blocks every number on the lead across all campaigns instantly, and the CRM record is updated
  • Holiday calendars block dialing on those days; admins can add or remove dates
  • Business-to-business campaigns skip the national list (except in the UK, where CTPS covers businesses) but still respect hours and internal DNC

Evidence for every call

Each call stores the lead's local time, time zone, consent basis and which national list upload was in force, so you can answer a complaint with records instead of guesses.

At a glance

Regions
United States, Canada, United Kingdom, Australia, Custom
National list
CSV upload; consumer campaigns pause when it's older than the region's limit
Internal DNC
Instant and workspace-wide; kept 5 years (US) or 3 years (Canada, default elsewhere)

See it on your own CRM list

A 20-minute walkthrough with your Dialpad account and one of your real lists. Bring your hardest compliance question.