Callflows
A Callflow is the definition of how SIP Caller will interact with your contacts, once the call is established. But usually the interaction should not be the same if the call is answered by a human or an answering machine. This is why we perform real time speech analysis, to identify the answering endpoint, and let you configure a different Callflow for the case of human answer, and answering machine. By doing this, for example, you can run a survey when a human answers the call, and just leave a message if a voicemail is detected.
You can create callflows in 2 ways:
The easiest way to do this is using templates. We provide templates for the most common use cases, which you can use from a step by step wizard. And when you have a scenario not supported by the standard templates, you can use the designer to create it according to your needs.
To create a Callflow using templates, go to “Callflows” > “Create from template”. You can choose any of the following templates:

To create a Callflow with the designer, go to “Callflows” > “Create with designer”. You will be asked to provide a name for the callflow, and then you can start adding actions. Actions are executed from top to bottom.
The issues indicator in the toolbar shows whether the callflow has any problems while you’re designing it. Click it to see the list of issues, and click an issue to jump to the action that has it. Actions with issues are also marked with an error icon on the canvas. Campaigns using a callflow with issues won’t start until they are solved.
To add an action, click the plus (+) button on the canvas where you want to insert it, and choose the type of action you want. The new action is selected right away, so you can configure it in the Properties panel.
The available actions are the following:
To configure an action, click it on the canvas. Its settings are shown in the Properties panel on the right (at the bottom on small screens), and every change is applied to the action as you type. Press Escape or close the panel to clear the selection.
To delete an action, select it and click the delete button at the top of the Properties panel, or press the Delete key. You will be asked to confirm before the action is removed.
You can also collapse and expand an action with the arrow on its upper right corner, to keep large callflows easier to read.
This action requires 1 setting:
Message: this is the text of the prompt to play. The message can be static, or have variables, to play a different prompt on each call, for example an appointment date, a due balance, and so on. Variables are specified in square brackets:
Hello [CustomerName], you have an appointment with us on [AppointmentDate].
You will be able to provide variable values for each call when uploading the numbers for the campaign.
The message can be plain text, or SSML to customize the generated audio by providing details on pauses, and audio formatting for acronyms, dates, times, abbreviations, or text that should be censored. More information here, here and here.
This action requires that you upload a WAV file with the following format:
Once the file is uploaded, you can play it from the Properties panel to check that it sounds as expected. To replace it, click “Upload” again and select a different file.
This action performs the following steps:
You must specify the minimum and maximum number of digits to collect, and a name for the input. This name is used in reports to show how your users are answering to this action.

Each DTMF Input action has outputs, which let you run different actions depending on what the user enters. Outputs are managed from the “Outputs” section of the Properties panel: to add one, enter the value in the “Match” field and click “Add”, and to remove one, click its delete button. Select an output, in the Properties panel or in the tabs at the bottom of the action, to show its actions on the canvas, and add the children actions there. For example, if you want to play a prompt when the user presses “1”, you need to add an output for the value “1”, and then add children actions to it. If the input is considered valid but there is no specific child branch that matches it, then the actions from the “Valid” branch are executed. If the input is invalid or no input is detected, the actions from the “Timeout / Invalid” branch will be executed once all attempts have been consumed.
This action requires 3 settings:
[AgentExtension]
You will be able to provide a value for each call when uploading the numbers for the campaign.
This action has no configuration parameters, and will drop the call when executed.
Actions can be moved around. To do this, click on an action and drag it. You can drop it on any plus (+) button, when you hover this button you will see that it’s highlighted, indicating that it’s ready to accept the action.
The Callflows section lists by default all the callflows which are not archived. A dot on the left of each name shows whether the callflow is ready to be used:
From the Actions column, or by selecting a callflow in the list, you can:
Callflows are editable as long as they’re not being used by a campaign. Once a campaign is started, the Callflows being used by it are automatically switched to read-only mode. This is to avoid issues with statistics.
If you need to create a campaign using a slightly different Callflow, you can always duplicate an existing Callflow, and make the changes to the copy. Then you configure your campaign with this new Callflow.