- •Per-session pricing becomes a ceiling on dialing at scale, forcing operations to calibrate to cost rather than contact strategy.
- •Capacity-based infrastructure charges per-minute on connected calls, not a fee for the right to attempt one.
- •The High Velocity Network supports approximately 150 calls per second per node, enabling predictive dialing and number rotation at scale.
- •High velocity accelerates reputation wear, so the carrier layer should monitor 487 rates continuously to rotate numbers early.
Per-session pricing is one of the most persistent cost structures in outbound voice, and one of the least understood. It looks manageable at low volume. At scale, it becomes a ceiling on how aggressively an operation can dial - not because of technology, but because of pricing architecture.
The collections operations that scale most effectively are the ones that separated their voice infrastructure from per-session pricing before they needed the capacity.
What does per-session pricing actually cost at scale?
Per-session fees - charged per concurrent call channel or active session - are common in hosted dialer environments and some UCaaS platforms. The model sounds straightforward: pay for the sessions you use.
The problem is what this does to dialing behavior at scale. A collections operation running 500 concurrent agents cannot burst to 2,000 concurrent sessions during peak hours without a proportional increase in session fees. Campaigns that benefit from high call velocity - short-duration, high-frequency contact attempts across large account portfolios - are constrained by a cost structure that makes bursting expensive.
The result is that operations calibrate their dialing to what they can afford per-session, not to what the contact strategy actually requires. The technology can handle more. The pricing architecture says no.
This is not a small inefficiency. In collections, contact rate is the primary lever on recovery performance. An operation that dials at 60 percent of its optimal velocity because per-session costs make full capacity uneconomical is leaving recovery on the table every day.
What is capacity-based infrastructure and how does it differ from per-session pricing?
Carrier-grade voice infrastructure built for high-velocity outbound does not charge per session. It is built around raw call-processing capacity - measured in calls per second - with per-minute pricing on actual usage. You pay for what connects and how long it runs. You do not pay a fee for the right to attempt a call.
| Per-Session Pricing | Capacity-Based (Per-Minute) | |
|---|---|---|
| What you pay for | Each concurrent call channel or active session | Connected call minutes only; no fee per attempt |
| Bursting to peak volume | Proportional increase in session fees | No capacity surcharge; burst when needed |
| Dialing behavior impact | Operations calibrate dial rate to cost, not strategy | Dial rate determined by contact strategy |
| CPS capacity | Constrained by session tier | ~150 calls per second per node (High Velocity Network) |
| Common environment | Hosted dialers, some UCaaS platforms | Carrier-grade outbound voice infrastructure |
This changes the economics of dialing behavior entirely. An operation that needs to dial aggressively during a three-hour morning window can do so without a capacity surcharge. A campaign that benefits from short-duration, high-frequency attempts - checking for right-party contact across a large account pool - is not penalized for the velocity that makes it effective.
Our High Velocity Network is built specifically for this profile. The infrastructure supports approximately 150 calls per second per node - among the highest capacity in the industry. That capacity is available to the operation when they need it. The pricing is per-minute on connected calls, not per session on attempted ones.
What does high CPS capacity enable for collections dialing?
Call-per-second capacity is not just a throughput number. It is what enables specific dialing strategies that low-CPS infrastructure cannot support cleanly.
Predictive dialing at scale requires the ability to initiate a large number of calls simultaneously and route the first connected party to an available agent. The higher the CPS capacity, the more precisely a predictive algorithm can operate without introducing artificial pacing delays that reduce efficiency.
Number rotation at high velocity requires the ability to move through a large number pool quickly, resting individual numbers appropriately while maintaining campaign throughput. Operations constrained by low CPS capacity either rotate numbers too slowly - burning them through overuse - or reduce overall dial rate to compensate.
Blended inbound and outbound campaigns require capacity headroom. When inbound volume spikes unexpectedly, an operation with tight CPS capacity has to throttle outbound to protect inbound call handling. Adequate CPS capacity means both can run without competing for resources.
How does STIR/SHAKEN and number reputation management factor into high-velocity dialing?
Scaling call capacity is not just a throughput problem. At higher velocity, number reputation management and STIR/SHAKEN attestation become more important, not less.
High-velocity dialing accelerates the rate at which numbers accumulate carrier-side behavioral signals. A number that would take three weeks to flag at moderate volume might flag in three days at high CPS. Operations that scale capacity without scaling reputation management burn through number pools faster than they can provision new ones.
The infrastructure handling capacity should also handle reputation monitoring continuously. Early degradation in 487 rates on specific numbers is a warning to rotate before the Spam Likely label appears - but only if the carrier layer is instrumented to surface it.
What should you look for when evaluating outbound voice infrastructure for collections?
When evaluating outbound voice infrastructure for collections, three questions cut through most of the noise.
What is the CPS capacity, and is it per-node or shared across the environment? Per-node capacity at 150 CPS is meaningful. Shared-environment capacity divided across clients is not the same thing.
Is pricing per-session, per-minute, or a combination? Per-session fees often apply to concurrent sessions above a contracted baseline, which reintroduces the scaling constraint at the tier boundary.
Is number reputation management included in the carrier layer? Unified monitoring running on live production traffic is significantly more accurate than a separate service running simulations.
The Bottom Line
Per-session pricing constrains dialing behavior at exactly the moments when aggressive dialing is most valuable. Collections operations that move to capacity-based, per-minute infrastructure remove an artificial ceiling on contact strategy - and often reduce carrier spend at the same time.
The technology supports the scale. The question is whether the pricing architecture does too.
Frequently Asked Questions
What is per-session pricing in outbound voice?
Per-session pricing charges a fee for each concurrent call channel or active session, common in hosted dialer environments and some UCaaS platforms. At low volume it looks manageable, but at scale it becomes a ceiling on how aggressively an operation can dial.
How does capacity-based infrastructure pricing work?
Capacity-based infrastructure charges per-minute on connected calls rather than per session. You pay for what connects and how long it runs, with no fee for the right to attempt a call and no surcharge for bursting to peak volume.
What CPS capacity does the Teams Plus High Velocity Network support?
The High Velocity Network supports approximately 150 calls per second per node, which the article notes is among the highest capacity in the industry.
Why does high-velocity dialing accelerate number reputation wear?
High-velocity dialing accelerates the rate at which numbers accumulate carrier-side behavioral signals. A number that would take three weeks to flag at moderate volume might flag in three days at high CPS, so reputation monitoring must run continuously alongside the carrier layer.
What are the key questions to ask when evaluating outbound voice infrastructure for collections?
Three questions matter most: what is the CPS capacity and is it per-node or shared across the environment; whether pricing is per-session, per-minute, or a combination; and whether number reputation management is included in the carrier layer with live production traffic monitoring.
How does per-session pricing affect collections contact rates and recovery performance?
Because contact rate is the primary lever on recovery performance, an operation that dials at less than its optimal velocity due to per-session costs is leaving recovery on the table every day. Capacity-based infrastructure removes that artificial ceiling on contact strategy.
