Notifications and digest
Choose which updates reach you by email and in Watari, what the daily digest says, and how the team chat channel recovers when it is archived.
Configure how and where Watari notifies you and your team when something needs your attention.
Notification preferences are per-user. Each teammate manages their own email and in-app toggles from Settings → Notifications. The team chat channel (Slack or Microsoft Teams) is one per workspace, chosen by an admin when it is connected.
Where Watari posts
Watari can notify you through three channels:
- Email: sent to your account email address. Each event type has its own toggle.
- In-app notifications: appear under Updates on Home in the Watari dashboard. Some event types have the in-app notification locked on (critical issues, usage warnings, billing actions), these can't be silenced because they require immediate attention.
- Team chat: one card per issue in the Slack or Microsoft Teams channel your admin picked, kept up to date as the issue moves. See Routing and notifications for what the card says and how to connect.
Every message says what happened in its first words and has one thing to do. In-app titles use the same words as the issue page, for example Review the fix: Login fails on Safari, Watari asks: Leads arrive without a phone number or Update the customer: Export times out. Emails have a short subject that states the fact, open with what to do, and carry one button to the issue.
Event types
Settings → Notifications lists each event with an email switch and an in-app switch, in three groups. A channel Watari does not send an event on is left empty. When an in-app switch is always on, the reason is written under its row.
When it is your move
| Event | In-app | Notes | |
|---|---|---|---|
| Watari asks | Switch | Switch | Watari stopped before a draft fix and needs one answer from your team, for example which screen or which account. The notification carries the question, and the email also says why Watari asks. Answer it on the issue; when the issue came from Jira, Linear, GitHub Issues or Azure Boards, the email also says you can reply on that item with Watari's handle, for example "Or reply on Jira SCRUM-40 with @watariai and your answer.". Where your workspace has answering by email turned on, reply to the email with your answer from the address it was sent to. Replies are accepted only from mail that passes DMARC, so if your company's email domain has no DMARC policy, answer on the issue instead. One notification per question. Email is on by default for owners and admins; members can turn it on |
| Fix ready to review | Switch | Watari opened a draft fix for an issue | |
| Customer update ready | Switch | The fix is live and a customer update is ready for you to send. Not sent when Watari sends an update you already approved | |
| Critical issue | Switch | Always on | Watari found a critical issue |
When something happens
| Event | In-app | Notes | |
|---|---|---|---|
| New issue | Switch | Switch | Watari read a ticket and found a new issue |
| Issue status changed | Switch | Switch | The status of an issue changed |
| Daily digest | Switch | Email only; on by default |
Your workspace (owners and admins)
| Event | In-app | Notes | |
|---|---|---|---|
| Something stopped working | Switch | Switch | Watari could not finish a step, like reading a ticket or filing an issue |
| Usage warning | Switch | Always on | Your workspace is nearing its monthly work limit, or a request to raise it was answered |
| A connected tool stopped working | Switch | Switch | A connected tool needs connecting again |
| Billing action needed | Switch | Always on | Payment failed or trial ending |
The workspace group is shown only to owners and admins. Members do not see or set those events.
The page also says where new issues are posted in team chat. An admin gets a link to Settings → Connected tools to change it; a member is told who chooses the channel.
Daily digest
The daily digest is a per-user email that reads like the Issues page. It is on by default for every teammate:
- How many issues need you, first: "3 need you." The subject says the same after the workspace name, for example "Northwind: 3 need you today", so two workspaces never send two identical subjects.
- Each of those issues, with its next step ("Watari asks", "Review the fix") and a link to it, under the same two headings as Home: You can do these first (things someone who talks to customers can finish, such as answering Watari or updating the customer), then Waiting on your engineers. The first eight are listed, the rest are counted.
- How many Watari is working on.
- What got done: the customer reports Watari read and the issues it opened in the last day, and the issues finished this week.
One button opens Issues. The digest is sent at 8:00 AM UTC every day to every teammate who has not turned off the Daily digest email toggle. On a day when nothing needs anyone and nothing new arrived, no digest is sent.
To stop receiving it, go to Settings → Notifications and turn off the Daily digest email toggle, or use the unsubscribe link in any digest email.
Archived-channel recheck
If the Slack channel gets archived after Watari is set up to post there, Watari notices and pauses posting to that channel. It doesn't retry indefinitely. Instead, it marks the Slack connection as having a problem and checks the channel again once a month.
When that check finds the channel is available again (unarchived, or the bot was re-invited), posting resumes automatically. You don't need to reconnect or pick the channel again.
If you want to trigger a recheck manually rather than waiting for the next scheduled pass, visit Settings → Connected tools. The Slack card reads Watari could not post in Slack. Click Check channel, confirm the channel, and click Send test notification. A test that arrives clears the problem.
Next: Invoices, credits, and caps: mismapped credit window and overage cap configuration: download invoices, understand the mismapped credit window, and configure overage behavior.