dead_trigger

What Dead Trigger Does

Specifies the action to take when a call is detected as ‘dead’ — meaning the far end has hung up but the channel is still technically active. Properly handling dead calls prevents agents from being left on empty channels and reduces wasted agent time.

Recommended Configuration

| Center Size | Recommended Value | Notes |

| --- | --- | --- |

| 10–25 Agents | DEAD or valid extension for dead call handling | Start conservative, monitor for 48 hours before adjusting |

| 25–100 Agents | DEAD or valid extension for dead call handling | Scale gradually — larger operations amplify effects of misconfiguration |

| 100–500 Agents | DEAD or valid extension for dead call handling | Consult ViciStack optimization team for enterprise-scale tuning |

How to Change This Setting

• Go to Admin > Campaigns

• Select campaign

• Find Dead Trigger setting

• Set to DEAD to use the built-in dead call handler

• Or enter a dialplan extension to handle dead calls with custom logic

• Reload dialplan if using custom extension

• Submit

Common Problems

Leaving as NONE causes agents to sit on dead calls until they manually hang up

Dead call detection sensitivity varies by carrier

Conflicts with wait_for_silence setting

ViciStack Module

ViciStack’s Dialer Tuning & Auto-Configuration module automatically monitors and optimizes dead_trigger 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.