Build an IVR that Personalizes Every Call

Obsessed with personalizing every step of your customer journey? Tailor each call by integrating data from your CRM and other systems with communications APIs.

Learn More

Build an IVR that Personalizes Every Call

This article is the second in a three-part series on how to create a great communication experience with your IVR using APIs. Check out Part 1 to learn how you can update your IVR like you update your website, and Part 3 on how you can experiment with your IVR to keep up with changing needs.

Customers come in all stripes. No pizza joint worth its cheese would offer everyone who comes through the door the same standard-issue pizza. What about the meat lovers, vegans, and people who just want pineapple on their pizza pie?

Every customer has different needs, preferences, and circumstances for calling you. So how come when it comes to an IVR, so many businesses still keep serving up one-size-fits all menu?

It used to be that businesses were constrained by the available technology. But now we know that with APIs, you can change your IVR as easily as you change your website.

IVR phone trees built using communication APIs allow you to:

IVR Integration

Let’s take a look at what you can do with integration — we’ll get to experimentation in the next article.

Imagine This…

You just saw, your favorite pizza place, PieHard Inc’s ad in your facebook feed and now you’re craving for a slice. You call them up to order delivery and the IVR greets you by name and asks if you want to order a medium pizza margherita, your usual, or something new. “Just the usual,” you say.

You’ve just moved, so when the IVR confirms your delivery address, you choose to change it. The IVR tells you to check your text messages. When you do, you see the text from PieHard asking you to reply with your new address and zip code. You type it in, and in moments, the IVR confirms your new address. It reminds you about the free drink coupon you got in the email yesterday, which you confirm you want to apply to this order. The IVR asks if you want to use your regular credit card (you do), emails you a receipt, and says the pizza is on its way to you in a few minutes.

Whew, dinner accomplished.

Let’s Break Down What Just Happened:

IVR Diagram

It all starts with reaching PieHard Inc’s IVR built using Twilio Phone Numbers and Programmable Voice APIs. Twilio passes your caller ID to the PieHard communication application and waits for instructions on how to handle the call. Armed with the caller ID, the PieHard communication application queries the CRM for the customer record.

The PieHard communication application then uses the customer record to collect the caller’s recent browsing history from PieHard.com, its mobile app, or recent email interactions. It also queries the order system to see your previous orders and preferences.

This is how PieHard’s IVR can greet you by name and remember what you ordered last time.

PieHard knows the phone keypad is not ideal for entering alphanumeric information (like addresses). It used to have its IVR patch address changes through to its wait staff, who’d manually have to change it in the CRM.

Now that its IVR is built with a communications API, it can integrate not just with data sources, but also with text messaging. This allows PieHard to take your new address and automatically updates your customer profile in their CRM. This is how a seamless bridge is built between phone calls and messaging.

Final Thoughts

This fictional pizza place isn’t from the future. These types of experiences are possible right now. But PieHard doesn’t use a traditional legacy IVR hardware vendor because this level of integration and personalization would not be possible.

With an IVR built using communication APIs, integration with your website, email marketing provider, CRM, and other systems is seamless and easy.