Calling Hours Guards: Why Call Refuses Calls Outside Allowed Times
How calling-hours checks work in Call, why a call is refused or held, how local time and country rules apply, and what to do when a batch has numbers waiting.
Few complaints about outbound calling are as easy to avoid as the call that arrives at the wrong hour. Calling at dinner time, before breakfast or late at night turns a neutral contact into an irritated one, and in many countries it is also against the rules. A calling-hours guard stops the call before it goes out.

This guide explains what the guard does, why it works in the contact's local time, how to read a refusal in Call, and what to do about numbers that must wait. It sits alongside Choosing When to Call: Timing for Outbound Teams, which covers the sales-effectiveness side.
Why permitted hours exist
Rules about calling hours exist because a phone interrupts. Regulators in many countries set windows for telemarketing and some other automated calls, and some add limits on how many times a number can be tried. The windows differ by country, and sometimes by state or by the type of call. Even where the law is silent, courtesy is not.
Why a guard beats a reminder
- People forgetTime zones, daylight saving and public holidays catch out even careful teams.
- Lists cross bordersOne list may hold contacts in several countries, each with its own window.
- Automation is fastA dialler can place hundreds of calls before anyone notices a mistake.
- It leaves a recordA refusal that names its rule is evidence that the control works.
How the guard works in Call
Every outbound attempt is checked before the carrier is asked to dial. The guard reads the country of the number, finds that country's permitted window and compares it with the contact's own local time, including daylight saving. Examples in the product help include windows such as a mid-morning to early-evening range every day in one country, weekdays only in many others, and some countries that are never called. Exact windows are shown in the how-to articles and may change, so check the screen rather than relying on a copy in an article.
What happens to a call
- AttemptSomeone presses Call, a batch reaches the number, or a campaign dials.
- CheckThe contact's country and local time are compared with the permitted window.
- Allow or refuseInside the window the call goes on to the other checks; outside it, the call is refused or held.
- ExplainThe reason is shown: which rule, how to fix it and who can fix it.
The same guard applies to the browser dialler, outbound call agents, redials and campaigns. It cannot be switched off for a batch, because it is not a preference; it is a control.
Reading a refusal
In the dialer, a red box names the rule that stopped the call. In a batch, the line under a refused number in the recipients list says why. Two cases matter most.
| What you see | What it means | What to do |
|---|---|---|
| Outside permitted hours | The contact's local time is outside the window | Wait; a batch will retry when hours open |
| A legal limit for the country | Calls to that number are capped per day or week, or stopped after the person declined | Do not retry early; some refusals are for good |
| Country never called | Calls to that country are not allowed | Remove the contact from the campaign |
A batch keeps a number that has to wait for its hours and tries it again by itself, while the rest of the batch goes on. That is the right behaviour: a few numbers waiting should not hold up everyone else. A number whose person declined is refused for good.
Attempt limits sit next to hours
Hours are one of several checks. Others cover do-not-call lists, an attempt limit per campaign and a country limit on calls to a person today or this week. All are applied on the server for every call and cannot be raised from the call screens. Every call to a contact counts as an attempt, whether or not it was answered. If you want to understand the whole group, read Managing a Do-Not-Call List in Call.
Planning your campaign around hours
- Group lists by country so each batch targets one window.
- Schedule runs to start when the window opens in the contact's zone, not in yours.
- Expect fewer working hours for far-away lists and plan staffing accordingly.
- Treat a pile of held numbers as a signal to review start times, not to find a way round the rule.
- Check public holidays and local customs; the guard handles the clock, not culture.
Country matters for reading numbers too. Write numbers with the country code, or fill the country column on import so a local number can be read correctly. Our guide on Importing Contacts Without Making a Mess explains how.
A hypothetical example
Imagine a small training company that runs a follow-up campaign to people who attended a free workshop. The list holds contacts in three countries, and the team works from a single office. On the first morning the team starts a batch at their own nine o'clock. Contacts in the first country are inside their window and are called. Contacts in the second are still before theirs, so those numbers are held. Contacts in the third are in the evening, past their window, so those are held for the next day.
Nothing has gone wrong. The batch has done exactly what it should: it called the people it could, held the others and said why. The better response from the team is to split the list by country next time and start each batch when its window opens. That gives a cleaner picture of results as well, because calls in the same country at similar times are easier to compare.
What to tell your team
- A refusal is not an error; it is the control working.
- Do not copy numbers into the browser dialler to get round a held batch. The same guard applies there.
- If a refusal looks wrong, check the country on the contact before raising it.
- If someone asks not to be called again, record it at once so the suppression list protects them.
Explaining this clearly avoids a common temptation, which is to treat the guard as an obstacle to be worked around. A team that understands why the rule exists keeps to it without being asked, and the records show it.
What the guard does not cover
A calling-hours guard answers one question: is this a permitted time? It does not tell you whether you may call this person at all, whether you need prior consent, whether an automated or AI voice is allowed, or what you must say at the start of the call. Those depend on your country, your industry and how you got the number.
Doing it in Call
Calling-hours routine
- Make sure each contact has a country, or a number written with its country code.
- Read the red box or the line under a refused number to see which rule applied.
- Leave held numbers in the batch; they retry when their hours open.
- Do not attempt a workaround; the hours cannot be switched off for a batch.
- Review refusals weekly and fix list or timing problems at the source.
Pair this guard with the stop-all switch for emergencies and with suppression lists for people who ask not to be called. Together they make an outbound programme you can explain to a regulator, a manager or a customer.
Frequently asked questions
Whose time zone does the guard use?
The contact's local time, including daylight saving, not the caller's. A call can be fine for you and still outside the allowed hours where the contact is.
What happens to numbers that have to wait?
A batch keeps them and tries again by itself when their calling hours open, while the rest of the batch carries on.
Can I override the calling hours for a batch?
No. The calling hours and legal limits cannot be switched off for a batch.
Why was a call refused even inside the hours?
Another check may have applied: a do-not-call entry, an attempt limit or a country limit. The refusal message names the rule and who can fix it.
Does the guard decide whether I may call someone at all?
No. It checks timing only. Consent, registers and rules for automated or AI voices depend on your country and need separate attention.
Does every call count as an attempt?
Yes. Every call placed to a contact counts toward attempt limits, whether or not it was answered.