modules:counter

Counter

Function

This module is designed to keep track a variable and increment every time the module is visited.
It is most commonly used to keep track the number of occurrence a section has gone through (ex: user attempts) before branching to different call flow.


Additional comparison conditions can be added / removed from the module by pressing the add and remove ( ) buttons.

If the comparison condition is true, the call path will be directed to the node to the side of the condition ( ).
If the counter does not match any of the conditions listed, the call will then go through the node at the bottom of the module ( ).


By default, the counter for the variable to be assessed starts at 0. Each time the call-flow passes through this module, the variable's value increases by 1.

The variable's name that is defined in the module comes from the module's title bar. It can also be referred to later in the call flow with that variable name.
The counter variable can also be reset by using the Set Variable ( ) module, in order to reset the attempt counter when a success attempt has occurred.


Common Use Cases

Use Case Description Example
Login
Attempts
The counter module can be used to keep track of the number of attempts before directing the caller to a different call path.

In this example, if the caller provides a wrong login information 3 times, the call will transfer to a representative instead of allowing the caller to continue to re-try the login.

Here is what happens each time the call goes through the module:
1) login_attmept = 1 - invalid_prompt and retry
2) login_attempt = 2 - invalid_prompt and retry
3) login_attempt = 3 - transfer

Comparisons

User may set the comparison terms

  • Equals to ( = )
  • Greater than ( > )
  • Lesser than ( < )
  • Greater than or equals to ( ≥ )
  • Lesser than or equals to ( ≤ )
  • Not equals to ( ≠ )

Module Settings

  • None
modules/counter.txt · Last modified: 2018/08/28 15:16 by admin