There’s a huge temptation – once an IVR script is written, approved, sent to a voice talent to record, and finally installed – that it’s a self-sustaining entity which requires no supervision or monitoring.
Sadly, this is not true – and this thinking could comprise your company’s credibility and reputation.
IVR – or Interactive Voice Response – is a way for customers to navigate into a customer relationship through your phone system. By listening to the various choices and selecting the option they need (or perceive that they need), they can search for a solution in a turnkey way. Rather than have a live answer designate department with which to send to the call, the menu choices offer a turnkey way for the callers to route their concern or issue themselves.
And *if* the choices are clear enough, distinct enough from each other, and ultimately are well staffed to handle the live contact portion, all will be fine.
That’s a big *if*.
All too often, a company can be aware of callers abandoning the process and dropping off, but it’s essential to know exactly *where* in the menu you’re losing them – and *why*. It’s likely – that if there’s a similar point where callers quite the call – that it’s a “bottleneck” which needs to be corrected.
Deploying the correct software that will supply analytics is crucial to obtain the metrics of caller loss.
But here’s some tangible, hands-on things you can do to minimize any universal fault points in your IVR navigation:
Keep your choices narrowed down, distinct, and short
Anyone who has read my blogs – in the 20+ years I’ve been writing about improving IVR – knows that I evangelize about choosing a *few* options in an opening menu (no more than five), front-stacking them in order of urgence/importance, and making the choices distinctly different from each other (have you ever been navigating through a phone tree and you’re perplexed, because the choices seem too similar? I have.)
Test, test, and test again
I’m a big advocate of people calling into their system and trying it out for themselves. Get staffers to join in the testing process. Seeing (and hearing) the system though the caller’s perspective can identify sticky points and make you aware of any points in the menu which sound confusing, awkward, or just plain don’t make sense.
Deploy tracking software
VICIdial – a fantastic client of mine – offers an “Inbound IVR Report” as part of their VICIdial Call Center Suite which can show each step in the IVR and how many callers went through the IVR in a specific path – essential data to have in order to determine bottlenecks in the system and rectifying them. You can check it out here: www.vicidial.com.
Change as needed
Many companies wanting to get their IVR up and running thin of their prompts as a “one and done” situation – once it’s operational, it’s written in stone. IVRs need to be changed for many reasons – changes in hours (think: COVID modifications), changes of staff (especially noticeable when you have a phone tree listing staff and extensions) and changes which are needed when glitches in the system are identified.
Think of your IVR/Call center prompts as a living, breathing entity which requires monitoring and care, and a dedication to improving the process.