Related articles

2.0 - Call-flow and Automation to process maps

Throughout our help center, you will find many articles that describe step-by-step how to implement use cases. As you will discover in our Common Setups and Use Case-Section, we link many articles that can help you solve the use cases we introduce there.

Those articles are usually quite technical but most start with a process map that might look something like this:

The aim of this tutorial part is to make you feel comfortable creating such process maps from the written description of your process.

Even though there is nothing forcing you to draw your process, we highly recommend it. These are three reasons why:

Call-flows and automation can get very complex. They usually exceed our capacity which might lead to mistakes and wrong implementations as we loose the overview.

And drawing your process will not only help you with your implementation, it will also make you rethink your processes and you might want to optimize them.

Even more important, process maps are a documentation. If you want to change something in your call-flow later on, visualization will be crucial for you to remember what you implemented maybe year ago or for any other person to understand how the call flow works.

Therefore, we recommend take your time and try to put your processes into process maps. You will get much better as soon as you understand babelforce more.