Page History

...

3. This should open the Trigger module, where you can define the time frame (e.g. minutes, hours, etc.) that the bot will need to check if there was a new time entry entered. Additionally, this is where you can exclude users from the alert or add additional conditions/filters before triggering the bot. Under Schedule, you can set the timing and frequency of the bot alert.

4. Once done setting up your filters, click the next button to customize the bot alert message.

...

• Escalation Threshold - this is the number of times the bot is triggered before it escalates. For example, setting an Escalation Threshold of 3 means that the manager and/or user will be alerted that they have met the threshold ON the 3rd time the bot was triggered.

Image Modified

• Escalation Step - this is where you add the "levels" of escalation
• Message - this is the alert message that would be sent to either the user or manager when they meet the escalation threshold. The editor and tokens work the same as the bot alert message.

Note(s):

- The escalation to a manager and manager's manager will only work if both of them are on the Microsoft Azure Active Directory account.

- There are tokens that are specific only to the escalation alert

- BOT_NAME - the name of the bot that triggered the alert

- ESCALATION_TIME -  the number of times the bot has already been triggered

- MANAGER_NAME - the name of the user's manager

- USER_NAME - the name of the user that triggered the bot

- MANAGER_UP_NAME - the name of the manager's manager

Image Modified

11. After setting up the Escalation Steps, click Finish on the Escalation module and click Save on the Bot Design page.

Image Modified

...

BEST PRACTICES

• Don't turn on the alert yet after configuring your bot, simply enable Trigger. This will allow you to review the messages and data first before rolling it out to your team.

...