Aymar Agents’s notifications live across three different screens — the bell, per-channel owners, and Settings → Notifications — because each one configures a different piece of the same system. This page ties them together: what triggers each type of notification, which channels it can reach you through, and who decides what.
The three channels
Section titled “The three channels”| Channel | Can be turned off | Who controls it |
|---|---|---|
| Bell | No — always on. | Nobody: it’s the minimum guarantee that no notification gets lost. |
| Yes, per person. | Each person, in their own preferences. | |
| Yes, per person — and requires the tenant’s own WhatsApp channel connected with an approved internal template. | Each person turns their own toggle on; the tenant needs the channel and template ready, or delivery gets silently skipped (the bell and email, if active, keep notifying you all the same). |
What triggers a notification
Section titled “What triggers a notification”- A hand-off to a human — a conversation the AI passes to a person.
- A ticket assigned to you — the notification takes you straight to Tickets with that ticket already open.
- A channel alert — when a conversation on a channel escalates, it notifies that channel’s owners (configured on the channel’s own card); if a channel has nobody marked as owner, the notification goes to the whole active team — an escalation is never lost for lack of configured owners.
- A consumption or plan alert — for example, when your agency’s AI usage reaches your contracted plan’s limit.
- A new qualified lead — if your agency has that notice turned on (see below).
- A tenant-wide critical alert — through the channels (Email and/or WhatsApp) your administrator marked for the whole agency.
Where each thing is configured
Section titled “Where each thing is configured”- The bell itself isn’t configured — it’s the bell-shaped icon in the top bar, with a counter of unread notifications. Everything on this page eventually lands there, always.
- Who owns each channel, on the channel’s own card (Channels): check the boxes for the team members you want to receive that SPECIFIC channel’s escalation notice — you can pick several, or leave it with nobody (then it notifies the whole team). See Channels.
- Agency-wide alerts, under Settings → Notifications (Admin role): the email summary’s frequency (daily, weekly or off), whether every new qualified lead triggers a notice, and which channels (Email and/or WhatsApp) the tenant’s critical alerts go through.
- Your own personal preferences, on the same Settings → Notifications screen, under “How you want to receive alerts” — available to any role, saved instantly with no separate “Save” button: turn email and WhatsApp on or off for yourself. The bell doesn’t show up as a toggle because it can’t be turned off.
What to configure
Section titled “What to configure”- Channel owners: optional — with none marked, it notifies the whole team.
- Agency email summary: daily, weekly or off.
- New-lead notice: on or off for the whole agency.
- Channels for tenant-wide critical alerts: Email and/or WhatsApp.
- Your own preferences: email and WhatsApp, each person their own.
Limits and honesty
Section titled “Limits and honesty”- The bell can never be turned off — it’s the only channel that guarantees a notification always reaches someone.
- WhatsApp delivery needs two things at once: your own toggle turned on and a phone number saved on your profile, and your agency having a WhatsApp channel connected with an approved internal template. If either is missing, delivery gets silently skipped — it never fails visibly, it simply doesn’t arrive through that channel and you still get it through whichever ones you do have active.
- With no owners assigned to a channel, the escalation notice goes to the whole active team — that’s not a bug, it’s the by-design behavior so no escalation ever gets lost.
See also
Section titled “See also”- Conversations — the bell and the rest of the inbox.
- Channels — channel owners and their alerts.
- Settings and integrations — the full notifications procedure, with screenshots.
