A rolled-up email that summarizes what your AI employees did over a set period, instead of a separate message for every event. Today, notification email in Sistava sends per event and per category (employee updates, task completion, credit alerts, and so on); a digest option that batches those into one scheduled email is planned but not built yet.
Sistava already notifies you by email when something needs attention: an employee finishes a task, a credit threshold is crossed, someone mentions you in a comment. Each of those today goes out as its own email, grouped only into a handful of categories you can turn on or off from Settings > Notifications.
Email Digest Notifications is the planned next step: instead of an inbox that fills up one email at a time, you would get a single scheduled summary, for example once a day, that rolls up everything your employees did and everything waiting on you into one message.
The difference from today's per-event email is frequency and shape, not content. Per-event mail tells you the instant something happens; a digest trades that immediacy for a predictable, low-noise inbox rhythm, useful when you employ several AI employees and do not want a message every time one of them finishes a task.
It is worth knowing what the inbox already does for you before the digest lands, because most people assume it is noisier than it is. Only the events that genuinely need you leave the system as email: an employee asking for a decision or an approval, an employee raising something proactively, and credit alerts. The rest ring the in-app bell and stop there.
On top of that, several quiet guards already run on every notification email. One sent after a short delay is dropped entirely if you read the bell first, so opening the app cancels the email you were about to get. A newer message about the same thing replaces an older queued one instead of both arriving. And there is a hard ceiling on how many notification emails one person can receive in an hour and in a day, which no amount of employee activity can push past.
Your email preferences live on one flat page with five categories: your team's work, product updates, tips and check-ins, account and security, and billing and credits. The first three are yours to switch on or off. The last two stay on, because missing a sign-in email or a failed payment costs you more than an email you did not want. The in-app bell is never switched off by any of this.
Notifications fire two ways right now: an in-app bell alert, always on, and an email for the categories you have switched on in Settings > Notifications > Preferences. Two categories, account and security, and billing and credits, are locked on because they carry information you need regardless of preference.
Each qualifying event sends its own email, either immediately or after a short delay if you have not read the bell notification yet. There is no batching: if three employees finish tasks in the same hour, you get three separate emails, not one summary.
A digest is not a new category of thing to be notified about. It is a different delivery rhythm for events you already receive: instead of real-time, one-at-a-time email, activity would accumulate and go out as a single scheduled roundup.
That matters most for anyone running several AI employees at once, where per-event email can turn into a steady drip through the day. A digest would trade the instant-notice benefit of per-event mail for a calmer inbox: fewer emails, each one carrying more, sent on a schedule you control rather than the moment something happens.
Reading the bell cancels the email. Notification email for the routine stream is sent after a short delay rather than instantly, and if you have already seen the alert in the app by the time that delay is up, the email is dropped and never sent. People who work in the app all day therefore receive very little notification email at all.
Repeats are collapsed rather than stacked. If a newer message about the same conversation arrives while an older one is still queued, the older one is dropped instead of both landing. If the thing you were being asked about has already been resolved by the time the email is due, it is dropped too.
There is a hard ceiling per person, per hour and per day, on how many notification emails can be sent. No burst of employee activity can push past it. A digest would add a chosen rhythm on top of all of this rather than replacing any of it.
Planned: one scheduled email instead of many individual ones
The current notification system already tracks every event that matters (employee updates, task completion, credit alerts, comment mentions, input requests, billing events, direct messages) and already knows which of them you have enabled for email. A digest would sit on top of that: instead of sending each qualifying event as its own email the moment it happens, it would hold them and send one combined email on a schedule you set.
Because the underlying event tracking and per-category preferences already exist, a digest is a delivery mode on top of the current system, not a separate one. It has not shipped yet, so no digest schedule, frequency setting, or digest email template exists in the product today. When it lands, it slots into the same Settings > Notifications screen you already use, rather than opening a new area of the product.
The design intent is that a digest never quietly swallows something urgent. Account, security, and billing email would keep arriving the moment it matters, because a failed payment or a balance at zero is worthless to you a day late. The batching is meant for the routine stream, employee updates and finished work, which is exactly the part that turns into a drip when several employees are running at once.
If you employ multiple AI employees working through the day, a digest would let you check one summary email instead of reading a separate notification every time an employee finishes a task or reaches out.
A daily digest would give you a single moment, for example first thing in the morning, to see everything that happened and everything waiting on your decision, rather than reacting to notifications as they arrive.
For anyone who does not want to keep the in-app bell open all day, a scheduled digest would be a way to stay current on employee activity, task completions, and pending approvals through one email instead of many.
After a weekend or a short trip, a digest would give you one place to catch up on what your employees did while you were gone, instead of scrolling back through a scattered inbox to work out which messages still need a decision.
| Before | After |
|---|---|
| Every event that needs you arrives as its own email, whenever it happens. | Planned: one scheduled roundup carrying the same events, on a rhythm you choose. |
| Turning the volume down means switching a whole category off and hoping the bell catches it. | Planned: keep the category on and change only how often it lands in your inbox. |
| You check the in-app bell through the day to know where each employee got to. | Planned: one summary listing what happened and what is still waiting on your decision. |
| Routine updates and time-critical alerts share the same inbox with the same urgency. | Planned: routine activity batches while account, security, and billing email keeps arriving immediately. |
Not yet. Sistava currently sends a separate email per event and per category rather than a rolled-up summary. Digest scheduling is planned but not available in the product yet.
The intent is for a digest to be an alternative delivery mode, not a forced replacement: you would choose between real-time per-event email and a scheduled summary. That choice has not been built yet, so today every enabled category sends per event.
Credit alerts are locked email categories today because they are time-sensitive: your balance crossing 15% or 0% needs to reach you immediately, not on a delay. Any future digest would need to preserve that immediacy for credit alerts rather than batch them, since delaying a 0%-balance alert would mean you find out after work has already paused.
The same place you manage email today: Settings > Notifications > Preferences, next to the existing on/off toggles for each email category. No separate app, integration, or upgrade would be required; it would appear as an additional delivery choice alongside the per-event option that already exists there.
Yes, for most of them. The email preferences page lists five categories and three of them, your team's work, product updates, and tips and check-ins, have a switch you control. Account and security and billing and credits stay on, because missing a sign-in email or a failed payment costs you more than an email you did not want.
Yes. The in-app bell always fires and cannot be switched off, so every notification is still waiting for you inside Sistava even with every optional email category turned off. Email is the loud copy, the bell is the record.
No. Most activity only rings the in-app bell. Email is reserved for the events that actually need you, such as an employee asking for a decision or an approval, an employee raising something proactively, and credit alerts.
Yes. There is a hard per-person ceiling on notification email in any hour and in any day, and no amount of employee activity can push past it. Emails that would exceed it are dropped, not queued up to land later in a burst.
Email Digest Notifications is part of How you see what they did.
A real-time activity feed shows who is working on what right now. The step-by-step inspector traces every tool call, decision, and reasoning chain. Cost tracking breaks down spend per message, per employee, and per team. Walk through your live 3D office to see your workforce at a glance.