📋 What’s about
In a queue campaign, the dialer generates calls to contacts within a list and puts the call in a queue only when the contact answers the call. Available available agents in the queue will be able to answer and connect to the contact.
The XCALLY Motion Bull Dialer originates calls and waits for the contact to answer for a predefined Originate Timeout [secs]. If the contact answers before the timeout expires, the call is forwarded to the queue; otherwise, the call Originate Status will be set to No Answer.
Depending on Outbound Dialer Methods, calls are generated following a strategy:
In some methods, the system calls before the customer and when he/she answers the call, the system switches call to queue campaign, that switch call to agent. Once the call is placed in the queue, the dialer waits for predefined Queue Timeout [secs] and drops the call if the timeout expires before being answered by an agent in the queue.
In other cases the system calls before the agent and then the customer.
The XCALLY Motion Bull Dialer originates calls and waits for the contact to answer for a predefined Originate Timeout [secs]. If the contact does not answer before the timeout expires, the call Originate Status will be set to No Answer.
You can find the Queue Campaign section under the XCALLY Motion Bull menu:
♟️ Queue Campaign in 10 steps
Once the Queue Campaign is added, you need to edit it in order to configure its features:
selecting 3 dots of the specific Queue Campaign | clicking Edit Campaign and using the buttons on the top bar |
In fact you can:
Edit Campaign (explore documentation here)
Clone Queue Campaign
Add List (see step 6️⃣ )
Add Blacklist (see step 7️⃣ )
Add Team - Add Agent (see step 8️⃣ )
🔧 Troubleshooting
If the dialer does not start making calls, please make sure:
The queue campaign is Active
The global interval of the campaign is correct
The current time is within the time interval set
The time zone and the interval chosen for the campaign match
There are contacts in the list
There are available agent in the queue
The trunk is properly configured