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 rendered directly in the thread where the investigation was started
  • Ask follow-up questions in natural language to refine the analysis

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 — 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, channels whose name starts with inci-. If the condition is met when Traversal is added to a channel, we will automatically run 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 will surface to 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.

​
Proactive mode (Traversal Workers)

In incident channels, Traversal can go beyond one-shot investigations and stay resident for the whole incident as a Traversal Worker — investigating on its own, answering follow-ups in-thread, and drafting a post-mortem when the incident resolves. Workers are in beta and enabled per team.

​
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, bringing you directly to the relevant data in your primary observability tool
  • 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 — no 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 installs. The Microsoft Graph permissions below are granted by a tenant administrator at install time. For the full breakdown of what data the integration captures 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.

​
Support

Questions or issues? Email support@traversal.com.

​
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. Note that trigger conditions are case-sensitive — the message content must match your configured conditions exactly.