Engineering capabilities
- List and campaign management
- Answering-machine detection tuning
- Retry and timezone rules
- Agent availability pacing
VoIP
Auto Dialer
Automated sequential dialling from a list, connecting answered calls to a waiting agent u2014 a middle ground between manual dialling and predictive pacing.
Security & hardening
- Do-not-call list enforcement
- Calling window controls
- Trunk rate limiting against abuse
Auto dialler campaign architecture
Sequential automated dialling with answered calls handed to a free agent u2014 pacing follows agent availability rather than statistical prediction.
-
01
Campaign data
- Lead lists
- Timezone rules
- Retry policy
Calling windows enforced per timezone; retry counts and intervals defined per list.
-
02
Dialler
- Sequential pacing
- AMD tuning
- Agent availability
Answering-machine detection tuned deliberately u2014 aggressive settings drop live humans.
-
03
Call control
- Outbound routes
- CLI per campaign
- Recording
Separate routes per campaign so cost and reputation are attributable.
-
04
Carrier
- Trunk concurrency
- Rate limits
- Fraud alerts
Concurrency ceilings agreed with the carrier before campaigns ramp.
Frequently asked questions
How is it different from a predictive dialler?
An auto dialler places calls one at a time as agents free up. A predictive dialler dials ahead of availability using statistics, which raises talk time but introduces abandon risk.
What causes the awkward silence at the start of calls?
Answering-machine detection deciding whether a human answered. Reducing that delay is a tuning exercise, traded off against false detections.
What capacity do we need?
Trunk concurrency is sized from agent count, average call length and connect rate, with headroom u2014 undersized trunks cause failed calls, oversized trunks cost money.
Scope the work before you commit budget
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.