Automated outbound queue
It checks the list every twenty seconds and dials one line at a time, with a pause between calls.
DESKTalk to our teamManage outbound calls within each customer’s working day. Schedule requested callbacks, apply retry rules and stop when a contact needs your team’s attention.
Available capabilityA customer in Chennai said "call me tomorrow at eleven". Terramine Desk calls at eleven in Chennai, not in Dubai. No answer? It tries twice more, then again the next morning, then marks the contact as not working and asks someone on your team to decide.
It checks the list every twenty seconds and dials one line at a time, with a pause between calls.
It only rings during business hours where the customer is, worked out from their address or, failing that, their phone number.
No answer? Out of the box it tries again ten minutes later and ten minutes after that, then at nine the next morning their time, and once more an hour later. After that the lead moves to Contact not working.
"Call me Thursday at three" becomes a callback at three their time, and a callback promised without a time defaults to ten in the morning.
Call next, call off or move to the front, and the reason the agent won't ring a lead, shown on the lead's card.
A call the network couldn't place doesn't count as an attempt, and after three in a row your team is told.
A call opens in the language of the country it rings, by a rule you set: Portuguese in Angola, Spanish in Argentina, Russian in Kazakhstan. A customer's card can name its own, one card or a whole selection at once, and the colleague who speaks it makes the call, or the agent that speaks them all makes it in a native voice.
How many calls on the first day, how many on the next, and the wait between them are set in the column's head for every lead in it. Save, and the calls already planned move to the new rule.
The guided demo illustrates a selected workflow. Availability depends on the enabled configuration; beta items are labelled above.