# Slack Notifications

Connect Slack and your platform notifications move there automatically: an Employee finishing work, reporting in, or waiting on your decision shows up as a Slack DM instead of email. Approval requests arrive as an interactive card with Approve and Reject buttons, so you can resolve them without leaving Slack.

Once your workspace has an active Slack connection, Slack quietly becomes your primary notification channel. You do not flip a switch for this: connecting Slack is enough, and from that point on the two event types that matter most while you are away from your desk (an Employee update and a request for your input) land in Slack instead of your inbox.

Every message comes from one bot identity so your Slack sidebar does not fill up with a different bot per Employee. The DM text still names the Employee that triggered it, so you know at a glance who needs you. Requests that need a yes or no, an approval on spend, a choice between options, arrive as a Block Kit card with buttons: you can approve or reject right there, and the platform picks it up the same as if you had answered inside the app.

The difference from email here is speed and friction. Email on this same event type is deliberately delayed and capped, because an inbox is easy to let pile up; Slack delivery is immediate and uncapped, because Slack is where fast-moving teams already expect real-time pings, and a DM is easier to act on from a phone than opening a mail client. The trade is intentional: Slack for urgency, email for a durable record you can search later.

A single per-user hourly ceiling exists purely as a safety valve against a misbehaving Employee looping the same update, not as a spam control; a genuinely critical decision (one involving money or data loss) always gets through regardless of that ceiling. Everything else about volume is left to Slack's own mute and do-not-disturb controls, the same as any other app you have installed there.

## What Moves to Slack

Two notification types route to Slack today: an Employee update (an Employee finishes a piece of work or reaches out proactively) and an input request (an Employee is waiting on your approval or a decision). Both already exist as in-app bell and email notifications; Slack is an added delivery path for these two, not a replacement.

Other notification types, task assignments, credit alerts, billing events, comment replies, stay on the bell and email exactly as before. Slack was built for the two event types where speed of response matters most: work finishing and decisions waiting on you.

## One Bot, Every Employee

Rather than installing a separate Slack bot per Employee, proactive Slack DMs are relayed through a single install so your Slack workspace shows one consistent presence. The message body always names the actual Employee behind the update, so you never lose track of who is talking to you even though the sender in Slack stays the same.

This keeps your Slack sidebar clean as you hire more Employees: adding a tenth Employee does not mean a tenth bot showing up in your DMs, it means one more name appearing inside the messages you already get.

## How It Works

**Connecting Slack quietly becomes your notification channel**

Slack Notifications is not a separate setup step. It rides on top of the existing Slack connection: the moment your workspace has an active, non-revoked Slack install tied to your account, the platform treats Slack as your primary loud channel for the two notification types built for it today, an Employee update and a request for your input.

Each notification still creates its normal bell entry first; nothing about the in-app notification list changes. The Slack DM is an additional, faster delivery path layered on top, sent through your Personal Assistant's Slack install so you see one consistent sender in Slack no matter which Employee actually triggered the message.

Approval-style requests get an interactive card instead of plain text, with buttons to approve or reject in place. Everything else renders as a short text message naming the Employee and summarizing what happened. If Slack delivery fails for any reason, silently and without blocking your in-app notification, you still have the bell and, depending on the notification type, email as a backup.

## Use Cases

### Catch a decision the moment it is needed

An Employee hits something that needs your approval, a spend decision, a choice between two directions, while you are in a meeting or away from the app. Instead of finding out an hour later from your inbox, it lands in Slack as a card you can approve or reject with one tap.

### Keep tabs on a team without opening the app

Multiple Employees are working through the day. Rather than checking the bell repeatedly, you let updates come to you in the Slack channel where your own team already lives, each message naming which Employee it is from.

### Respond faster than email allows

Email on these event types is deliberately delayed to avoid inbox noise. When a decision genuinely cannot wait, Slack delivery skips that delay entirely, so the message is in front of you as soon as it happens.

## FAQ

### Do I need to turn Slack Notifications on separately?

No. There is no separate toggle. Connecting Slack to your workspace is what activates it: once you have an active Slack install, Employee updates and input requests start arriving as Slack DMs automatically.

### Will I stop getting these notifications in the app or by email?

No. The in-app bell notification is created exactly as before for every event; Slack is an added delivery path on top of it, not a replacement. Email for these same event types still exists as a fallback and follows its own delay and cap rules.

### Can I approve or reject a request directly from Slack?

Yes, for input requests. Those arrive as an interactive card with Approve and Reject buttons, and acting on them in Slack resolves the request the same as answering it inside the platform.

### Which notification types are available in Slack right now?

Employee updates and input requests only. Task assignments, credit alerts, billing events, and comment replies are not routed to Slack today and stay on the bell and email.

### Is there a limit on how many Slack messages I can get?

There is a generous hourly ceiling per user that exists only to stop a misbehaving Employee from looping the same message, not to cap normal use. A genuinely critical notification always gets through regardless of that ceiling; day-to-day volume control is left to Slack's own mute and do-not-disturb settings.

## Where Slack Notifications fits

Slack Notifications is part of Ways you talk to them.

Chat in the app with live reasoning, speak to your AI voice agent over a call, message on Slack or WhatsApp, send an email, or embed a widget on your website. Every channel connects to the same AI agent with the same memory and capabilities. Switch channels mid-conversation and your employee picks up right where you left off.

- [Ways you talk to them](/en/features/channels): Every channel. One conversation.

## Read the guide

- [Guide: Slack Notifications](/en/guide/account/notifications)

## More in Channels

- [Web Chat](/en/features/channels/channel_web_chat): Chat with any AI employee directly in the workspace, with a streaming reply, a live execution timeline showing what it is reading, thinking, and doing, and inline approve/reject buttons when it needs a sensitive action confirmed. It is the default channel: nothing to configure, works on desktop or mobile, and every conversation persists so you can pick it back up later.
- [Voice Calls](/en/features/channels/voice_channel): Voice Calls is a planned channel for speaking to an AI employee out loud and hearing it reply in real time, instead of typing. It is not available yet: there is no voice button in the workspace today, and the feature is paused while the underlying voice flow is redesigned. When it ships, a voice call will run through the same skills, tools, and memory as a typed conversation.
- [Connect an Email Provider](/en/features/channels/channel_email): Point your own SendGrid, Mailgun, or Postmark inbound-parse webhook at a tenant-scoped endpoint and every email that lands there gets turned into work for an employee. Forward support requests, sales inquiries, or internal approval emails and the employee reads the sender, subject, and body, then acts on it in the background. You get a 202 response immediately; there's no waiting on the request.
- [Personal Mailbox](/en/features/channels/channel_mailbox): Every employee gets its own email address on the shared Sistava domain the moment you hire it, no setup. Email it directly, CC it on a thread with other people, or forward something over, and it reads and replies within seconds. Free to send from, with a monthly cap by plan. Control the shared employee signature in Company Profile, or connect your own Gmail or Outlook when you want it sending as you, with no cap.
- [Send from Gmail or Outlook](/en/features/channels/connected_mailbox): The built-in employee address is free and always on, but it sends as the employee, not as you. Connect your own Gmail or Outlook instead and an employee sends and replies from your real address, in your name, with no monthly sending cap on any plan.
- [Talk to Your Employee on Video](/en/features/channels/channel_in_app_video): In-App Video is a planned channel for live, face to face video calls with an AI employee, camera and microphone, directly inside the workspace. It has no working implementation today: it appears in Settings > Technical > Channels as a Coming soon placeholder only. Once it ships, it is meant to run on the same execution pipeline as every other channel, so the employee keeps its skills, tools, training, and conversation memory on a video call. If you need an employee in a live call today, it can already join a Google Meet, Zoom, or Microsoft Teams meeting as a participant, which is a different capability and available now.
- [Chat Widget](/en/features/channels/channel_chat_widget): The Chat Widget will let you embed an AI employee directly on your public website so visitors can ask questions and get answers without leaving the page. It is on the roadmap and is not available to configure yet: today it appears in Settings > Technical > Channels as a Coming soon placeholder with no setup, embed snippet, or Manage action.
- [SMS](/en/features/channels/channel_sms): SMS is a planned channel for reaching an AI employee by ordinary text message, with no app to install. It is on the roadmap and not available today: there is no SMS number, no inbound texting, and no way to turn it on yet. Until it ships, use web chat or Telegram for mobile access from any phone.
- [WhatsApp](/en/features/channels/channel_whatsapp): WhatsApp is a planned messaging channel for talking with an AI employee from your phone. It is not connected yet: the card shows as coming soon and cannot be set up today. When it ships, it will carry the same employee memory, skills, and guardrails as web chat, Telegram, Slack, and the mailbox. Telegram and Slack are live now and give you the same access from a phone, so nothing you set up today has to be rebuilt when WhatsApp arrives.
- [Discord](/en/features/channels/channel_discord): Discord is a planned channel for bringing an AI employee into the servers and direct messages your community already uses. It will connect the same way Slack does today: authorize a bot through OAuth, then map it to one employee. It is not available to connect yet, so no Discord traffic reaches an employee until it ships. Slack, Telegram, each employee's own email address, and web chat cover the same job in the meantime.
- [Calendar Invites](/en/features/channels/channel_calendar): Add your employee's personal address as a guest on any Google, Outlook, or Apple calendar event and they show up for the meeting automatically, no RSVP or extra app on your side. Once the meeting starts, the employee joins the Meet, Zoom, or Teams call, listens, speaks when addressed, and writes a summary afterward. There is nothing to switch on for the invite itself, just turn on the Meeting Attender tool for that employee once.
- [Slack Channel](/en/features/channels/channel_slack): Bring your AI employee into Slack as a real bot user your team can mention, DM, or trigger with a slash command. Every reply lands in the same thread, and memory, tasks, skills, and tools stay shared with web chat, so a conversation started on Slack continues anywhere else. You approve or reject requests right from Slack, and the bot only speaks when mentioned, DM'd, or already in a thread.

## Explore

- [Every feature](/en/features)
- [Hire an AI employee](/en/market)
- [Pricing](/en/pricing)