Watari for Slack
Every customer issue, one card, in the channel your team already reads.
A customer reports a problem, and someone has to confirm it is real, find the code behind it, get a fix reviewed, and remember to tell the customer. Watari runs that loop. In Slack, each issue is one card that says whose move it is, changes as the issue moves, and lets your team take the next step without leaving the channel. Watari never reads your Slack messages.
Watari is installed from your Watari account: sign up free, then Settings → Connected tools → Slack. Already a customer? Connect Slack now. The steps are below. By installing you agree to our privacy policy and terms.
- Trial
- 14 days of Growth · 3 repositories · 10 Mapped Issues
- Reads messages
- Never
- Setup
- OAuth · 2 minutes
- Slack add-on cost
- None: bundled
What is Watari for Slack?
Watari for Slack gives every customer-reported issue one card in a channel you choose. The card leads with whose move it is, Watari edits it as the issue moves and says each change in its thread, and its buttons let your team answer Watari, draft a fix, review the pull request and send the customer update. It never reads Slack messages.
Why support and engineering teams connect Watari to Slack
One card per issue, kept up to date
Every customer-reported issue gets one card in the channel you pick. The card leads with whose move it is, "Your move · Review the fix" or "Watari’s move · Drafting a fix", and Watari edits that same card as the issue moves, so the channel never fills up with a message per step.
Every change said in the thread
Each change is also said in the card’s thread, so the history of the issue sits under its card. When a step needs your team, that reply is posted to the channel too, so it does not sit unseen higher up.
Act from the card
When it is your move, the card carries the button for it: Answer Watari’s question, Draft a fix, Add detail and retry, Review PR to open the draft pull request, then Send, Edit and send, or Skip the customer update Watari wrote. It is live and Fix was wrong are there too. Watari never merges anything.
Acts as the person who pressed
Each button acts as that person’s Watari account and checks their role there, the same way the issue page does. The first time someone presses, Watari matches them by the confirmed email on their Slack profile. If they sign in to Watari with a different address, they confirm their Slack account once with Sign in with Slack.
Never reads your Slack messages
Watari asks for no permission that can read message history, search messages or open files, and it posts only to the channel you pick. The only text it receives from Slack is what someone types into a Watari form opened from a card.
Tells you when the channel breaks
If the channel is archived or the bot is removed, the Slack card in Settings → Connected tools says so in plain words, and posting resumes once the channel is back. Check channel and Send test notification confirm it.
How to install Watari in your Slack workspace
Create your Watari account
Sign up at watari.ai/signup, or sign in at watari.ai/login if you already have an account. The 14-day free trial of Growth includes up to 3 repositories and 10 Mapped Issues and needs no credit card. Connect where customer reports arrive (a help desk or an issue tracker) and your GitHub or Azure DevOps code.
Click Connect on the Slack card
In Watari, open Settings → Connected tools and click Connect on the Slack card. Slack’s consent screen lists the seven bot permissions Watari asks for. None of them can read messages.
Click Allow
Choose your Slack workspace and click Allow. Slack sends you back to Settings → Connected tools in Watari, with the Slack card marked Connected.
Pick the channel
Click Configure on the Slack card and choose a channel. Watari joins a public channel on its own. For a private channel, type /invite @Watari in that channel first, and it then appears in the list. Save.
Send a test
In the same dialog, click Send test notification. A test message reaches the channel within seconds. From the next issue on, each one gets its own card there.
After you install
A successful install sends you back to Settings → Connected tools in Watari, where the Slack card reads Connected. From there:
- Pick a channel. Click Configure on the Slack card. Public channels are listed and Watari joins the one you pick. For a private channel, type /invite @Watari in it first.
- Send a test. Send test notification posts a message to the channel within seconds, so you know it works before the first issue arrives.
- Watch the first card land. The next customer-reported issue gets its own card. It starts as Watari’s move while Watari finds the code, and the same card changes as the issue moves.
- Press its button when it is your move. The first time, Watari matches you by your Slack email, or asks you once to confirm your Slack account with Sign in with Slack.
- Disconnect any time. Disconnect Slack, inside Configure on the Slack card, erases the token and stops all posting at once.
Exactly what Watari can do in your workspace
Watari asks for seven bot permissions, and the consent screen you approve lists each one. None of them can read message history, search messages or open files, and none is an admin permission. The one user permission, openid, is asked only when a person links their Slack account with Sign in with Slack, and tells Watari only which Slack user and workspace signed in.
- Post and edit cards
chat:write+chat:write.public, post each issue’s card to the channel you chose, edit it as the issue moves, and reply in its thread. The second keeps cards reaching that public channel if the bot is removed from it.- List channels
channels:read+groups:read, fill the channel picker with public channels and the private channels the bot was invited to, and notice when the chosen channel is archived. Channel names and IDs only, never message content.- Join
channels:join, join the one public channel you pick, so there is no manual /invite step.- Know who pressed
users:read+users:read.email, look up only the person who pressed a button on a card, so the button acts as their Watari account with their role. Watari never lists your workspace’s members.- Store
- The bot token (AES-256-GCM encrypted before it is saved), your Slack workspace ID and name, the channel you chose, the IDs of the cards Watari posted, and for a person who linked their account, their Slack user ID. Each workspace’s data is isolated with Postgres row-level security. No Slack message content is stored: none is ever read.
Pricing
The Slack app is bundled with every plan, never metered. You only pay when Watari delivers a Mapped Issue: a bug, or a code-actionable feature request, paired with the file and function Watari ranks as the most likely cause. Draft fixes, customer updates, and Jira / GitHub Issues sync are bundled the same way.
Starter
$400/mo
20 Mapped Issues included · $25/bug on-demand
For small support teams routing their first Mapped Issues.
Growth
$900/mo
60 Mapped Issues included · $20/bug on-demand
For teams running customer support at production volume.
Scale
$1,800/mo
150 Mapped Issues included · $15/bug on-demand
For multi-repo SaaS with a dedicated support function.
Indian buyers (with GSTIN) are billed in INR; everyone else in USD.14-day free trial of Growth · up to 3 repositories · 10 Mapped Issues included · no credit cardrequired. Annual billing saves 17%. Full plan comparison at watari.ai/pricing.
Security & privacy
- No permission that can read messages, search or files.
- Every button checks the presser’s Watari role.
- Every click is checked against Slack’s signature.
- Bot token AES-256-GCM encrypted at rest.
- Postgres row-level security on every tenant-scoped table.
- Your tickets and code never train any model.
- Full security posture at watari.ai/security · privacy details at watari.ai/legal/privacy.
Frequently asked questions
Does Watari read my Slack messages?
No. Watari asks for seven bot permissions: chat:write and chat:write.public to post and edit its cards, channels:read, groups:read and channels:join for the channel picker, and users:read and users:read.email to learn who pressed a button on a card. None of them can read message history, search messages or open files. The only text Watari receives from Slack is what someone types into a Watari form opened from a card.
What does Watari post in Slack?
One card per customer-reported issue. It says whose move it is and the next step, names the issue with one sentence on where it stands, says who reported it, and carries the button for the next step. Watari edits the same card as the issue moves and says each change in its thread. A finished issue shrinks to one line.
Who can press the buttons on a card?
A member of your Watari workspace. Each press acts as that person’s Watari account and checks their role, so a button does exactly what that person could do on the issue page, no more. Watari matches the presser by the confirmed email on their Slack profile. If it does not match, only that person is told, with a one-time link to confirm their Slack account with Sign in with Slack.
Can Watari post to a private channel?
Yes. Type /invite @Watari in the private channel first, then pick it in Settings → Connected tools. Watari only sees private channels it has been invited to.
What happens after I click Allow on the Slack consent screen?
Slack sends you back to Settings → Connected tools in Watari. Click Configure on the Slack card, pick the channel, save, and click Send test notification to see a message arrive. If anything fails during the install, the same page says what went wrong and lets you try again.
Why does the consent screen say "App is not approved by Slack"?
Slack shows that banner on apps that are not yet listed in the Slack Marketplace. It does not change how the install works or what Watari can do. Watari’s Marketplace listing is under review.
Does the Slack app cost extra?
No. The Slack app is included in every plan and never metered. You pay only per Mapped Issue, an issue Watari maps to your code. Draft fixes, customer updates and tracker sync are included the same way.
How do I disconnect, and what Slack data does Watari keep?
In Settings → Connected tools, click Configure on the Slack card, then Disconnect Slack at the foot of the dialog. The token is erased at once and Watari stops posting. While connected, Watari keeps the encrypted bot token, your Slack workspace ID and name, the channel you chose, and the IDs of the cards it posted so it can edit them. When someone links their Slack account, it keeps their Slack user ID until they unlink it in Settings, Profile. Watari never stores Slack message content, because it never reads any.
When a support ticket reports a bug, your engineers get a drafted fix.
Connect your help desk or your issue tracker, then GitHub or Azure DevOps. Watari maps each bug to the exact file and function in your code and drafts the fix as a pull request your CI checks.
14 days free. No card. Cancel any time.