Skip to main content
WHAWIT posts incidents into a Microsoft Teams channel as they escalate. Each incident arrives as a card with buttons — Acknowledge, Snooze, Resolve, Assign — that act directly on the incident. Every action is attributed to the Teams user who clicked it and appears on the incident timeline in WHAWIT.
WHAWIT incident card in Microsoft Teams

An escalated incident in a Teams channel, with in-place actions

Requirements

  • A WHAWIT account. Channels are connected per project: incidents of the connected project post to the channel.
  • The WHAWIT app installed in your Teams tenant — from the Teams app store, or uploaded to your organization’s app catalog by a Teams administrator.
  • To use the card buttons, the Teams user’s email address must be a member of the WHAWIT organization. Channel membership alone is deliberately not enough — anyone can see the card, only your team can act on it.

Connect a channel

1

Add the WHAWIT app to the channel

In Teams, open Apps, find Whawit and add it to the team channel where incidents should land. On install, the bot introduces itself and posts a pairing code — eight characters, valid for 30 minutes.
WHAWIT pairing code message in Teams

The bot posts a pairing code when it joins a channel

2

Enter the code in WHAWIT

In app.whawit.ai, select the organization and project the channel belongs to, then open On Call → Meerkats, open your monitor’s row menu (⋮ → Edit), and scroll to the channels section — the Teams channels card. Enter the pairing code and press Connect. The same card is also available under Integrations → Microsoft Teams.
3

Done

The channel appears as connected, attributed to the user who linked it. From now on, incidents of that project post to the channel as they escalate.
Code expired, or lost the message? Mention the bot — @Whawit connect — in the channel. If the channel is not yet connected, it answers with a fresh pairing code.

The incident card

When an incident escalates, the card carries the severity, status, summary and description, plus: After an action the card refreshes in place, showing what happened and who did it — Acknowledged by [email protected] — and the same entry lands on the incident timeline. Once an incident reaches a terminal state, action buttons are removed from the card. Actions are single-use: a second click on an already-applied action answers “Already applied” instead of repeating it.

Talking to the bot

The bot answers any mention. @Whawit help (or anything else) replies with the channel’s connection status and where to manage your on-call setup. In a channel that is not connected yet, any mention gets a fresh pairing code.
WHAWIT bot replying to a help mention in Teams

The bot answers mentions with the channel status and next steps

Alternative: incoming webhook (no bot)

If you prefer not to install the app, WHAWIT can post through a Teams Workflows incoming webhook instead:
  1. In Teams, open the channel → WorkflowsPost to a channel when a webhook request is received, and copy the generated URL.
  2. In WHAWIT, open On Call → Meerkats → your monitor → ⋮ → Edit, scroll to the channels section and paste it into the Microsoft Teams webhook field.
With the webhook transport, card buttons open WHAWIT in the browser (signed, single-use links) instead of acting in place — the platform does not allow callbacks on webhook cards. The bot transport is the recommended experience.

Security and data

  • The bot stores only the conversation reference it needs to post to your channel, and reads the clicking user’s email address to attribute actions.
  • Authority over incidents comes from WHAWIT organization membership, never from channel membership.
  • Webhook action links are signed and single-use; links on old cards expire after 24 hours (the incident stays reachable through Open incident).

Troubleshooting