I have been reviewing call logs since the new Analytics portal launched due to KPI impacts. I have found two issues in how RingCentral dispositions/tags a call that is questionable. I say questionable because I consulted with someone who manages an IVR system for 57M customers that I partnered with several years ago.
Scenario 1: Customer calls 800 number, selects a queue and is routed to voicemail.
Issue: RingCentral will tag the call as Abandoned when the call is sent to voicemail prompt which is correct tag. RingCentral then tags the same call again with Abandoned after voicemail is left. That makes for two Abandoned KPI dings for one call. This is new as of April 2019 after looking back through Nov - March data.
I am not sure how anyone is supposed to answer a call when it is in Voicemail so I believe this is an invalid tag for Abandoned since the call has already been tagged.
Call Example:
Scenario 2: Customer calls 800 number, selects a queue, then presses keypad # for another queue, call is routed to that queue and answered in the other queue.
Issue: Since customer selected another option while in IVR queue, that queue is dinged with Abandoned call tag. When the call is routed to another queue based on customer selection and call is answered, call is still left abandoned in original queue.
Plus the other queue never shows the call as Abandoned and is call count for both queues
Suggestion: Tag/disposition the call the same as when call first comes into 800# and customer selects an IVR option there.
Call Example: Caller pressed 3 on keypad routing to another queue. This call was tagged as abandoned and was answered in another queue.
Same caller pulled up in queue customer was routed to and does not show it was Abandoned here. (I would not expect or want it to either)!
We have a low call volume which is a good thing from one perspective and bad from KPI perspective based on how calls are tagged/dispositioned in the IVR for call routing.
Has anyone else had this issue or have you noticed it? If yes, were you able to develop a resolution for this?
Thanks,
Blue
I believe engineers need to review the logic behind dispositioning the same call twice like this one. Add an algorithm to prevent the same call as abandoned or allow the customer (our organization) the ability to decide how we would like the calls like this handled. Customers will play in IVR system and/or accidently press a key. The opportunity is to adapt in how customers play within the system and not apply negative KPIs. This is a false negative since it is only one call in the same queue.
We have to report raw data to our client and explain that this is how RingCentral dispositions their calls. Even our client disagrees with how this is dispositioned!
Thanks again,
Blue
Going with the current logic where a customer presses a key while in VM prompt taking them back into the queue. In this scenario, a customer could possibly do this as many times as they wish until someone answered (Or is there a limit). With that logic in a low volume queue, we could have 4 abandoned calls with one call into that queue. When a queue only has two inbound calls a month, that would place that queue in the negative with more abandoned dispositions than actual inbound calls. We sometimes only have 2 calls into this queue....
The Customer Service queue only exists because RingCentral enables users to press 0. Tier 2 has said this cannot be disabled and has to be allowed. Other IVR systems has the ability to disable certain key presses as an invalid option which would be ideal to guide users to options available!
I reached out to a former colleague and ran this past her. She agrees in how this is a double ding and as mentioned in my original post she manages an IVR system for a much larger customer base in the millions. When I reviewed we have a low call volume vs their high call volume the impact is felt even more.
In regards to the call being dispositioned as abandoned when customer selects an option for another queue that is a false metric in itself. The call is routed to another queue where it was answered and needs to be treated as a routed call similar to when call comes into 800# and customer selects a option.
My background - I have worked with IVR systems with another company for 10+ years and metrics even longer with a top 4 telecommunications company in customer management for their call centers
I reached out to an analytics manager and was advised:
The first case there might be the following scenario: a caller picked a Queue and was routed to VM. He heard the prompt but did not want to leave a VM. So he might have decided to try again and get connected to a queue agent. While the VM prompt was on he pressed # and the Queue number again, so he was redirected to the same queue. since the queue has a setting to redirect all calls to VM the scenario was the same. A caller heard the prompt and left a VM. Since there were 2 calls to the same queue within one call session the first try (call), we fix the result as abandoned (no VM left) and the second try (call), we fix the result as VM/abandoned.
For the second case, a caller selected a queue and while he listened to the queue greeting he changed his mind and used the same scenario as before-- pressed # and another queue number. He was redirected to EVARS queue. As there was a call to the first queue (customer service) we are to display the call result - there was no live talk - it's abandoned. The caller was switched to the second queue and was answered. We show the result for the second queue as answered. In call session we display that there were 2 queues involved, so there results displayed are also for 2 queues.
A new Community is coming to RingCentral!
Posts are currently read-only as we transition into our new platform.We thank you for your patience
during this downtime.
Try Workflow Builder
Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!Try RingCentral Workflow Builder
