Notifications #

The platform can notify you about important events across multiple channels, so you never miss a critical update — a new contact, a low credit balance, or a message that needs human attention.

Where to Find Notifications #

How to get there: Settings → Notifications group → Notifications.

Open Settings (gear icon near the bottom of the left sidebar), then click Notifications in the Settings menu. On a phone, tap the menu icon (☰) first.

At the top of the page is a Push on this device card for turning browser push notifications on for the device you’re using. Below it is one table: each row is an event category, with an On switch and three channel columns — Email, Push, and In-App. Below that is a card for managing additional email recipients.

Notification Channels #

You can also route events to an external system — your CRM, a Slack channel, WhatsApp, Discord — via a webhook. Configure that separately on Webhooks; it isn’t one of the three toggle columns on this page.

What each alert tells you: every notification email has an Open button that takes you straight to the chat, task or setting it is about, on your own app address. On accounts managed by an agency, the email subject and the push title start with the account’s name in brackets, for example [Acme Dental] WhatsApp needs a quick reconnect, so you can tell at a glance which client it is about. When a message fails to send, the alert says why (for example that the 24-hour reply window has closed) and links to the conversation.

Enabling Push: push is enabled per device from the Push on this device card at the top of the page. Click Enable on this device and approve the browser’s permission prompt — from then on, any category with its Push toggle on will notify that device. Once enabled, the card shows a Send test notification button so you can confirm it’s working, and a Turn off on this device button to stop notifications on that device only. Repeat the enable step on each computer or phone you want notified. If the card says notifications are blocked, allow them for the site in your browser’s own settings first.

Team members working in more than one account: notifications belong to the account they happen in, not to the person. The bell only shows alerts for the account currently open in the switcher, but push is delivered to the device regardless of which account is open. So a team member who works across several accounts should enable push from this card once inside each account (and be added as an email recipient in each one) to be alerted about all of them. The Send test notification button in each account confirms it’s working.

Push on your phone: open the app in your phone’s browser, install it to your home screen (Chrome → menu → Add to phone, Safari → Share → Add to Home Screen), open it from the home screen, then enable push from the same card. You’ll get native push notifications on the lock screen — no App Store needed.

The Notification Bell #

In-app alerts live under the bell icon in the left sidebar (top bar on mobile). A counter shows how many are unread.

• Click a notification to jump straight to the page where you can act on it — an alert about your AI setup opens the AI Agent it’s about, a channel disconnection alert opens Channels. Opening it marks it read.
• One message, one alert. A single incoming message can qualify for more than one category at once (a starred contact whose AI is paused, say, matches both Important Contact Messages and Messages from Paused Contacts). You get one entry in the bell and one push for it, not one per category: the first alert wins and carries the context, so a starred contact’s alert reads “New message from Jane (bot paused)” when the AI is paused for them. Email alerts are separate and keep their own frequency settings.
• Alerts about the same contact clear together. One conversation can raise several alerts (a message while the bot is paused, a human-alert, a read receipt), so they’re treated as one thing to read: clicking any one of them marks them all read, and opening that contact’s chat clears all of them too — including any browser push notifications still on screen for that person. You never have to tick off the same conversation twice.
• Unread alerts stay on top. Everything you haven’t opened yet sits above the alerts you’ve already read, newest first within each group, so an unread alert never scrolls away under newer ones you’ve dealt with. Open it (or mark it read) and it drops back into the timeline.
• Mark one read without opening it. Hover a notification and click the tick on its right: it’s marked read where it is, the counter drops, and you stay on the page you’re on. Alerts about the same contact clear together here too.
• Mark all read clears the counter in one click.
• Written in your language. Bell and push alerts use the account’s language (the one set under Account Settings), the same as your notification emails. Alerts that were already in the bell keep the language they were written in.
• View all notifications at the bottom of the bell opens the full notifications page, which has a Reminders tab — the task reminders you asked for, in one place, separate from everything else in the feed.
• Dismiss a notification with the X next to the tick to remove it permanently.

Alerts about something that failed — a channel disconnection, a broken API key, a critical alert — are also kept in the Error Log, with the code and the fix, so you can look one up long after the notification is gone.

Which events appear under the bell follows your per-category settings below: the In-App column controls it per category, independent of Email and Push.

Notification Categories #

There are 23 notification categories in total: the 22 listed in the table below, plus New Sub Account, which only exists on agency accounts. Each category has its own On/Off switch and, when on, per-channel toggles for Email, Push, and In-App.

A few critical alerts always stay locked on (shown with a lock icon instead of a switch): subscription updates, credit alerts, auto-recharge, appointments, human alerts, API key errors, and critical alerts. These can’t be switched off, so you never miss something that could interrupt your service or cost you money.

The full list of categories:

Emails to chat widget visitors #

When you or your AI reply to someone on your website chat widget and they have left the page, the visitor can get an email saying they have an unread reply, with a link back to the conversation. It goes out 15 minutes after your reply, and only if the visitor has not seen it by then and left an email address.

This email goes to your visitor, not to you, so it has its own switch in the Chat widget visitors card on this page: Email chat widget visitors when they have an unread reply. Turn it off and visitors never get it; your own alerts are not affected.

Until you touch that switch, it follows your Message Reads row, which is how this email used to be controlled, so nothing changes for you until you set it.

Email Notification Recipients #

By default, notifications go to your account email address. Add more recipients so other people receive the same broadcast alerts.

Team members aren’t added here automatically. Inviting someone to your team doesn’t subscribe them to broadcast alerts like New Contacts. They automatically receive their own Lead Assignment emails for leads assigned specifically to them. Add their address below if you want them on the broader alerts too.

Adding a Recipient #

1. In the Notifications page, find the recipients card and click Add email.
2. Enter the email address.
3. We email a 6-digit verification code (valid 30 minutes) to that address.
4. Enter the code next to their email in the app — they start receiving notifications once verified. If the code expires, click Add email again to resend.

You can add multiple recipients. Each one has its own set of category subscriptions, adjustable from the Categories button next to their row once verified.

Removing a Recipient #

Click the trash icon next to any email address to stop sending it notifications.

Toggle Everything On or Off #

Each category has its own On switch. There’s no single “disable everything” button — toggle categories individually, or leave the critical ones (which are always on regardless) as your safety net during a quiet period like a vacation.

Tips #

• Start with real-time attention on Human Alerts and Credit Alerts so you can respond quickly.
• Add your support team as email recipients for Human Alerts so someone’s always covering it.
• Route Human Alerts to a webhook if your team lives in Slack, Discord, or WhatsApp rather than email — a chat ping gets noticed faster than an inbox that’s already full. See Webhooks.
• Keep New Contacts on In-App only if you don’t want every one landing in your inbox. (Message Reads never emails you in the first place.)

Next Steps #

• Account Settings — Manage your profile and security.

• Webhooks — Route events to Slack, Discord, WhatsApp, or your own systems.
• Phone Numbers — Manage your messaging channels.