Differentiate Missed Calls That Were Answered by Queues or Backup Extensions
Currently, when a call is routed to a user extension but not answered—and then picked up by a call queue or backup extension—the original user’s call log shows it as "missed." This can cause confusion for both end users and admins, especially when there is a valid call recording and the call was actually handled.
Proposed Solution:
Add a new call status such as "Forwarded & Answered" or "Missed by User, Answered by Queue" to better reflect the call path.
Display which extension ultimately answered the call in the call log (e.g., "Answered by ext. 13 – Dispatch").
Optionally, allow filters in analytics/reporting to separate unanswered missed calls from redirected answered calls.
Benefits:
Increases transparency in call routing and handling.
Reduces confusion and unnecessary support tickets related to “missed” call logs.
Helps teams better evaluate user and queue performance.
Clarissa
shared this idea