3.3 - Building triggers

We already gave a short introduction to triggers in this article. Now we are getting serious. You will learn how to create your own triggers and make use of them.

Introduction to triggers

Triggers describe a certain condition. They don't do anything on their own but you need them for making your calls go where you want them to go.

For instance, in the call-flow we are analyzing in this section, we have four triggers:

  1. One checks if business hours are not true. So if a call reaches the platform after hours it returns TRUE.
  2. Another checks if a calendar is true. So if you entered an exceptional holiday and a call reaches the platform at that time, it will also return TRUE.
  3. The third looks if there are any agents logged in to take calls. If there are it also returns TRUE.
  4. The last one checks the queue wait time (how long hast the customer been waiting in the queue)

So that's what we do with triggers. We define conditions and based on whether or not they are true a call takes a certain route in your call flow. Triggers are only useful if you combine them with modules or events. But you cannot build a call flow without them.

Let's look at how triggers work and what you can do with them.

Creating triggers

Every trigger consists of at least one

 

  • Expression
  • Operator
  • and in most cases an Expectation

mceclip0.png

Expressions are like facts that exist on the platform. For instance, each Business Hour and Calendar has its own expression (open the drop down list to find out which exist). If you have one Business Hour for your New York City and another for your Amsterdam office, you might find the following two expressions in the list:

    • Business Hours [Office Hours - US/NYC]
    • Business Hours [Office Hours - EU/Amsterdam]

So the moment you create a new Business Hour, a new expression will show up.

This also applies to new calendars, queues, variables and IVR inputs.

Moreover, you have a number of pre-defined expressions, mainly concerning calls and agents.

 

To define a trigger, you must create some logical condition with the help of Operators. So for instance, you want calls that reach your platform after hour to got to an after hour prompt. Therefore, you need to check whether Business Hours are not applying. As you will see in the example below, you can select the operator "is no given" to define this condition. Alternatively, you could use "is equal to false" or "is not equal to true". There are many ways of achieving and testing this condition.

This is the list of all currently available logical Operators:

      • is equal to
      • is not equal to
      • is great than
      • is great than or equal to
      • is less than
      • is less than or equal to
      • matches
      • is similar to
      • is given
      • is not given
      • starts with
      • ends with
      • contains
      • does not contain

 

Setting up the three triggers for the call-flow

The first trigger we already discussed extensively in this tutorial: it checks whether Business Hours do not apply (please make sure you select the correct Business Hours).

 

 

 

mceclip0.png

 

The second trigger is looking at holidays. Here you also need to make sure the correct calendar is selected.

 

 

 

 


The third trigger is checking if agents are enabled. Enabled means that at least one agent is online. However, this does not mean an agent is ready to take a call. This one agent might be busy in a call.

 

 

The fourth trigger checks how long a call has been waiting in a queue. If it waits more than 300 seconds, the trigger is true.

 

In the next section, you will learn how these conditions that triggers create can be used to define a call's path.

Have more questions? Submit a request