When I’m collaborating with clients about exactly what content should be in their IVR, I notice that many of them have a “shopping list” of things that need to be in their menu. “We have to list all of the extensions in accounting in case someone’s hunting for someone specific.” Or: “We need to make sure that the after-hours extension goes to Frank if callers need immediate support.” would be typical requests that I get from telephony installers.
But *what if* (and this “perfect world” thinking here) – designers of IVRs and call flows thought about how quickly they can get callers through the IVR, in addition to the framework of where extensions need to go? Knowing that virtually nobody has *too much* time on their hands, why don’t more IVR designers have speed and efficiency at top of mind when writing a call flow script?
Especially if you’re designing a system for emergencies (flood/hurricane/wild fire warnings), urgent medical call flow, and even IT support carries with it a certain level of urgency that would benefit from a speedy pace and an overly-sensitive respect for the caller’s time and patience.
I’ve even called into IVRs that I’ve voiced in the past and wondered why I was “plodding” along. I became aware that a more rapid pace is best suited for most industries a few years ago – and now the IVRs I voice sail along, balancing that need for clarity with expediting the caller to support.
Here’s my checklist as to why the need for speed is essential when designing a call flow:
If It’s Medical, Urgent, or Technical Support-Driven, All the More Reason to Turbo
Nothing is more frustrating – when you’re returning a call about your MRI results – to encounter a long, lumbering phone menu that just doesn’t “understand” how urgent this information is to you. Same goes for calling your bank to report an unknown charge on your statement – you don’t want to waste time in a 21-option phone menu that isn’t getting you directly to help. Make sure – if your company offers urgent/critical/emergency support, that the phone menu “acknowledges” that and gets the callers speedily though the options.
Think About Attentions Spans and Patience.
We’re all used to bite-sized, fast-scrolled reams of information passing by us at rapid speed. That’s just the reality of our world. Unfortunately, this has made most of us very short on patience, and lacking in true, robust attention spans. While it’s a sad commentary on us as a people, if you are designing a telephony platform, it’s a good idea to always remember that callers can’t remember long menus of choices, and almost everyone is short on expendable time and patience.
Remember Your Last Time on an IVR.
I usually try to spend as little time a possible on the phone. When I do – and I encounter a particularly frustrating IVR – I’m in a flurry of taking notes in my head: “That was too many options. Those options are too similar. It’s too slow.” You don’t need to be an expert on call flow structure to remember how frustrated you were the last time you called a company and heard – repeatedly – “Your call is important to us.” It was torturous, and disingenuine. Make sure that you avoid everything you personally dislike in a phone system, when designing yours, and don’t feel obligated to include meaningless phrases in your system just because they’re prevalent in others.
Time Is the Greatest Commodity.
By escorting your callers rapidly and efficiently through your IVR, you are telling them that you acknowledge that their time is a premium and that you won’t be the one to waste it. Time is our greatest commodity, and very few callers will forget the company that wasted their entire morning by having them work their way through a lengthy IVR only to find out that their issue can’t be answered by a live a agent or that a live agent is not actually *ever* available to take their call.
When it comes to IVR call flows, speed is of the essence. The faster and more efficiently you can get the caller to their destination, the happier they’ll be.