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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.