✸ If you are not quite sure what a call flow is, we suggest you go back to our initial chapter that explains this part in detail.
Building call flows with babelforce is easy once you get the hang of it. To get started go to IVR call-flows > Call flows.
Each flow consists of Modules that you link together. Each module type serves a different purpose (you will see the overview below), they have specific settings that will allow you to create your flow.
Imagine building blocks - separately, each block doesn't tell you much about its full functionality. They are just pieces of different colors and shapes. However, if you connect them in the right way, you will see the bigger picture and what you can build with them.
That's also how our modules and call flows work. Each module has a different function and by itself, it may not look powerful. But if you connect the modules together, you will get a well-functioning call flow.
In the end, once you connect the modules, your call flow will look like a tree with your number as an entrance point. It could look like this for instance:
Each pictograph represents one module type. Below we will explain each of them.
Automatic Call Distribution
The module that you will always need is the Automatic Call Distribution (ACD). ACDs route a call into a call queue (customers may hear an audio recording while waiting). Without ACDs, you could not connect your customers with an agent. In the most basic call flow, we will discuss in the next section, you will only need to connect this module with a queue and a phone number and your team can start taking calls. The selections are defined in the setting section of the queue, but without the ACD you would never get the customer's call to the point of being selected at all.
The ACD also defines what's happening to a call that is not answered by one of your agents. You could, for instance, forward the caller to 'sorry' audio if non of your agents is available. This takes us to the next module type: the Audio Player.
Audio Players are what they seem to be (no hidden features): they simply play an audio file. They don't do anything else, therefore they are usually linked to other module types. Or they are at the very end of a flow, saying goodbye to a customer.
Often, Prompt Players will welcome a customer before they are forwarded to the queue, and they are in many cases used within an ACD (playing the queue wait music). So if you think back to the process maps from the previous chapter: The audio player was always green boxes.
They can actually be used for a number of really cool features - but we'll get to that when we discuss Local Automations.
You can imagine a Switch Node as a small program that makes numerous decisions based on a set of rules, all within a few milliseconds. In our process charts, these were those diamante-shaped purple decision points.
It's like being at an intersection with roads going in different directions to different destinations. Maybe you want to see your grandma? Or perhaps you want to go and buy a new chair? What's triggering your decision? Your grandma called and said she prepared your favorite cake - so are you hungry? Or maybe your back hurts terribly because your old chair broke? Where you go depends on the conditions and their priority at that moment you reach the junction.
The Switch Node obviously has no needs but you can feed it with certain triggers that are comparable to decision points at an intersection. Whatever way the call goes after entering the Switch Node depends on the testing of certain predefined conditions: Is the caller reaching you in or after business hours? From which number is the caller reaching the line? Is an agent logged into the system and ready to take a call? You can define as many conditions as you want and you can even test customer inputs in connection with the Input Reader. This leads us directly to the next module.
With Input Readers, you are able to store customer inputs. For instance, you ask the customer to select a language or to choose which type of problem they have and they make their choice with the dial pad. This module plays a prompt, stores the DTMF response (any number between 1 - 9, *, #) and it offers a range of settings and therefore great flexibility. Input Readers often work together with a Switch Node which reads the customer's selection, and forwards the call accordingly.
This is a small but useful module that makes it easier for agents working in multiple regions or for multiple brands to recognize a caller's origin. For instance, if an agent picks up the phone, the Agent Queue tells the agent which language the caller speaks. This module is used within the ACD module.
In case all your agents are busy or a caller reaches your line after business hours, the Voice Recording module makes it possible to store any voice message from your customers. They can easily be set up at the end of any call flow. The recordings can be pushed to your CRM or helpdesk or stored on your own servers.
A simple menu offers limited options for customers to make a selection. It is the simpler version of an Input Reader and can be used for directly routing calls to another module after a selection was made. The caller enters a numerical option, and based on this option is routed to a predefined module.
One disadvantage is the lack of a 'barge-in delay'. This means that customers cannot interrupt the prompt by pressing the number of their choice - they always have to wait until the end of the prompt. With Input Readers, however, barge-in can be configured.
The Transfer module is the easiest way to forward calls to office workers that do not work in Support or Sales but have a direct line. It can be configured by simply mapping the employee's phone number to this module and then linking the employee's device. This device can be reached via Agent ID number (SIP ID), mobile number, etc.
Now you know the basics. It's time to dig deeper into specific modules. Let's start with triggers.