Help Center › Dialer Compliance › Carrier-rate (CPS) pacing

Carrier-rate (CPS) pacing In rollout

As your combined call volume grows, Asan CRM briefly paces new calls so you stay under your carrier's calls-per-second ceiling — nothing gets rejected.

This protection is rolling out. The controls already live — warm-up, rotation, and per-seat concurrency — keep normal volumes comfortably within carrier limits, so most teams won't reach this ceiling before it ships.

Why it matters

Carriers cap how many calls can start per second across a connection (your carrier publishes a calls-per-second, or "CPS", limit). That ceiling is shared across everyone dialing at once, so at high combined volume a sudden cluster of simultaneous call-starts can get rejected — even if each individual seat is within its own limits.

How it will work

When combined volume approaches the ceiling, Asan CRM holds new call-starts for a moment and releases them as capacity frees up:

You click dial once — the call starts itself the instant there's room. No re-clicking.
It's visible — a brief "pacing your calls" indicator shows it's working, not stuck.
Nothing is dropped — calls are spaced out by a fraction of a second, not rejected.

What you'll see

During peak volume, a short "High volume — pacing your calls" indicator appears on the dial control. At normal volume you'll never see it.

Frequently asked

When would I actually notice this?+

Only at high combined volume across many seats at once. Small and mid-size teams stay well under the ceiling and won't see pacing at all.

Will pacing drop my calls?+

No — it spaces call-starts by a fraction of a second and they fire automatically. It's the opposite of a rejection: it's what prevents one.

Is this live now?+

It's rolling out. Until it's live, the warm-up, rotation, and concurrency limits keep your volume within 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