Handle queue callback requests
Open Callbacks in the user portal if your profile grants access to queues. A queue distributes calls to its agents. This list contains the callback requests presented to you.
Each row shows the name or number, the queue, the request date, the wait time in seconds, and the number of attempts. "No pending callback requests." is the state of an empty list after reload.
Call back or close
- Check the number and the queue.
- For an open request, click Call back.
- Wait for the response. The list is reloaded after the action.
- For a request already taken with no associated call channel, Retry makes the request available again. After reload, Call back can launch the new call.
Call back initiates a real call. List actions are unavailable while a request is in progress.
To end a request without a new callback:
- Click Close on the correct row.
- Enter a Reason.
- Click Confirm.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Reason | Explains the closure | Required, not empty after trimming spaces; input limited to 1,000 characters and server-side check limited to 1,000 bytes; accented characters may count for more | Request handled with the customer |
The closure is confirmed within the row; this screen does not offer a dedicated cancel button for this entry. No closure is sent until you confirm.
Check the result
After success, the processed row is removed from the current list, then the data is reloaded. In a queue's administrative history, these rows are read-only, showing their status and reason.
If it doesn't work
An error appears in the list or in a notification. Note its text and the time. Check the reloaded status before trying again to avoid calling back twice. The server verifies that a device is registered before taking the request. A request already taken by another agent or already closed is rejected. If the reason is rejected, check that it is not empty and shorten it, especially if it contains many accented characters. After a response timeout, the request may remain reserved while the call is being verified: wait for the reload. Scheduled campaign callbacks are described in Campaigns.
