Microsoft Teams app
Add the Watari app to a Teams team, connect it to your workspace, choose the channel, and act on issue cards without leaving Teams. Covers who can press what, disconnecting, and the Teams workflow option that works today.
The Watari app for Microsoft Teams posts one card per issue in a channel your team already reads, keeps that card up to date as the issue moves, and lets your team act on it from Teams: answer Watari's question, start a draft fix, add detail and try again, or send the customer update.
The Watari app for Teams is rolling out. It will be added from the Teams Store once Microsoft has approved the listing. Until then, connect Teams with a Teams workflow, which works today and needs no app at all: see Use a Teams workflow instead.
Everything here is bundled. Cards and buttons never add to your Mapped Issue count.
Get help
The Watari app for Teams is made and supported by Watari AI. Email support@watari.ai with any question about the app, connecting a team, or your account. Using it needs an active Watari account: sign up for Watari, or email us for details.
To help us answer in one reply, include:
- the name of your Watari workspace and of the Teams team;
- what you pressed or expected, and what happened instead;
- the issue title, or a screenshot, if it is about one issue.
What it does for your team
- One card per issue, kept up to date. Watari posts a card when an issue arrives and changes that same card as the issue moves, so the channel reads one card per issue, not a stream of updates.
- Your team hears when it is your move. Each change is also said as a reply under the card. A reply brings the card back to the bottom of the channel and tells the people following it, so a step like "Your move · Update the customer" reaches you even when the card was posted days ago. Steps Watari takes on its own stay quiet.
- The step is done where you read it. Buttons on the card open a short form in Teams, shown only to the person who pressed.
Add Watari to a team and connect it
Connecting always starts in Teams. Only someone in the team can show that the team is theirs, so there is no way to start from Watari.
Add Watari to your team. In Teams, open Apps, search for Watari, and add it to the team you want cards in. Watari posts a welcome message in the team's General channel.
Press Connect to Watari. The person who added Watari to the team presses Connect to Watari in the welcome message. Teams shows that person, and nobody else, a link that works once, for 15 minutes. If the link stops working, press Get a new link on the same message, then Open Watari.
Choose the workspace. The link opens Watari. Sign in if you are not already, then pick the Watari workspace this team should belong to. You must be an owner or admin of that workspace.
Sign in with Microsoft. Sign in with the same Microsoft work account you pressed Connect with. Watari takes you to Settings → Connected tools, where the Microsoft Teams app card shows your team.
Choose the channel. On the Microsoft Teams app card, press Choose channel, pick the channel for Watari cards in the dialog and press Save. Nothing is posted until a channel is chosen. Press Configure, then Send test, to see a card arrive. A private or shared channel needs one more step first, below.
When the team is connected, every owner and admin of the workspace is told, in Watari and by email, and Watari posts one line in the team's General channel saying which workspace it is connected to and who connected it.
Only the person who added Watari to the team can connect it. Anyone in a Teams team, guests included, can see the welcome message, so Watari gives the link to the person who added the app and refuses anyone else. If that person is not available, remove Watari from the team, add it again, and press Connect to Watari in the new welcome message.
If your organization has to allow Watari first
Some organizations do not let people sign in to new apps with their Microsoft work account. Then Sign in with Microsoft stops and Watari says your organization has to allow Watari first. A Microsoft administrator of your organization approves Watari once, and after that everyone signs in normally. Watari asks only for your name and your account's identity, nothing in your mail, files or chats.
One team per workspace
A workspace posts to one Teams team, and a Teams team belongs to one workspace. To move cards to another team, disconnect the current one first, then press Connect to Watari in the other team.
To move cards to another channel of the same team, an owner or admin presses Configure on the Microsoft Teams app card and chooses another.
Private and shared channels
Watari posts in standard, private and shared channels. For a private or shared channel, add Watari to the channel first, because Teams does not let an app post there until it is added to that channel:
- In Teams, open the channel's menu and choose Manage channel.
- Open Apps and add Watari.
- Back in Watari, press Send test in the dialog.
Until then Watari says it can't post to that channel, and the Microsoft Teams app card says the same with these steps.
What a card shows
Each card says:
- Whose move it is and the next step, on the first line: "Your move · Review the fix", "Your move · Watari asks", "Watari's move · Looking for the cause".
- The issue, linked to its page in Watari, with one sentence on where it stands.
- Who reported it and where, the severity, and how many customers have reported it.
- A short quote: the customer's own words, or Watari's question when it is waiting on your team.
- The button for the next step, and Open in Watari beside it.
When the issue is done, the card shrinks to one line and its buttons go away.
Act from the card
Buttons on Teams cards are rolling out with the app. Each one opens a short form in Teams that only you see:
| Button | When it shows | What it does | Who can press it |
|---|---|---|---|
| Answer | Watari asked your team a question | Pick one of Watari's choices or type your answer. Watari tries again with it. | Any member |
| Draft a fix | Watari found where it happens but was not sure the report is a bug, so it waited for you | Starts the draft at once, the same as the button on the issue page. Nothing to fill in. | Any member |
| Add detail and retry | Watari stopped, or a draft was closed as wrong | Tell Watari where to look or what was wrong. It tries again with what you said. | Any member |
| Send, Edit and send, Skip | The fix is live and the customer update is waiting on you | Send shows the whole update and where it goes. Edit lets you change it first (25 to 120 words). Skip asks why, if you want to say, and closes the issue. | Any member |
| It is live | The fix is merged and Watari is waiting to hear it reached production | Confirms the fix is live, so Watari moves on to the customer update. | Owners and admins |
| Fix was wrong | A draft fix is ready for review | Asks what was wrong and records it. The draft stays open where your code lives. | Any member |
Actions you need less often, Skip and Fix was wrong, sit in the card's ... menu.
Each button acts on the step its card showed. If the issue has moved on since, Teams tells you it is already handled and the card catches up. After you act, the card changes for everyone in the channel and says what happened.
Watari checks your role in the workspace when you press, the same way it does in Watari. The roles are described in Settings → Team.
Link your Microsoft account the first time
The first time you press a button, Watari does not yet know which Watari member you are, so the form gives you a one-time link instead:
- Open the link. It works once, for 15 minutes.
- Sign in to Watari as yourself. You must be a member of the workspace the team is connected to.
- Press Sign in with Microsoft and sign in with the Microsoft work account you pressed the button with.
- The page says your Teams account is linked. Press Go back to Teams and press the button again.
Both sign-ins must be your own, so a link forwarded to someone else links nothing. From then on, buttons in that team act as you.
Ask Watari in Teams
Mention Watari in the team with help to see where this team stands and what the buttons do. Watari answers hi, hello and help, and never repeats what you wrote.
Disconnect
Only an owner or admin of the connected workspace can disconnect. On the Microsoft Teams app card in Settings → Connected tools, press Configure, then Disconnect. Watari stops posting, forgets the channel and every linked Microsoft account for that workspace, and tells every owner and admin, in Watari and by email.
Disconnecting does not remove the app from your team. To remove it, remove Watari from the team in Teams. Removing the app in Teams also disconnects the team, and whoever adds it again connects it again from a new welcome message.
Use a Teams workflow instead
If the app is not available to you yet, connect Teams with a workflow you build in a channel from Microsoft's own template, then paste its address into Settings → Connected tools. It needs no app and nothing for a Teams administrator to approve. The steps are on Routing and notifications, under the Microsoft Teams tab.
A workflow posts the same cards with links instead of buttons, and it cannot change a card it already posted, so it posts a new card when an issue becomes your move. When the Watari app is connected and has a channel, cards come from the app only, so your team reads one card per issue. The Microsoft Teams card in Settings → Connected tools then reads Not in use, because nothing is sent through the workflow; you can disconnect it from its Configure dialog.
Limits
- One channel. Watari posts in one channel you choose, in one team. It can be a standard, private or shared channel; add Watari to a private or shared one first.
- One team per workspace, and one workspace per team.
Routing and notifications: Slack, Microsoft Teams, Linear, Jira
Configure where Watari posts updates, where issues are filed, and how Watari picks up issues your team hands it in Jira or Linear. Includes the Slack channel-invite step and the Microsoft Teams workflow setup.
Webhooks and events
Which provider events Watari subscribes to, how retries and signed payloads work, and what happens when a delivery fails.