Help Center › Dialer Compliance › Calling-hours protection

Calling-hours protection

Asan CRM only places calls during local daytime hours for the person you're calling — automatically, based on their number. Off-hours calls are held, not dialed.

In one line: calling someone at the wrong hour is the fastest way to earn complaints — and complaints are what get your numbers labelled "Spam Likely." This keeps every call inside a reasonable local window without anyone watching the clock.

Why calling hours matter

Late-night and early-morning calls drive complaints, and complaint rate is one of the strongest signals carriers use to flag a number. One agent dialing an East-Coast lead at 10 PM their time can quietly damage a number the whole team relies on. Asan CRM removes that risk by checking the recipient's local time on every call — so a tired agent, a wrong timezone assumption, or a late shift can't put your numbers at risk.

How it works

Before each call connects, Asan CRM works out the recipient's local time from their phone number and only dials inside the allowed window:

Setting	Behaviour
Allowed window	8:00 AM – 9:00 PM
Timezone basis	The recipient's local time (from their area code), not yours
Outside the window	Call is held with a clear reason — never silently dropped
International / unknown region	Skipped, so you don't accidentally place an out-of-policy call

Because the window follows the lead's timezone, your team can dial from anywhere — a Karachi-based floor calling US leads is checked against US local time automatically.

What you'll see

When a lead is outside their calling window, the dialer skips it and tells you exactly why instead of failing quietly:

Held — it's 9:14 PM for this lead (Eastern). We hold calls to 8 AM–9 PM in the recipient's local time. This lead will be available again when their window opens.

Tips

Build lists across timezones. If one region is closed, queue leads in regions that are still inside their window so agents stay productive.
Trust the skip. A held call isn't a bug — it's protecting the number. The lead returns automatically once it's a reasonable hour for them.

Frequently asked

Whose time zone decides the window — mine or the lead's?+

The lead's. Asan CRM reads the recipient's local time from their number, so a call is only placed when it's daytime for them, regardless of where your team sits.

Can I change the 8 AM–9 PM window?+

The window reflects standard calling-hour expectations and isn't customer-adjustable. If you have a specific regulated use case, contact support.

What happens to a lead that's outside its window?+

It's held with a reason and automatically becomes dialable again once the local window opens — you don't have to re-add it.

Why was an international number skipped?+

If a number's region (and therefore local time) can't be confirmed, Asan CRM skips it rather than risk an off-hours or out-of-policy call.

Was this article helpful?

Thanks — we'll use this to make the docs better.

Last updated 16 Jun 2026 · Applies to: Asan CRM