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 4 Next »

Background Information


  • Message Command is a trigger-type bot block that primarily recognizes the commands you send to MSPbots on Teams or Slack.
  • For example, by setting Message Command block to in and appending the Attendance-in and Alert blocks, MSPbots can identify the in command you input, automatically store your check-in record in the database, and respond accordingly.

Main Section


  1. Log in to the MSPbots app using your Office 365 account. 
  2. Navigate to Bots on the left menu then click the New Bot button on the Bots screen.

    You can also start creating a bot from a widget on your dashboard. Click the ellipsis button and select 
    Create Bot.
    create bot-widget
  3. When the Create a new bot window appears, click on Start From Blank > Message Command.
  4. Fill in the required fields for creating a bot. 
    1. Enter a name in the Bot Name field.
    2. Identify the Role that will have access to the bot.
    3. Add a clear Description of the bot. (Recommended)
    4. Then click the Continute button to open the tab with the details and settings for your new bot.
  5. Click Design to enter the Message Command pop-up window.

    Using the in command as an example, please refer to the other types of message command bots at: How to Configure the Message Command Bot Block.


    • Message Tool - If you want to trigger the bot by sending commands in Teams, please select teams. And if you want to use Slack, please select slack.

    • Command - Select the command you want MSPbots to recognize, or enter a custom command. For example, if you want to trigger the attendance bot using the check-in command instead of the in command, you can enter check-in here.
  6. Click Finish button.
  7. Click on the Message Command block, then click on the  under the block, and finally select Add a Block.
  8. Click on the generated blank block, and enter Attendance-in into the search bar, and then click on Attendance-in to add the block.
  9. Click on the Attendance-in block, then click on the  under the block, and finally select Add a Block.
  10. Click on the generated blank block and enter Alert into the search bar, and then click on Alert to add the block.
  11. Click the in the upper-right corner of the Message Command block, and then click Edit to make your settings.
  12. Click Next to configure the Attendance-in block.
  13. Please customize MSPbots' responses for each of the following scenarios in the Attendance-in pop-up window.
    • Clock in - Success
    • Clock in time is outside working hours -or- Clock in time is incorrect
    • Clock in update - Success
    • Wrong command
    • Clock in is done by an invalid account
  14. Click Next to proceed to the Alert configuration page. Follow the prompts on the page to configure the Alert block according to your preferences.

  15. Click Finish.
  16. Click Save in the upper right corner to save your settings.
  17. As shown in the figure below, when "in" is entered in MSPbots, it will be recognized and responded with the corresponding answer.

    Message Command Bot Types


    OrderMessage CommandCorresponding BlockNeed for Alert BlockMessage Command Bot Description
    1hiCommand-HelpYesBot that recognizes "hi" command to return answers related to help information.
    2helloCommand-HelpYesBot that recognizes "hello" command to return answers related to help information.
    3inAttendance-inYesBot that recognizes "in" command for attendance check-in.
    4

    out

    Attendance-outYesBot that recognizes "out" command for attendance get off work.
    5breakAttendance-breakYesBot that recognizes "break" command for attendance interrupt work.
    6lunchAttendance-lunchYesBot that recognizes "lunch" command for attendance  lunchtime.
    7onsiteAttendance-onsiteYesBot that recognizes "onsite" command for attendance check-in.
    8backAttendance-backYesBot that recognizes "back" command for attendance back to work.
    9ptoAttendance-ptoYesBot that recognizes "pto" command to handle related leave operations.
    10wfhAttendance-wfhYesBot that recognizes "wfh" command for attendance check-in.
    11statsUtilization-statsYesBot that reports the total working hours, utilization rate, overlapping time entries, ongoing work orders, and pending tasks to the user before the end of each workday.
    12ntNT command message formattingNoWhen entering the "nt" command, the bot returns data in a custom format.
    13rejectTeams Command-rejectNoBot that recognizes "reject" command to skip the current ticket, which needs to be used in conjunction with the "nt"command.

    14

    qa QA check activities
    QA check agreements
    QA check boards
    QA check campaigns
    QA check companies
    QA check contacts
    QA check invoices
    QA check orders
    QA check projects
    QA check purchaseOrders
    QA check reportsActivity
    QA check reportsAgreementInvoice
    QA check reportsAgreementList
    QA check reportsAgrType
    QA check reportsInvoiceProduct
    QA check reportsInvoices
    QA check reportsOpportunity
    QA check reportsProduct
    QA check reportsSchedule
    QA check reportsService
    QA check reportsServiceSla
    QA check reportsTime
    QA check schedules
    QA check sheets
    QA check tickets
    QA check timeEntries
    Yes

    These bots are used by QA personnel to check various business scenarios.

    15nttest-YesJust for testing, please do not use.
    16helpCommand-helpYesBot that recognizes "help" command to return answers related to help information.
    17unknownTeams Command-ChatGPTYesBot that returns answers from chatGPT. Please connect to the OpenAI integration before using this bot.
  • No labels