To create a Call Flow, the components are dragged and dropped from the right-hand menu onto the desktop and linked together.
A call flow must always start with a Connect component and is then run through “from top to bottom”. The mouse wheel can be used to zoom in and out of the interface.
The components are connected via connecting lines and with the help of so-called ports. Only output ports can be connected to input ports via connection lines. Double-clicking on the connection line inserts a point on the line, which can be used to move the line freely on the desktop for a better overview.
Generally, components have both an input port and an output port. However, there are also components where an output port has been omitted because it is not required due to the scope of the function. For example, in the case of the Disconnect component, there is no outgoing port because the Call Flow is automatically terminated after the call is disconnected. The opposite is true for the Connect component, which is basically the first component in a call flow. An incoming port on this component is therefore not required. Furthermore, there are components that additionally have so-called error ports. These are always triggered in the call flow if an event defined in the component configuration occurs (such as the caller exceeding the maximum number of invalid entries or a queue timeout).
As an alternative to connecting components with arrows, you can use what is known as “portal mode.” In this mode, the visible arrow connections are replaced by invisible links between the individual components.
This is particularly helpful for large or complex flows, as it keeps the workspace more organized and makes it easier to understand the flow’s structure.
Above the component menu there are two arrows. These can be used to repeat or undo the last action(s) performed, and the help texts can be displayed and hidden by clicking the question mark icon.
If faulty JavaScript code is generated due to an error in the Call Flow Designer when creating a call flow and a new version of the Call Flow Editor app is then released, the faulty call flow must be opened and saved once with the new app. This is because the JavaScript code for the call flow is always generated based on the components in the Call Flow Designer shortly before saving. It is also advisable to check the individual component settings once again, as settings may have been added there for which – if not set – a defined default value applies.
In the Call Flow Designer, components can be copied and pasted using Ctrl+C / Ctrl+V – even across different flows. The structure and layout are preserved.
When pasting into other call flows, required elements (e.g., variables) are automatically carried over or recreated. This makes it easier to reuse existing logic and speeds up the creation of call flows. Audio files are not copied along with the components and must be added manually if needed.
