N O T I C E


MSPbots WIKI is moving to a new home at support.mspbots.ai to give you the best experience in browsing our Knowledge Base resources and addressing your concerns. Click here for more info!


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The micro-trained bots of MSPbots are known for providing value to businesses by taking action in real-time. It automates repetitive tasks and takes away inefficiencies by flagging action items from key reports and encouraging productive behavior in the organization. This article discusses the types of bots and how each can add value to your MSP.

What types of bots are available with the MSPbots app?

Use this guide to see how each type of bot can work for your MSP.

Bot TypeDescriptionExamples
Alert The Alert bot is one of the most commonly used bots of MSPbots. It sends automated alerts to inform users of action items or escalate to managers when expected actions are not taken or specified parameters are not met. The alert messages are sent in real-time so that users can take immediate action and get back on track ASAP.

Time Entry Bots, After Business Hours Verifier, Idle Time Verifier, Next Ticket Rejected Alert, Ticket Resolution Prompter, Ticket Not Updated, Priority Tickets Alert

Reminder Reminder bots send out regular alerts to clock in or out, start tasks, and complete entry descriptions, among others.

Clock In/Out Reminder, Task Prompter, Time Sheets Submission Reminder, Onsite Schedule Prompter Real-time

Time/UtilizationTime and Utilization bots send out timed notifications pertaining to a staff member's utilized time, schedule, and tasks worked. These give recipients snapshots of the tasks that technicians' worked on and if required, a comparison to the company's standard or benchmark utilization.

Tech Stats Reviewer, Attendance Auto Out, Last 5 Day's Work Hours Summary, Daily Statistics Per Resource, Tech Utilization, Team Statistics EOD

Ticket relatedTicket-related bots are created to manage tickets or tasks assignments, progress, and updates among other functions.

Ticket Resolution Prompter, Ticket Notifier, New Tickets for the last 7 days, Stale Ticket, Daily Ticket Statistics

Report 

These bots send status, updates, or a set of numbers that help in making decisions.

Last Week vs. This Week, Late Time Entry Team Monthly Leaderboard, Monthly Business Report, SMaRT Hours for Clients, Past 4 Months, Weekly Tickets Needing Attention

QAQA bots prompt users for any missing information or documentation helping technicians and managers to complete data forms.

Ticket Closure QA, Ticket QA, Categorization, Attached Agreement Mismatch Prompter, Ticket QA, No Ticket Owner

Financial These are bots whose function is to prompt users for any revenue, income, expense related triggers.

Revenue this Week, Expense Report Alert on the 15th day

Information/input requiredSimilar to QA bots, these are automated system triggers that require users to provide an input in order to add more information to tickets, tasks, or others.

Work Type Prompter, Scheduled Ticket Acknowledgement, Short Time Entry Verifier

Attendance Attendance bots generate alert and reminders pertaining to staff attendance.

Attendance Adjustment Pending for Approval, Weekly Attendance Summary

Frequently asked questions on bots

  1. How do the bots work? Once configured, bots need a platform to send the message, alerts, or reminders to technicians, managers, and others. We have MS Teams and email readily configured and we are working on other channels as w
  2. Is there a limit as to when the bots can run? There is no limit to the amount of messages or alerts our bots can send in a day. Once a trigger event has been hit, it will automatically send the messages out and a user can configure the schedule to suit.
  3. Do bots require a separate integration? Bots work with your normal PSA like Connectwise or Autotask, RMM such as Liongard,  CRM  such as Hubspot, or any other platform. We just need to connect via a secure API and we are good to create the bots! 
  4. Is there a bot to alert or send a message if the user or technician has not acted upon the original alert? Yes, besides copying managers and supervisors on the original alert, a bot can be configured to send an escalation message if not acted upon beyond a set amount of time,
  5. Once configured, can a bot be easily modified or turned on or off by a user? Bots are easily customizable and modifiable even if it has already run. A user just needs to change or switch it on or off.


  • No labels