Help Center › Dialer Compliance › DialGuard

DialGuard

DialGuard is Asan CRM's server-side dialing safety system — 7 guardrail layers that protect your numbers and carrier trust automatically.

Every guardrail is enforced server-side. It cannot be bypassed by users, browser extensions, or API calls.

What is DialGuard

DialGuard is a server-side enforcement system that sits between your agents and the carrier. Every outbound call passes through DialGuard before it reaches Twilio or Telnyx. It checks volume caps, warm-up status, number health, time-of-day rules, and rate limits — then either allows the call or blocks it with a clear reason. The goal is simple: protect your numbers and carrier trust so you can keep dialing without interruption.

The 7 guardrail layers

Layer	What it does	Status
1. Daily volume caps	Soft warning at 200 calls/day per number, hard cap at 450. Prevents any single number from getting burned by overuse.	Live
2. Account warm-up ramp	New accounts start conservative and increase over 11 dialing days (25 → 1,000). Builds carrier trust gradually.	Live
3. Number rotation	Least-used healthy number selected per call. Spreads volume evenly across your pool.	Live
4. Calling-hours enforcement	Only dials 8 AM – 9 PM in the lead's local time zone. Blocks calls outside compliant hours.	Live
5. Concurrency & rate limits	2 concurrent calls and 250 calls/hour per seat. Prevents burst patterns that trigger carrier filters.	Live
6. Number reputation	Auto-benches flagged numbers and removes them from rotation until they recover.	Live
7. CPS pacing	Spaces call-starts to stay under the carrier's calls-per-second ceiling at peak volume.	In rollout

Each layer has its own detailed article: Account warm-up, Calling hours, Number rotation, Number reputation, Concurrency & rate limits, and CPS pacing.

Server-side enforcement

All enforcement happens on the server before a call request reaches the carrier. This is a deliberate design choice — it means the rules cannot be bypassed by users, browser extensions, or direct API calls. When an agent clicks dial, the request passes through DialGuard's checks on the server. If any layer blocks the call, the agent sees a clear message explaining why (e.g., "Daily cap reached for this number" or "Outside calling hours for this lead's time zone"). The call never reaches the carrier.

This protects both your numbers and your team — agents don't need to think about compliance rules because DialGuard handles them automatically.

DialGuard in the Compliance Monitor

Every DialGuard layer reports its real-time status to the Compliance Monitor. Admins can see which layers are active, how close any number is to its daily cap, warm-up ramp progress, and whether any numbers have been benched for reputation issues — all from one dashboard.

Frequently asked

What is DialGuard?+

DialGuard is Asan CRM's server-side dialing safety system. It enforces 7 guardrail layers — daily caps, warm-up ramp, number rotation, calling hours, concurrency limits, reputation monitoring, and CPS pacing — to protect your numbers and carrier trust automatically.

Can DialGuard be turned off?+

No. DialGuard is always active and cannot be disabled. The guardrails are designed to protect your numbers and keep you dialing long-term. Turning them off would risk carrier bans and number flagging.

What happens when I hit a cap?+

You'll see a clear message explaining which limit was reached — for example, "Daily cap reached for this number." DialGuard will automatically route your next call through a different number if one is available. If all numbers are capped, dialing pauses until the next day.

Are limits per-account or per-number?+

It depends on the layer. Daily volume caps (200 soft / 450 hard) are per number. Concurrency (2 calls) and hourly rate (250/hour) are per seat. The warm-up ramp is per account. This layered approach protects at every level.

When will all layers be live?+

Six of seven layers are live today. CPS pacing (layer 7) is in rollout. The existing layers already keep normal and high-volume teams within safe carrier limits.

Was this article helpful?

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

Last updated 16 Jun 2026 · Applies to: Asan CRM