How to Set Calling Hours, DNC and Consent Rules

Quick answer

To set compliance rules in DialerBee, go to Admin console → Compliance, which opens the Compliance Dashboard. In the Calling Hours section set Start Hour (08:00 by default), End Hour (21:00 by default), Timezone and Jurisdiction, then pick the Calling Days, remembering that days left off are blocked. In DNC Import, drag and drop a CSV or TXT file with one phone number per line in E.164 format, and use Manage DNC Numbers to add a single number with a reason or to search and remove one. In Compliance Rules, switch on Consent Check, DNC Check, Calling Hours, Frequency Cap and CLI Ownership. Then verify the setup in Recent Compliance Decisions and in the compliance audit report. These are compliance-supporting controls, not legal advice.

Compliance failures are rarely decisions. They are a supervisor who did not know the calling window in another country, a list that was clean when it was uploaded a fortnight ago, or a fourth attempt against a contact who asked twice to be left alone. Configuring these rules once means nobody has to remember them again.

This guide is the admin console procedure for the three controls people ask about most: the calling window, the do-not-call list and the consent rule. The capability overview is on the Compliance Autopilot page. What follows is where to click, what the fields default to, and how to prove the rules are firing.

One caveat. These are compliance-supporting controls that help you meet obligations under frameworks such as TCPA and GDPR and under regional regulators. They do not replace your own counsel.

Step 1: Open the compliance dashboard

Go to Admin console → Compliance. The screen is titled Compliance Dashboard and its subtitle reads "DNC management, calling hours, CLI verification, and compliance audit log". Four cards sit at the top: Total Checks, Allowed, Blocked and Block Rate.

If the screen shows the banner "Compliance is not configured for this tenant", nothing below has been set yet. Never leave that banner standing on a tenant that dials.

Step 2: Set the calling window

Find the Calling Hours section. It has five controls.

Start Hour, which defaults to 08:00.
End Hour, which defaults to 21:00.
Timezone, which defaults to America/New_York. The list includes Asia/Dubai, Asia/Riyadh, Asia/Amman and Africa/Cairo alongside the North American zones.
Jurisdiction, offering United States (US), United Arab Emirates (AE), Saudi Arabia (SA), Jordan (JO) and Egypt (EG). The hint under it reads "This window applies to calls whose destination is this country."
Calling Days, seven day buttons with all seven selected by default. The hint reads "Days left off are blocked, no calls that day (e.g. weekend)."

An Allowed Hours strip shows the resulting window across the 24 hours of the day, which is the fastest way to catch a window saved the wrong way round. Click Save.

The window applies to calls whose destination is that country, so the rule follows the number being called rather than the location of the floor doing the calling. A floor calling four countries needs the window set for each of them.

Step 3: Match the window to the regulator

The values below are the per-jurisdiction defaults recorded in the BroadNet Engage admin guide. Use them as a starting point, and confirm the current rule with the regulator or your counsel before relying on it.

Jurisdiction	Start	End	Days	Timezone
UAE	09:00	18:00	Sun to Thu	Asia/Dubai
Saudi Arabia	09:00	17:00	Sun to Thu	Asia/Riyadh
Egypt	09:00	18:00	Sun to Thu	Africa/Cairo
Jordan	09:00	18:00	Sun to Thu	Asia/Amman

A tenant override may be more restrictive than the jurisdiction default. It may not be less restrictive, so you cannot extend calling hours beyond what the regulator permits by editing a field.

Step 4: Load the do-not-call list

The DNC Import section has a drop area labelled "Drag and drop DNC file (CSV/TXT)" with the note "CSV or TXT, one phone number per line (+E.164 format)". Two counters sit beside it: Total DNC Numbers and Last Import. Numbers are validated as 7 to 15 digits, so a malformed row is caught at import rather than dialled.

Below it, Manage DNC Numbers handles the day to day:

Add number to DNC takes one number and a reason. The reason defaults to Manual Entry, with Customer Request, Legal Request and Complaint as the alternatives. Click Add to DNC.
Search and remove from DNC takes a number of at least seven digits and offers Remove from DNC on each match.

Step 5: Switch on the per-call rules

The Compliance Rules block is a set of toggles, each with its own description on the screen.

Rule	What the screen says it does
Consent Check	Require consent record before dialing. Disable for implied consent campaigns.
DNC Check	Check against Do Not Call registry before dialing.
Calling Hours	Enforce the permitted window in local time at the destination.
Frequency Cap	Limit call attempts per contact per time period.
CLI Ownership	Verify tenant owns the CLI number for the jurisdiction.

Consent Check needs a decision rather than a default: turning it on means a marketing call will not be placed without a consent record for that contact. The admin guide records the consent types kept (Marketing Voice, Marketing SMS, Marketing WhatsApp, Marketing Email, Transactional and Recording), the sources accepted (web form, IVR capture, recorded call, API and imported), and that UAE TDRA requires consent renewal every two years.

Step 6: Registry integration and the override

The DNC Registry Integration section carries two toggles that are on by default: Auto-check on import and Block DNC during campaigns. A DNC API Key field stores the credential for external scrubbing.

Below them sits Supervisor DNC override, off by default, carrying the on-screen warning "Caution: May violate compliance regulations". Leave it off unless you have decided who may use it and you are reading the audit afterwards.

Defaults and limits

Field	Section	Default	Accepted values
Start and End Hour	Calling Hours	08:00 and 21:00	as shown on the screen
Timezone	Calling Hours	America/New_York	North American zones plus Asia/Dubai, Asia/Riyadh, Asia/Amman, Africa/Cairo
Jurisdiction	Calling Hours	United States (US)	US, AE, SA, JO, EG
Calling Days	Calling Hours	All seven selected	Any subset of Mon to Sun
DNC file format	DNC Import	CSV or TXT	One number per line, E.164, 7 to 15 digits
DNC add reason	Manage DNC Numbers	Manual Entry	Manual Entry, Customer Request, Legal Request, Complaint
Auto-check on import, Block DNC during campaigns	DNC Registry Integration	Both on	On or off
Supervisor DNC override	DNC Registry Integration	Off	On or off
Frequency Cap value	Compliance Rules	as shown on the screen	as shown on the screen

Verify it works

A compliance rule you have not seen block anything is a rule you are hoping about. Prove each one.

Add a test number you control to the DNC list with the reason Customer Request, then attempt it from a campaign. The attempt should be blocked.
Read Recent Compliance Decisions on the same screen. Each entry shows the phone number, the reason, a decision badge of Allowed or Blocked, and a timestamp. Your test should be there.
Watch the Blocked and Block Rate cards after a campaign runs. A block rate of zero on a list that has never been scrubbed usually means a rule is off.
Attempt a call to a destination outside its permitted window and confirm it is blocked with a calling hours reason.
Generate the compliance audit and DNC compliance reports, filter to blocked decisions and export to CSV for your records.

Troubleshooting

The banner says compliance is not configured. Nothing on this page has been saved for the tenant. Set the calling window first, then the rules.
No calls go out at all. Check Calling Days. Days that are not selected are blocked, and it is easy to save a window with the weekend left off for a market whose weekend is different.
Calls go out at the wrong local time. The window applies to the destination country, so check the Jurisdiction and Timezone pair rather than the clock on the floor.
The import reports fewer numbers than the file held. Rows outside the 7 to 15 digit range are rejected. Re-export in E.164 with one number per line.
A number on the DNC list was still dialled. Check that DNC Check and Block DNC during campaigns are both on, and check whether Supervisor DNC override was used.
Marketing calls are blocked for consent when you expected them to run. Consent Check requires a consent record for the contact, and an expired record does not count. The screen notes that the check can be disabled for implied consent campaigns, which is a decision for your counsel and not a default to flip.

Frequently asked questions

Where do I set calling hours in DialerBee?

Admin console then Compliance, in the Calling Hours section of the Compliance Dashboard. Set Start Hour, End Hour, Timezone, Jurisdiction and Calling Days, then save. The window applies to calls whose destination is the country you selected.

What are the default calling hours in the console?

Start Hour defaults to 08:00 and End Hour to 21:00, with the timezone defaulting to America/New_York and all seven calling days selected. Change all four to match the market you are calling rather than accepting the default window.

What file format does the DNC import accept?

CSV or TXT with one phone number per line in E.164 format. Numbers are validated at 7 to 15 digits, so malformed rows are rejected at import instead of being dialled and charged for.

Can I add or remove a single DNC number without importing a file?

Yes. Manage DNC Numbers takes one number and a reason, which defaults to Manual Entry and also offers Customer Request, Legal Request and Complaint. A separate search box finds a number and offers Remove from DNC.

Which compliance rules can I switch on per tenant?

Consent Check, DNC Check, Calling Hours, Frequency Cap and CLI Ownership, each with its description on the screen. There are also two registry toggles that are on by default, Auto-check on import and Block DNC during campaigns, and a Supervisor DNC override that is off by default.

Does configuring this make my operation compliant?

No product can make that claim. These are compliance-supporting controls that help you meet obligations under frameworks such as TCPA and GDPR and under regional regulators, with decisions recorded so you can explain them later. Your own counsel remains the authority on your obligations.