Adam’s Continuity at BlackAcid

Developing an IVR can immediately be a daunting task if you have not had any experience doing so before. To simplify it, Twilio.com came up with a solution that takes the complicated choices in technology away from the project. You will immediately start to think about your call system instead of which text-to-speech solution should we go with, which software pbx technology to implement, how much will our phone costs be, can we afford it? Wait, what about multi-lingual call handling? Don’t get me wrong, I like to build systems, asterisk is quite fun to get dirty with, but you can’t do both and have immediate results.

So after whiteboarding your idea, you want to start out with a menu system. I’d recommend splitting up the greeting from your initial menu. For example in TwiML, do a call redirect from the greeting to your menu.

[The requested file ivr-twilio/welcome.xml could not be found]

Menu’s should be simple, they should also conform to the same usage standard through every call screen.

Some common dial keys that have been recommended by others are:

• * – Repeat
• # – Go back
• 7 – Previous
• 9 – Next
• 0 – Operator

Also, when asking for user selection, keep the number of choices to 5. Have them enter 9 for more options. With menu’s always make sure to gather input at anytime to allow quick navigation for experienced phone users. Here’s an example of a call menu with TwiML.

[The requested file ivr-twilio/menu.xml could not be found]

When you want to build a search interface into your IVR, you need to make it simple, but also make sure you accept all input and handle all operations normally. People really want to press 0 when it doesn’t work. Additionally, you need to keep track of the number of search failures and offer a solution. In most cases, a dial out to a human will suffice. In the case of no man power, I recommend a voicemail using TwiML’s record tags. Here’s an example search interface:

[The requested file ivr-twilio/search.xml could not be found]

When you have too much data, too little structure, and need to tell the phone user a book, don’t. Give them options, a details menu is a good thing. If you provide information such as phone numbers, add an option to redirect the call. If you have related information or you are nested one level deep in a list, offer the option to go directly to the next item. It’s important to provide this level of navigation as it will save them time and you money on your minutes.

Voicemail systems are not complicated, but are difficult to maintain. Fortunately, for us we don’t have to worry about that, we just want to send the recorded message to the right dept. Handle your voicemail successes & failures accordingly. Have the user try again if the voicemail fails and always provide a fail-safe redirect so that they can try something else if they can’t leave a voicemail at that time.

[The requested file ivr-twilio/voicemail.xml could not be found]

Next up, I’ll talk about Robo-Calling!