Traditional CTI services use a basic flow execution model to control the flow of calls. When a call comes in, the flow starts with call control actions like answering, transferring to a queue, and other simple actions.
The flow execution continues until the call ends, or the user initiates a hang-up command to stop the flow execution. However, this model is limited to call channels only, and other communication channels are not supported.
This was OK for traditional CTI service. But how can we provide this with CPaaS technology? How should we control the flow if the channel is not a call? The CPaaS supports many more communication channels, including voice, video, SMS, email, and others. To control the flow of all these channels, CPaaS providers should offer a unified interface that can control the flow of all channel types.
I implemented this called “Activeflow” in a VoIPBin service.
Activeflow is a powerful concept that provides a unified flow control interface for all channel types. It is created when flow execution starts and allows users to control the flow for any channel type. In VoIPBin’s implementation of Activeflow, customers can use the hang-up command for call channels and Activeflow’s stop command for all other channel types.
Overall, Activeflow is a critical feature that CPaaS providers should offer, as it provides a simple and unified way to control the flow of all communication channels. This helps users save time and increase productivity while managing their communication channels in a more flexible and customizable way.
This is details about the activeflow.
