Second and third agent alerts: escalation when nobody answers

Every call that reaches an agent plays a short alert sound, usually a simple ding, so the agent knows a live caller is on the line. That works fine for a steady stream of strangers. But some callers are not strangers. They called five minutes ago, got dropped, and are trying again. VICIdial lets you play a second or third alert sound for exactly those people, so the agent hears something different and treats the call accordingly.

What the second and third alerts actually do

The first agent alert is the baseline ding that fires on any call into the in-group. The second and third alerts are conditional. Each one has a trigger, and the sound only plays when that trigger matches. The most common trigger checks whether the same person called this in-group recently. You give each alert its own audio file, so the agent can hear by ear whether this is a fresh caller or a returning one.

You can match on the customer's phone number or on the specific lead record. Matching by phone number catches anyone calling from the same line. Matching by lead is tighter and ties the repeat to one known contact in your system.

The trigger window and what counts

Each alert has a trigger seconds value that sets how far back the system looks. The default is 600 seconds, which is ten minutes. So with the phone trigger, if the same number called the in-group within the last ten minutes, the second alert fires. Stretch that to an hour if your callers tend to wait a while before retrying.

You can also tell the trigger which previous calls to count. Some trigger options only count earlier calls that timed out as a drop, which is useful when you specifically want to flag people you already failed once. Others also count calls that were handled with no agent available. There is even a container option that lets the system search across a list of related in-groups instead of just the one, so a caller bouncing between two queues still gets flagged. Worth understanding the difference between a dropped call and a queued one is covered in our piece on Drop Call Seconds.

When you actually want this

The classic case is a support line where a caller got cut off mid-conversation. When they call back, a sharper alert tone tells the agent to lead with an apology rather than the standard greeting. Sales teams use it too: a hot Lead who calls twice in ten minutes is more likely to buy, and the agent should know that before they pick up. Each option also has a delay in milliseconds before the call connects, and an only setting that suppresses the first ding so the agent hears just the escalated sound rather than both. None of this touches the call's Disposition; it only changes the sound the agent hears.

Keep the alert audio short and obviously different from the standard tone, or your agents will not register the change. These alerts sit alongside other in-group routing controls, and you can see how they fit into the bigger picture in our guide to inbound call handling. The alert never changes where a call goes, only how it sounds to the Agent who answers it.

Repeat callers in an Ingroup are a signal worth catching, and an escalating alert is one of the cheapest ways to act on it. If you want this kind of inbound control without managing your own server, see what is included on every plan over on our pricing page.