Back to Docs
Email notifications

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

  1. Open your agent → Configuration tab → scroll to the bottom and open Alerts.
  2. 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.
  3. 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:

┌────────────────────────────────────────────────────────┐
│ ● Demo booked ✎ ✕ [ON] │
│ When the customer confirms a date for a demo │
│ Also send by: [✓ Email] [ Telegram] │
│ [ ✉ [email protected] × ] [ ✉ [email protected] × ] │
└────────────────────────────────────────────────────────┘

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 Agents

WHEN

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 settings

Setting 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?

Yes. Every alert always lights up the bell in Kronos AI and fires a push to your phone or browser (if you have push enabled). Email is sent on top of that, to the recipients you configured. You can't turn the in-app notification off for an alert — turn the alert itself off instead.

What happens if Email is on but the recipient list is empty?

Kronos AI falls back to your account email (the one you signed up with). It's a safety net so a notification is never silently lost. The first time you turn on Email, your account email is preset as a chip, so this fallback usually doesn't kick in.

What if my agent sends 50 alerts in a minute?

In Instant mode you'll get 50 emails. Switch to Queue mode at notification settings to batch them into a single digest every N minutes. Digests group by alert, so you'll never get a single email that mixes recipients meant for different teams.

Can different alerts notify different teams?

Yes — that's the whole point of recipients living on the alert. A "Sale closed" alert can list ceo@ + ae@, while a "Refund requested" alert lists support@ only. They never mix.

Can a specific inbox use a different throttle than others?

Yes. Open the inbox at /app/settings/inboxes, scroll to Email Delivery Timing, toggle Override global, and pick Instant or Queue for that inbox only. Recipients are NOT inbox-scoped — they stay on the alert.

Will recipients see the customer's phone number / IG handle?

The email subject is the alert name ("🔔 Alert: Demo booked"). The body shows the agent's note and a button labeled "View conversation" that requires Kronos AI login. Recipients without a Kronos AI account can't view the conversation contents — they just see the alert summary.

Can an alert carry a file?

Yes. Any alert can carry an optional attachment — a file the agent created or one of the Resources assigned to it. There is nothing to turn on: the agent attaches a file only when the alert or its instructions ask for it, or when the file is clearly what your team needs. The email itself links to the conversation; it does not attach the file.

How do I add a teammate who doesn't have a Kronos AI account?

Add their email as a recipient. They'll receive the notification email. To view the actual conversation they need an account (invite them as a member of your workspace separately).

Is there a way to stop receiving all emails at once?

Turn off Email on every alert. That's the master kill-switch. Emptying the recipient list of an alert won't stop emails — they'll just fall back to your account email. Turning an alert off stops it completely, in-app included.

My prompt still says mark_objective_achieved. Does it still work?

Yes. The tool is now called send_alert (parameter alert_name), and older prompts that use mark_objective_achieved keep working.

What happens to queued emails if my plan is canceled?

Operational data including queued email rows is purged on cancellation along with your other agent/conversation data. KPI and billing data is preserved separately.
Email Notifications — Kronos AI Docs | Kronos AI