Get an email when your agent sends an alert
Hook your team straight into the moment that matters — a sale closed, a demo booked, a lead qualified. Kronos AI sends a clean transactional email with a one-click link to the conversation.
TL;DR
- Open your agent → Configuration tab → scroll to the bottom and open Alerts.
- On any alert, next to Also send by, turn on
Email. Your account email auto-fills as the first chip; add up to 5 recipients. - Done. Delivery is instant by default — switch to a queued digest in notification settings.
What it does
Every Kronos AI agent can be given alerts — moments you want to hear about, like "Demo booked" or "Customer asks for a person". Each alert has a name and a description of when the agent should send it. When the agent sees that moment in a conversation, it sends the alert (with a short note) using its send_alert tool, and Kronos AI delivers it:
In-app notification (always)
A ping in your Kronos AI bell and on your phone or browser (push). Every alert sends one — there is nothing to turn on.
Email notification (optional)
A transactional email from [email protected] to the recipients you choose, with a link to the conversation.
Email is an extra channel you turn on per alert, next to Also send by. So is Telegram. The in-app notification is sent either way.
Turning email on for an alert
Open your agent at /app/ai-agents/<your-agent-id>, stay on the Configuration tab and scroll to the collapsible Alerts group at the bottom. Each alert shows its name, its description, a pencil to edit it, a delete button and an on/off switch. While it is on, you can pick extra channels; when Email is on, a chip input for recipients appears:
Email starts off. The first time you turn on Email for an alert, your account email is preset as a chip — remove it or add up to 5 addresses. Different alerts can route to different teams.
Who vs When — two separate questions
Kronos AI splits the two decisions into different places so each one has a single source of truth:
WHO
Per alert, in the agent editor.
Each alert has its own list of up to 5 recipients. Different alerts can route to different teams. Falls back to your account email if Email is on but the list is empty.
Open AI AgentsWHEN
Global setting, with per-inbox override.
Choose between Instant (one email per alert) and Queue (batched digest every N minutes). High-volume inboxes can override the global default so they get a digest while quieter inboxes stay instant.
Notification settingsSetting recipients per alert is intentional: it's how you make a "Sale closed" alert notify the CEO while a "Refund requested" alert notifies the support lead, without having to juggle global rules.
Instant vs Queue: choosing a delivery mode
By default, every alert your agent sends triggers its own email (Instant). For high-volume agents that send many alerts per hour, this can be noisy — switch to Queue mode to batch them into a digest.
Instant (default)
One email per alert
- Fires immediately as the agent sends the alert.
- Subject: "🔔 Alert: <alert name>".
- Best for low-volume / high-signal agents.
Queue
Group into a digest
- Alerts collect for N minutes (1–1440).
- Then sent as a single email: "🔔 3 alerts from your agent".
- Protects your inbox during burst activity.
The throttle window is per-user, per-inbox. A digest is only flushed when the oldest queued alert reaches the window — quiet inboxes never email.
Managing recipients (per alert)
Each alert stores its own list of up to 5 email addresses. They're entered as chips: type, press Enter (or comma / Tab / blur), and the email becomes a removable tag.
- Auto-preset. The first time you turn on Email for an alert, your account email is added as the starting chip. Edit or remove it freely.
- No verification step. Emails are added immediately. Only invite addresses you trust — anyone listed will receive the notification body.
- Recipients see the full body. Including the agent's note and a direct link to the conversation. The link requires Kronos AI login.
- Emptying the list is fine. If you remove all chips but leave Email on, Kronos AI falls back to your account email so notifications never silently disappear.
Sender, deliverability, and unsubscribing
All emails come from Kronos AI <[email protected]>. Accidental replies route to [email protected] (our support inbox) so nothing is lost.
Each email includes a standard List-Unsubscribe header — Gmail and Outlook render this as a native "Unsubscribe" button at the top of the message. The unsubscribe link points at your notification preferences page where you can turn email off globally or per inbox.
We use SPF + DKIM (via Hostinger) so the emails authenticate cleanly. If a recipient marks one as spam, future emails to that specific address may degrade — you can re-enable by removing and re-adding the address.
Where to do what
FAQ
If Email is on for an alert, do I get two notifications?
What happens if Email is on but the recipient list is empty?
What if my agent sends 50 alerts in a minute?
Can different alerts notify different teams?
ceo@ + ae@, while a "Refund requested" alert lists support@ only. They never mix.Can a specific inbox use a different throttle than others?
Will recipients see the customer's phone number / IG handle?
Can an alert carry a file?
How do I add a teammate who doesn't have a Kronos AI account?
Is there a way to stop receiving all emails at once?
My prompt still says mark_objective_achieved. Does it still work?
send_alert (parameter alert_name), and older prompts that use mark_objective_achieved keep working.