Skip to main content
With the Traversal Teams bot, you can start investigations, receive reports, and ask follow-up questions without leaving Microsoft Teams. Mention @Traversal in any channel, in a group chat, or in a direct chat with the app. With Traversal in Teams, engineers can:
  • Start investigations from any channel, group chat, or direct chat, either by mentioning @Traversal manually or through configured auto-triggers.
  • Receive investigation reports in the thread where the investigation was started.
  • Ask follow-up questions in natural language to refine the analysis.
  • Work alongside Incident and Alert Workers that maintain channel context and act proactively.

Watch the demo

See Traversal investigating an incident from Teams.

Install the Teams app

Get the Traversal app into your Microsoft Teams workspace.

​
Starting an investigation

Mention @Traversal with a description of what you’re seeing. Include any context that helps, such as symptoms, affected services, and a timeframe.
Traversal runs the investigation against your connected observability tools and posts the report back into the same thread.

​
Triggers

Triggers let Traversal automatically start investigations when certain conditions are met. There are two types.

​
Message triggers

Message triggers fire when a message in a configured channel matches certain conditions, for example a keyword match or a message from a specific user. Use @Traversal register-trigger to create one. You’ll provide:
  • The channel to monitor
  • Conditions such as keyword matches or sender filters
  • The type of context Traversal should pull into the investigation

​
Channel join triggers

Channel join triggers fire when Traversal is added to a channel that matches a pattern you define. The pattern can match against the channel name or description. For example, it can match channels whose name starts with inci-. If the condition is met when Traversal is added to a channel, Traversal automatically runs an investigation. You can also specify the context source Traversal pulls into the investigation:
  • Channel description
  • Message content
  • Message thread content

​
Managing triggers

Use @Traversal register-trigger to set up a new trigger. A pop-up opens so you can configure it. Use @Traversal show-triggers to view and delete triggers across your organization. Use @Traversal show-channel-triggers to see only the triggers configured for the current channel.

​
Traversal Workers

Traversal can also work in a channel continuously as a Worker, following what happens and deciding when to act without waiting for an @Traversal mention.
  • Incident Workers own live incident response from initial investigation through verified recovery and the post-mortem.
  • Alert Workers continuously triage alerts, reuse relevant prior work, and identify the signals that need action.
Deploy Workers by scanning your workspace, picking a channel, or setting an auto-deploy rule. Each Worker comes with a scratchpad, private chat, schedules, and custom instructions, and the Workers console shows all your Workers in one view. You can also start and stop a Worker without leaving Teams. The rules that apply on both platforms are in Start and stop a Worker from chat.

​
Start a Worker

Mention @Traversal worker-start in the channel, group chat, or meeting chat you want the Worker in.
Teams can’t open a form straight from a typed command, so Traversal sends you a private card. Only you see it, and it may arrive in your direct chat with Traversal rather than in the channel.
1

Open the form

Click Open Worker form on the card.
2

Choose a Worker type

Pick Incident, Alerts, or Custom. Incident is the default.
3

Add custom instructions

Optional for Incident and Alerts, required for Custom.
4

Start the Worker

Click Start Worker. The form closes with a confirmation only you see, and the Worker posts its usual arrival message in the conversation, noting that it was deployed with a Teams command.
If a field is invalid, the form closes and tells you why. Teams can’t redisplay the form with your entries, so run @Traversal worker-start again to reopen it. If the conversation already has a Worker, Traversal tells you its type instead of sending the card. For a private channel, add @Traversal first.

​
Stop a Worker

Mention @Traversal worker-stop in the conversation.
The Worker signs off and names who stopped it. If the conversation has no running Worker, Traversal tells you so privately.

​
Investigation output

When Traversal completes an investigation, it renders the report directly in Teams. The report includes:
  • Citations, with links to the observability sources referenced in the investigation.
  • Any visuals Traversal drew, posted as images.
  • A link to open the investigation in the Traversal UI for more detail.

​
Follow-ups

Mention @Traversal in the same thread as an investigation report to ask follow-up questions or trigger additional analysis.

​
Group chats and direct chats

Traversal also works outside channels. Add the Traversal app to a group chat, or open a direct chat with it, and mention @Traversal to start an investigation. You don’t need to be in a specific channel.

​
Permissions

Traversal follows the principle of least privilege. The bot runs as a registered Microsoft app that a Teams administrator uploads to your org catalog. It uses two kinds of Microsoft Graph permissions:
  • Resource-specific consent (RSC) permissions apply only to the team, group chat, or meeting Traversal is added to, and are granted by whoever adds it there. They cover @Traversal investigations, triggers, and Workers in those conversations.
  • Application permissions are tenant-wide and optional. An administrator grants them once to unlock org-wide features such as auto-joining new meetings and reading channels Traversal isn’t in.
For the full permission list, what works with RSC only, and how it’s handled, see Microsoft Teams data privacy and security.

​
Security and data handling

  • Data usage. Teams data is used only to deliver the features described on this page. We do not use Teams data to train LLMs.
  • Scoped engagement. Your organization decides where Traversal participates. It acts only on mentions, configured triggers, or Workers your team has enabled.
  • Transport and storage. All traffic is encrypted in transit, credentials are stored securely, and inbound requests are validated against Microsoft-signed tokens.
  • Least privilege. Traversal requests only the minimum permissions needed for the functionality described here.
  • Retention. See the privacy policy for retention and deletion practices.
Traversal uses generative AI and may produce inaccurate or incomplete outputs. Validate recommendations before acting.

​
FAQ

If Traversal replies with a prompt to connect your workspace, an admin needs to click Connect to Traversal to pair it with your organization. If there’s no response at all, the app may not be installed correctly. See the installation guide or reach out to a Traversal team member.
Run @Traversal show-channel-triggers to confirm the trigger is enabled in the intended channel. Trigger conditions are case-sensitive, so the message content must match your configured conditions exactly.

​
Support

Questions or issues? Email support@traversal.com.