Customer first callbacks overview
When you configure callbacks, you must choose to first route the callback to either the agent or the customer. By default, Genesys Cloud enables Agent First for callbacks in a queue. Alternately, you can choose Customer First to direct Genesys Cloud to connect to the callback recipient before an agent accepts the interaction. After the system determines that the customer is available and ready to speak to an agent, then the interaction routes accordingly and keeps the position in the queue.
For more information about customer first callbacks, see Callbacks FAQs.
Customer first callback settings
The Customer First callback option enables Genesys Cloud to dial the customer before connecting the interaction to an agent. When you select Customer First, configure the settings in this table.
- Genesys recommends that you do not use voicemails in customer first callback queues. Because voicemails also dial to the customer first, the agent cannot listen to the voicemail before the customer connects. Voicemail and customer first callbacks are unsupported.
- Customer first callbacks use the default trunk caller ID to make outbound callbacks and currently does not support prioritized caller selection to configure caller ID information.
- Customer first callbacks are treated as inbound calls and use the voice script for callbacks. Genesys currently does not support callback specific agent scripts.
Setting | Options |
---|---|
Agents can schedule a callback in advance for |
To determine the duration of agent callback ownership and scheduling access, use the up and down arrows to define how far in advance agents can schedule owned callbacks. The minimum time is one hour; the maximum is 30 days. |
Live Voice |
Click the list and select the method that you want to use when Genesys Cloud detects a live voice.
|
Answering Machine |
Click the list and select the method that you want to use when Genesys Cloud reaches an answering machine.
For all other call progress outcomes, Genesys Cloud dispositions the call with the outcome code and does not retry unsuccessful outcomes. For more information about in-queue and inbound flows, see Create a flow. |
Pacing Modifier |
Enter a modifier value to derive the number of callbacks that the system places at a time. The number of callbacks that the system dials is a combination of the pacing modifier and the number of online agents. The system checks the number of agents that are online and does not consider the agent status. The number of callbacks at a time are directly proportional to the value of the pacing modifier. The higher the value of the pacing modifier, the higher the number of callbacks. Genesys Cloud uses this modifier to calculate a coefficient that is multiplied by the number of agents that are logged on to the queue to determine the number of callbacks initiated at one time. The pacing modifier does not consider the status of the agent; for example, idle or interacting. If an agent is in available status in the queue, then Genesys Cloud multiplies the calculated coefficient by the online agent count. Notes:
|