Quick Reference
wait_for_silence
What Wait for Silence Does
The number of milliseconds of silence VICIdial waits for after a call connects before attempting AMD analysis. Setting this too low means AMD starts analyzing mid-greeting; too high delays AMD decision and adds latency to agent call delivery.
Recommended Configuration
| Center Size | Recommended Value | Notes |
| --- | --- | --- |
| 10–25 Agents | 1000 to 2000ms for most AMD configurations | Start conservative, monitor for 48 hours before adjusting |
| 25–100 Agents | 1000 to 2000ms for most AMD configurations | Scale gradually — larger operations amplify effects of misconfiguration |
| 100–500 Agents | 1000 to 2000ms for most AMD configurations | Consult ViciStack optimization team for enterprise-scale tuning |
How to Change This Setting
-
Navigate to Admin > Campaigns
-
Select campaign
-
Find Wait for Silence field
-
Enter milliseconds (e.g., 1500)
-
Tune based on AMD accuracy results
-
Monitor AMD false positive/negative rates after changes
-
Submit
Common Problems
Value of 0 causes AMD to analyze immediately — high false positive rate
Values over 3000ms add noticeable delay to call connection
Must coordinate with call_timeout and dial_timeout values
ViciStack Module
ViciStack’s AMD Optimization module automatically monitors and optimizes wait_for_silence based on real-time performance data from your operation. Instead of manual tuning, ViciStack continuously analyzes call outcomes, agent performance, and contact rates to recommend and implement optimal values — often catching configuration drift before it affects your numbers.
Frequently Asked Questions
What does wait_for_silence do in VICIdial? +
The number of milliseconds of silence VICIdial waits for after a call connects before attempting AMD analysis. Setting this too low means AMD starts analyzing mid-greeting; too high delays AMD decision and adds latency to agent call delivery.
What is the recommended value for wait_for_silence? +
The recommended range for wait_for_silence is 1000 to 2000ms for most AMD configurations. The out-of-box default is 0. Note that optimal values vary by operation size, campaign type, and carrier — use ViciStack's automated tuning to find your exact optimal configuration.
Can ViciStack automatically optimize wait_for_silence for me? +
Yes. ViciStack's AMD Optimization module monitors wait_for_silence continuously and alerts you when the value drifts outside optimal range. On qualifying plans, ViciStack can automatically adjust this setting based on real-time performance data — no manual intervention required.
Need Help Optimizing Your VICIdial?
Get a free performance audit from our team of VICIdial experts. We'll identify quick wins and long-term improvements.
Get Your Free Audit →