Help Center › Dialer Compliance › Concurrency & rate limits
Concurrency & rate limits
Each login can run up to 2 calls at once and 250 calls an hour. It stops a single seat from bursting like a spam dialer.
In one line: sudden bursts — lots of calls at once, or very fast — are a top trigger for carrier rejections and spam flags. These per-seat limits keep every login dialing at a human pace.
The limits
| Limit | Per | Value |
|---|---|---|
| Concurrent calls | login | 2 at a time |
| Calls per hour | login | 250 / rolling hour |
A 3rd simultaneous call, or the 251st within an hour, is held with a clear message rather than rejected. Both checks run before your daily warm-up cap, so a held call never costs you any of your daily allowance.
This is why each agent needs their own login. Ten agents sharing one login would be capped to 2 calls at a time between them — give each agent a seat and each gets their own 2 concurrent / 250 per hour.
What you'll see
The Compliance Monitor shows a live line per login, which turns yellow as you approach a limit:
Active now: 1/2 concurrent · Last hour: 132/250
Frequently asked
Why does each agent need a separate login?+
The limits are per login. One login per agent means each agent gets their own 2-concurrent / 250-per-hour budget; sharing a login splits a single budget across everyone.
What happens when I hit a limit?+
The next call is held with a clear message until there's room (a slot frees, or the hour rolls forward). Nothing is rejected and nothing is lost.
Does a held call use up my daily cap?+
No. These checks run before the daily warm-up cap, so a held call costs you nothing toward your daily total.
Are these limits per agent or per account?+
Per login (per seat). They sit alongside the per-account daily cap and the per-number caps.
Was this article helpful?
Thanks — we'll use this to make the docs better.
Last updated 16 Jun 2026 · Applies to: Asan CRM