Burst headroom: short spikes included.
$0
for a short burst above your streams
Every voice fleet has two sizes: the ordinary day and the spike. Your streams price the first. The spike is included: a key at its stream count can still open extra lines for a short burst, at no extra charge.
The mechanics
- A key at its stream count can still open up to half again its streams, at least one extra, so a spike connects instead of ringing busy.
- A call that is already going is never cut off, whatever happens to the count.
- If a key runs over for long stretches in a day, new extra calls are declined at connect with a clear concurrency error (WebSocket close 4429), so your agent can retry or fall back, and we reach out about adding a stream.
The headroom, stated
Headroom is deliberately simple: half again your streams, at least one extra, at no extra charge. It covers the short peak; a busy hour that always runs over is the signal to add a stream.
table 01
Lines at once during a short spike
| Your streams | Burst headroom | Lines at once |
|---|---|---|
| 1 | +1 | 2 |
| 5 | +2 | 7 |
| 10 | +5 | 15 |
| 20 | +10 | 30 |
Where burst earns its keep
The workloads that spike by calendar, not by trend: the 8 AM Monday wave, a launch-day rush, the end-of-quarter dialer push. Headroom carries the short peak; a spike that lasts all day is the signal to add a stream.
Notes
Do I have to enable burst?
No. Every stream key has the headroom from the start, and it costs nothing extra.
Is a burst line slower than a regular one?
No, a burst line is the same serving path with the same measured figures. Burst headroom is a limit on the key, not a separate tier.
A key, one stream, your own script, nothing on it counted while you build.
Get a key, run your own script