IVR Builder Software
Author Image

By: Aivis Olsteins

In News

2019-04-04

IVR Builder Software

Requirements and components of a modern IVR building software system.

In earlier posts I have discussed how IVR can help reduce number of agents required in a call center, and the use of text to speech versus prerecorded messages. Now let's discuss what other characteristics an IVR system would ideally require.

  1. Flexibility. The IVR systems of are almost never static. Usually their requirements change with time, as business requirements change. An auto responder may be required to change schedules as business schedules change, or inbound call distribution may change as staff or department response change. Therefore IVR software should be built in a way that it is easy to modify. Be it a phrase in text to speech, or a file to play, or different number to respond to. It should not require a programmer to update such small day to day tasks.
  2. Feature set. A large selection of features is desirable: playing and recording voice files, text to speech, speech recognition, various touch tone (DTMF) detection ways (like long strings or single press commands), possibility to connect with 3rd party APIs and databases. Besides that IVR should possess ability to do some arithmetic, logic and string manipulation operations, like combining strings to pass to text to speech, or calculate numeric values. It should also have built-in flow control logic, like loops, conditional branching (if, then, else) and iteration support.
  3. Monitoring and Alerting. The IVR system should offer tools to constantly monitor its status and alert in case of critical incident. As with any telecom system, always on and instant incident reporting is crucial for interrupted service delivery.
  4. Extensive Reporting. IVR is mostly an automated system, and what is going on between it and the user, is not directly visible to the operator. Operator might not see if users are able to successfully navigate through the IVR flow and reach the goal, and at what point they are likely to drop off. Therefore extensive logging and reporting is essential: to be able to follow users navigation through the flow in order to reveal possible issues.

For a demo of our IVR Builder, please see this interactive online demo page.

 

Leave a comment
About Author
Author Image

My name is Aivis Olsteins and I am owner of DataTechLabs. My experience in Telecoms started in early 1990's and I have worked in multiple technical positions in mobile, messaging and data networks. My expertise lies in telecom networks, database systems, distributed processing and large data analysis. These posts are my attempt to share my knowledge with everyone who might find it useful.

Get in Touch

If you have something to say, please use the contact form below to get in touch with us. We will get back to you as soon as possible.

Mail Us

DataTechLabs SIA, Muzikas str 12A
Jurmala, LV-2008, Latvia.

Call Us

+371 67 66 09 01
+ 1 202 499 1550

E-mail Us

info@datatechlabs.com
support@datatechlabs.com