If a caller requests a callback but doesn't confirm the caller ID, RingCX will not be able to process the callback request.
This shows in RingCX Analytics as Callback Interactions Unaccepted (Call Result of Inbound ACD Queue Callback Incomplete). This definition would show that the system tried to initiate the callback but was not answered where as it was not actually triggered.
Suggest to expand the Callback results to include more granular scenarios such as
"Inbound ACD Callback Unconfirmed CallerID"
"Inbound ACD Callback Duplicate Request"
This will allow contact centres to have a significantly better understanding if they are accurately servicing their callback requests or why a callback may not have been initiated.
There is a big difference to a callback being executed but not answered to not being executed due to a system or user error.