Ability to view the key presses made by the caller in the performance report
Ability to view the key presses made by the caller in the performance report.
Currently, customers must contact us to determine what occurred during a call and why it was routed to a different extension.
This process would be simplified if there were an option to view this information in the performance report or detailed call logs.
For example, a caller contacts a call queue number and while waiting accidentally presses a key such as #2, resulting in the call being routed to that extension. Currently, to determine why this occurred, then trace the call using Internal tool. However, if customers had the option to view these details in call logs or the performance report, they would not need to contact support and could immediately determine why the call was misrouted.
Josoel
shared this idea