Returns a simple card to allow Partners to provide the tribu team with feedback for Tribu. Typically used to report issues, feature requests or modifications. These are then stored in the Tribu feedback table which feeds directly into our development sprint discussions Command: /addfeedback

Returns the start and end times for the user who issues the command. This allows a user of Tribu to view their set work hours. The work hours are used when using the Automated scheduling feature of Tribu. Note: By default, Tribu will always deem the standard work week to be Monday to Friday and now work can be automatically scheduled on a Saturday or Sunday

This will remove the ‘Away’ status from the user matching the email specified in the command. The Away status silences @mentions from Tribu to that user while they are away and divert those @mentions to an alternative person to notify. This Away status is a Tribu only status and does not correlate to any integrated system currently.

Returns a simple card to allow partners to specify a person who is away and to divert any Tribu notification messages to an alternative person. This also allows the selection of a date and time to remove this away status automatically. The away status silences @mentions from Tribu to that user.

This will set the Manager notification to the user matching the specified email. Manager notifications are for Ticket Idle and SLA Overdue notifications. Multiple users can be assigned as a Manager. All Managers will be @mentioned for any Ticket Idle or SLA Overdue notification as well as the assigned resource.

This will set the work hours for the user issuing the command. This specifies the earliest time Tribu can schedule a service call for the user and the latest time it can schedule a service call when using the Schedule Automatically option in ticket notification schedules. Note: By default, Tribu will always deem the standard work week to be Monday to Friday and now work can be automatically scheduled on a Saturday or Sunday

This will set the user matching the email specified as a First Responder. First Responders will receive @mentions for New Ticket notifications from Talos. Multiple email addresses can be specified for multiple users to receive @mentions, separated by a space.

This will remove the First Responder status from the user matching the email specified. This will stop @mentions being sent to the user for New Ticket notifications. Multiple email addresses can be specified for multiple users, separated by a space.

Returns a list of users with the status of Away. The Away status silences @mentions from Tribu to that user while they are away and divert those @mentions to an alternative person to notify.

Returns a list of tickets, their status and ticket title for the user issuing the command. Each ticket specified has a hyperlink to the ticket URL for quick reference opening. Optionally, if an email address is specified the command will return the list of tickets for the user with the matching email address in the same format.

Returns multiple dialogs. If the company name specified has multiple matches, a simple dropdown selection is presented for the user to select the correct company to create the new ticket for. With the correct company identified, the dialog then returns all current open tickets for that company to help prevent duplicate tickets being created. The next dialog then returns a detailed card with fields to create a new support ticket. Ticket Title is the only mandatory requirement for Tribu, though your business processes may require other fields. These are not currently enforced by Tribu. Optionally, if an email address is specified the command will return the list of tickets for the user with the matching email address in the same format.

Returns a simple card allowing the user issuing the command to select from any tickets they are assigned to as Primary Resource or Secondary Resource (if selected in Tribu preferences). An option to have the note email to the ticket contact is available and signals to the corresponding Autotask workflow to send the contents of the note out via an Autotask Notification template.

Returns a simple card allowing the user issuing the command to select from any tickets they are assigned to as Primary Resource or Secondary Resource (if selected in Tribu preferences). Time’s can be manually typed or select from the dropdown in the 30 minute increments. Note that a date selection is NOT available and will always be entered on the day the card is submitted. The /TimeEntry command is intended to encourage time entries to happen as the work is being completed or immediately after.

Returns a card to select the Ticket and to give a title to the attachment as required by the PSA. Note that you must attach a file to the dialog with the /addattachment command using the paperclip symbol. The tickets presented to the user will only include those where they assigned as the Primary Resource or Secondary Resources.

Initialises Tribu into a Microsoft Teams Chat channel.

Use /diagnose command to test the various permissions and setup of your PSA integration with Tribu. The result will assist with any setup issues you might face.