To guard against excessively long caller wait times, you can overflow queued contacts in the following ways:
|
Option |
The hunting rule will run when |
Expected wait time |
The contact is expected to be waiting in the queue for more than this number of seconds. The expected wait time is calculated at run-time based on the amount of time taken to handle previous calls and the number of calls currently queued. |
Current wait time |
The contact has waiting in the queue for this number of seconds. |
Queue length |
The number of contacts in the queue exceeds this value. |
Time since agent available (seconds) |
This number of seconds has elapsed since an agent became available. Where an agent is servicing several queues, this field can be used to set one queue with a lower priority than the others (since matching rules attempt to find the agent who will answer the call soonest). The field is commonly used on a hunting rule on an OUTBOUND queue to delay calls from an OUTBOUND campaign being routed to an agent, giving them time to answer contacts on inbound queues. |
Note: you can add as many hunting rules as required. A rule runs only when the one before is not able to route a contact to an agent. You can change the running order of multiple rules on the Edit Queue screen.
|
|
To overflow immediately when no agent is available to take calls:
To overflow when no agent answers within the timeout configured in the ACD treatment.