Concurrency, not minutes
Dialler traffic is bursty. A campaign can request dozens of simultaneous attempts within a second, and a trunk sized on average usage will reject calls at exactly the moment the operation is trying to work. Capacity is planned on peak concurrency with headroom.
Integration
We connect to the contact centre platform or the SBC in front of it, over SIP. Your platform keeps the queueing, agent routing, recording and reporting; Voicetelo carries the calls and provides the records behind them.
- SIP connection to platform or SBC
- IP authentication for static environments
- Capacity aligned to dialler peaks
- Records for every attempt, answered or not
Numbering
Inbound numbers can be provisioned per campaign, per market or per client and routed independently, which keeps reporting clean without changing the platform configuration each time.
Explore DID NumbersAnswer rates and quality
When answer rates fall, the cause is usually in the numbers rather than in opinion: ASR, PDD and cause-code distribution will show whether calls are being rejected, delayed or dropped, and where. Those measures are what we will look at with you.
Outbound compliance
Outbound campaigns carry obligations that vary by jurisdiction — consent, calling hours, identification of the caller, do-not-call handling and recording notification among them. These rest with you as the party making the calls, and traffic must comply with the Acceptable Use Policy.