Notifications

The Notifications page decides who hears about what. Pick the events that matter to your team, such as a visitor asking for a human, a new lead, or an agent running low on AI credits, and choose where each alert arrives: in the dashboard, by email, on Telegram, or in Slack.

7 min read Updated

Notifications are configured per agent. Open an agent and click Notifications in the sidebar. You get a single grid: each row is an event, each column is a delivery channel. Tick a box to turn that alert on. Your AI agent keeps answering visitors on its own. Notifications are how a person on your side finds out when a conversation needs a human, when a lead is worth following up, or when the agent is about to run out of AI credits.

Settings are saved per agent. If you run more than one agent, set up notifications for each one. New agents start with sensible defaults already switched on, so you do not have to configure anything before going live.
The Notifications grid with five events, including the Usage limit warning at 80%, and the channels In-app, Email, Telegram, Slack and Teams marked Soon
Each row is an event, each column is a delivery channel. Teams is coming soon.

Which events can alert you

There are five events you can be notified about:

  • New chat started. A visitor starts a conversation in the chat widget. Useful if you like to watch conversations as they begin.
  • Live agent requested. A visitor asks to speak to a human, by clicking the Talk to a human button or by asking the agent. This is the most time-sensitive event, because someone is waiting for a reply.
  • New lead generated. A visitor shared their contact details, either in the pre-chat form before the chat starts or during a conversation, for example through the Lead Generation skill.
  • New visitor message. Someone replied in a chat you have already joined. This keeps you in the loop on conversations you are actively handling.
  • Usage limit warning. The agent has used a set share of its AI credits for the current billing period. See the usage limit warning below.
These events tie directly into the rest of the dashboard. Live agent requested and New visitor message are part of live chat, New lead generated feeds your Leads, and the Usage limit warning is about your AI credits.

Where alerts are delivered

Each event can be delivered through one or more channels. You choose them independently per event, so a low-priority event can be in-app only while an urgent one also reaches your phone.

  • In-app. A pop-up notification inside the dashboard while you are signed in. In-app alerts appear anywhere in the portal, not only on the Live page, so you do not have to keep the inbox open to catch them.
  • Email. A message sent to the recipient addresses you set up. Best for alerts you need to see even when nobody has the dashboard open.
  • Telegram. The alert is posted into a Telegram chat you connect. Telegram works for every event, including New visitor message, so it is a good real-time companion while you handle a chat.
  • Slack. The alert is posted into a channel of a Slack workspace you connect.

A Teams column is shown with a Soon label and cannot be selected yet.

Not every channel is available for every event. New visitor message can fire on every reply in a joined chat, so to avoid flooding your inbox it is limited to in-app and Telegram. Email and Slack are not selectable for that event.

The usage limit warning

Usage is measured in AI credits. The Usage limit warning tells you when an agent has used a set share of its credits for the current billing period (its plan credits plus any extra credits), so you can add credits or upgrade before it pauses.

  • Choose the threshold. In the event's row, Warn at lets you pick 50, 80, 90, or 95 percent. The default is 80 percent. The label next to the picker still reads "of monthly AI responses used"; the share is calculated from AI credits.
  • Once per billing period. The warning is sent once when the threshold is crossed, not again for every answer after it.
  • On by default. In-app and email are switched on for this event. If no email recipient is set, the email goes to the account owner.
When credits run out, the owner is always told. The moment an agent has used up its AI credits, the agent's owner receives an email that the agent pauses, once per billing period. This email cannot be switched off, because it is about a service interruption, not a preference. An in-app alert is shown as well if in-app is on for the usage warning. See When credits run out for what visitors see and how to resume.

The default setup

Every new agent is created with notifications already configured, so alerts work on day one without any setup. In-app alerts are switched on for every event. Email is switched on for the events most worth interrupting your day: a visitor asking for a human, a new lead, and the usage limit warning. Telegram and Slack start switched off until you connect them.

EventIn-app (default)Email (default)
New chat startedOnOff
Live agent requestedOnOn
New lead generatedOnOn
New visitor messageOnNot available
Usage limit warning (at 80%)OnOn

When an agent is created, the account owner's email is also pre-filled as a recipient, so the default email alerts have somewhere to go straight away. You can change any of this at any time. Nothing is locked in.

Setting recipients

As soon as you turn on email, Telegram, or Slack for any event, a Recipients area appears for that channel. Each list is shared across every event that uses the channel, so you maintain one list rather than repeating it per event.

  1. Turn on a channel for an event

    Tick the box for at least one event in the grid. The recipient fields for that channel only show up once the channel is in use somewhere.

  2. Add the recipients

    • Email recipients: type an address, use Add email for more, or remove one you no longer need. Every address must be valid.
    • Telegram recipients: click Connect Telegram chat. Telegram opens in a new tab; press START in the chat to finish linking, then tick the chats that should receive alerts.
    • Slack channels: connect your Slack workspace and pick at least one channel. Public channels work right away. For a private channel, invite the bot in that channel with /invite @YourBotName, then refresh the list.
  3. Save your changes

    Click Save. If a channel is switched on but has no valid recipient, the page asks you to fix it first. If you leave the page with unsaved changes, the dashboard warns you so nothing is lost by accident.

Not seeing the email alerts? Check your spam folder and add build@ultimo-bots.com to your safe senders, so future notifications land in your inbox.

How notifications connect to live chat and leads

Notifications are the glue between your agent and your team. Tuning them is how you control how loud each part of the product is:

  • Live chat. Live agent requested and New visitor message are the heartbeat of the live chat experience. When a visitor asks for a human, an alert is how the right person knows to open the inbox and take over from the agent.
  • Leads. New lead generated mirrors what shows up in your Leads. Turning on email for this event means a new lead reaches your team even when no one is watching the dashboard.
  • Usage. The Usage limit warning gives you time to add AI credits before the agent pauses.

A practical setup for most teams is to leave the defaults as they are: in-app for everything so you can glance at activity, plus email for the events that need a fast human response. From there, dial individual channels up or down to match how your team works.

Notification recipients are not the same as team members. Adding an email or a chat here only routes alerts to it. It does not give anyone access to the dashboard. To give a colleague access, invite them on the Team members page.

Next steps

Notifications work best alongside the features they alert you about: