Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
description
description

...

  • For Stakeholders:  There is an assurance that nothing is missed out and all tickets that are scheduled to be worked on will be catered by the assigned technician in a given time-frame.
  • For Managers and Supervisors: This will save them the time to check with the technicians if they are aware that a ticket was assigned to them and they will be working on it within the schedule set. This has a positive impact towards the utilization rate of their technicians.
  • For Agents and Technicians:  This bot will send out helpful reminders so that they are alerted if they miss to acknowledge scheduled tickets that they need to work on which will improve their chargeability and value to the company.

Anchor
requirement
requirement

...

REQUIREMENTS

  • Active ConnectWise Manage Integration 

Image Added

  • Active Microsoft Teams Integration

Image Added

Image Added

  • Message Switch is set to Enabled on the MSPbots User Management Page

Image Added

  • (OPTIONAL) The user's manager is configured within Azure Active Directory

Anchor
configuration
configuration

...

BOT CONFIGURATION

Here are the steps to configure the bot.

1. Open the bot by expanding the left navigation and clicking Bots.


Image Added


2. Using the search bar, search for the bot CW Scheduled Ticket Acknowledgement Alert 3.0. Click on the bot name to edit.


Image Added


3. This should open the Trigger module, this is where you can define how long before the scheduled start date the bot should trigger. 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.


Image Added

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

Image Added

5. This should open the Alert module. This is where you can set the following:

  • Where to send the messages
  • Message recipients
  • Alert Message

Note: You can either send the message to the user or technician who triggered the bot by choosing email or the field containing the email address of the user or any specific user on your team.

Image Added

6. To edit the alert, simply use it as you would a text editor. The important feature here is the "Insert a token" Image Added button which would allow you to dynamically insert corresponding field values from ConnectWise Manage such as first name, ticket ID, etc.

Image Added

To illustrate further, this message:

Image Added


Would look like this:


Image Added

7. After setting up the medium or channel where you want to send the alerts to and customizing your alert message, click the Next button again.

8. This will open the final module that you need to configure - the Escalation module. This is where you can set your escalation cycle, escalation threshold, escalation steps, and escalation alert messages.

Image Added


9. The Time Frame is when the count of alerts and escalations would reset. For example, setting a Time Frame of "Week" would reset the accumulated count of alerts and escalations to zero every Monday.

10. The Define Escalation Steps is where you're going to set when to alert the user and the manager that the bot alert count has reached a threshold and the user and time entries need review.

For each escalation, you can set the following: 

  • 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 Added


  • 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 Added


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

Image Added

Anchor
practices
practices

...

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.

Image Added

  • Let your team know that you are enabling the bot and do a short 15 minutes coaching to let them know what the bot is about and how it will help your company accurately measure their profitability.

Anchor
source
source

...

DATA SOURCES

Source Widget: CW Scheduled Ticket Acknowledgement Alert 3.0

The CW Scheduled Ticket Acknowledgement Alert 3.0 uses the following data from ConnectWise Manage: 

  • Tickets
  • Schedule
  • Users

Anchor
description
description

...

BOT DESCRIPTION:

Reminds users to acknowledge scheduled tickets and check respective calendars.


Anchor
integration
integration

...

RELATED INTEGRATION:

Anchor
care
care

...

WHY SHOULD YOU CARE?

Sometimes, technicians fail to acknowledge a scheduled ticket that was assigned to them.

  • For Stakeholders:  There is an assurance that nothing is missed out and all tickets that are scheduled to be worked on are going to be catered by the assigned technician in a given time-frame.
  • For Managers and Supervisors: This will save them the time to check with the technicians if they are aware that a ticket was assigned to them and they will be working on it within the schedule set. This has a positive impact towards the utilization rate of their technicians.
  • For Agents and Technicians:  This will send out helpful reminders so that they are alerted  if they miss to acknowledge scheduled tickets that they need to work on which will improve their chargeability and value to the company.

Anchor
requirement
requirement

...

REQUIREMENTS

  • Active ConnectWise Manage Integration 

...

Anchor
configuration
configuration

...

BOT CONFIGURATION

Here are the steps to configure the bot.

...

8. This will open the final module that you need to configure - the Escalation module. 

The escalation process happens by sending an alert to the manager or designated supervisor when the technician fails to acknowledge a scheduled ticket multiple times within a defined time frame. This is where you can set your escalation cycle, escalation threshold, escalation steps, and escalation alert messages.


9. The Time Frame is when the count of alerts and escalations would reset. For example, setting a Time Frame of "Week" would reset the accumulated count of alerts and escalations to zero every Monday.

...

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

Anchor
practices
practices

...

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.

...

  • Let your team know that you are enabling the bot and do a short 15 minutes coaching to let them know what the bot is about and how it will help your company accurately measure their profitability.

Anchor
source
source

...

DATA SOURCES

Source Widget: CW Scheduled Ticket Acknowledgement Alert 3.0

The CW Scheduled Ticket Acknowledgement Alert 3.0 uses the following data from ConnectWise Manage: 

  • Tickets
  • Schedule
  • Users

---------

EDITS:

I think there are 2 groups of KBs here with the updated content as the 2nd group. Please retain the updated one. Thanks