Example of an Incomplete IVR Tree Design

I have lived in the US for a while now; in fact, I am celebrating 1 year of living here this weekend. One of the things that I learned quickly was the need to register all  phone numbers with the Do Not Call Registry (www.donotcall.gov). However, life is not that simple and you can end up on someone's list.
I am not sure how my cell number got on Wells Fargo's campaign list. I mean, either the bank is calling the previous owner of my number or someone else just wrote their number down wrong. Either way, I started getting these automated Wells Fargo IVR campaign calls: "This is an important message for XY regarding card services. If this is XY press 1, if not press 5." (or something similar to that). The IVR tree is smart enough to eventually offer the option of "this is a wrong number," but when you go on that path, it tells you to call a generic 1-800-???-???? number. That's exactly how much I remember from that number and that's the problem. I always get the call when I am not able to write the number down. Would it be such a huge problem to repeat it a second time? Also, if you really need to talk to me, and just selecting the option of "this is not a correct number" is not enough, why doesn't the IVR offer the option of being connected to an agent? Or why not send a text message to the number saying, please call this number to be taken off the list. I have nothing against Wells Fargo, but this is fantastically annoying.
So when designing your IVR tree, think about the other side - the recipients of your calls - and account for all possible scenarios thoroughly.

 

@MichalGrebac (www.twitter.com/MichalGrebac), 2Ring

Posted by Michal Grebac

Related Press Releases

Statement from 2Ring regarding Mozilla.org Add-on

Mozilla.org has temporarily disabled a 2Ring add-on in its Firefox Add-ons catalogue due to policy violation concerns.
More

2Ring Gadgets for Cisco Finesse v4.3.1-4.3.6

2Ring Gadgets for Cisco Finesse is a set of simple, open, and smart tools for improving productivity and user experience across all Cisco Contact Center platforms (Express, Enterprise, and Packaged UCCE).
More

IMPORTANT: Potential loss of functionality of 2Ring Gadgets after upgrading Google Chrome to version 80

This is a very important message for all 2Ring customers whose agents or supervisors use Cisco Finesse with 2Ring Gadgets for Cisco Finesse in Google Chrome.
More

2Ring Gadgets for Cisco Finesse v4.3

Details on what has been added to 2Ring Gadgets for Cisco Finesse v4.3 - adding support for ad-hoc integrations, a brand new UI for 2Ring Team Gadget - enhanced agent roster, current dialogs for UCCX chat and email, ..
More

2Ring Scripts & Forms v3.2 - Release Notes

2Ring Scripts & Forms v3.2 - adding support for newer MS SQL Servers, and forms now support pre-selecting dates, and come with a new card type - a drop down list.
More