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!
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!
Background Information
- Teams Command is a trigger-type bot block that primarily recognizes the commands you send to MSPbots on Teams. For example, by setting Teams Command 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
- Log in to the MSPbots app using your Office 365 account.
- 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. - When the Create a new bot window appears, click on Start From Blank > Teams Command.
- Fill in the required fields for creating a bot.
- Enter a name in the Bot Name field.
- Identify the Role that will have access to the bot.
- Add a clear Description of the bot. (Recommended)
- Click More Edit to open the pop-up window and fill out the required fields.
- Then click the Save button. Clicking Save opens the tab with the details and settings for your new bot.
- Click Design to enter the Teams Command pop-up window, then select the command you want MSPbots to recognize. Using the in command as an example, please refer to the other types of teams command bots at: How to Configure the Teams Command Bot Block.
- Click Finish button.
- Click on the Teams Command block, then click on the under the block, and finally select Add a Block.
- Click on the generated blank block.
- Enter Attendance-in into the search bar, and then click on Attendance-in to add the block.
- Click on the Attendance-in block, then click on the under the block, and finally select Add a Block.
- Click on the generated blank block.
- Enter Alert into the search bar, and then click on Alert to add the block.
- Click the in the upper-right corner of the Attendance-in block, and then click Edit to make your settings.
- 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
- Click Next to proceed to the Alert configuration page. Follow the prompts on the page to configure the Alert block according to your preferences.
- Click Finish.
- Click Save in the upper right corner to save your settings.
- As shown in the figure below, when "in" is entered in MSPbots, it will be recognized and responded with the corresponding answer.
Teams Command Bot Types
Order Teams Command Corresponding Block Need for Alert Block Teams Command Bot Description 1 in Attendance-in Yes Bot that recognizes "in" command for attendance check-in. 2 out
Attendance-out Yes Bot that recognizes "out" command for attendance get off work. 3 break Attendance-break Yes Bot that recognizes "break" command for attendance interrupt work. 4 lunch Attendance-lunch Yes Bot that recognizes "lunch" command for attendance lunchtime. 5 back Attendance-back Yes Bot that recognizes "back" command for attendance back to work. 6 onsite Attendance-onsite Yes Bot that recognizes "onsite" command for attendance check-in. 7 wfh Attendance-wfh Yes Bot that recognizes "wfh" command for attendance check-in. 8 pto Attendance-pto Yes Bot that recognizes "pto" command to handle related leave operations. 9 hi Teams Command-help Yes Bot that recognizes "hi" command to return answers related to help information. 10 hello Teams Command-help Yes Bot that recognizes "hello" command to return answers related to help information. 11 help Teams Command-help Yes Bot that recognizes "help" command to return answers related to help information. 12 stats Utilization-stats Yes Bot 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. 13 reject Teams Command-reject No Bot that recognizes "reject" command to skip the current ticket, which needs to be used in conjunction with the "nt"command. 14 unknown Teams Command-ChatGPT Yes Bot that returns answers from chatGPT. Please connect to the OpenAI integration before using this bot. 15 nt NT command message formatting No When entering the "nt" command, the bot returns data in a custom format. 16 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 timeEntriesYes These bots are used by QA personnel to check various business scenarios.
17 nttest - Yes Just for testing, please do not use.
Overview
Content Tools