Alerts: who gets notified and when

Alerts keep you on top of what InboxAgent does without watching the app. Set them under Notifications in the sidebar (admins only). A new workspace starts with all five default alerts on, going to the person who created the workspace.

Who gets alerted

The “Send alerts to” bar at the top lists your recipients. Everyone here receives every default alert — by email and in the app’s bell. Add a colleague’s address, click Add person, then Save. Remove someone by clicking the × on their chip and saving.

(One side effect worth knowing: saving the recipient bar resets all five default alerts to “email + in-app” delivery. That’s the intended setup for defaults; per-channel customization belongs in custom alerts.)

Alerting a mailbox you monitor

If a recipient is also a mailbox InboxAgent monitors, we flag it with a note when you save. This is allowed, not blocked. Every alert InboxAgent sends is tagged so it can’t be re-processed or set off a loop, even when it lands back in a monitored inbox. The only cost is noise: that inbox gets a copy of the alert. Keep it if that is what you want, or point the alert at a different address.

The five default alerts — “Email me when…”

• “a new lead is detected” — InboxAgent decided an email is a sales lead.
• “a support request comes in” — a support ticket decision.
• “something needs your review” — an email joined the Manual review queue.
• “a mailbox loses connection” — a mailbox needs reconnecting (what to do).
• “a lead or ticket can’t reach your CRM or helpdesk” — an outbound push failed (Delivery failures).

Each is a simple on/off switch. Turning one off stops both the email and the in-app notification for that event; turn it back on any time.

Three honest mechanics

• You get the alert when a lead or ticket is detected. Either way it reaches a board of its own — Leads or Follow-ups — so the alert is your cue to go and work it. If you have a CRM or helpdesk connected and its push then fails, the alert is suppressed (so you’re never told a record was created when it wasn’t) and the failure shows on Delivery failures with its own “can’t reach your CRM or helpdesk” alert. Review and mailbox alerts fire when that event happens. See decisions explained.
• At most one email per email. However many times a message is re-processed, each alert rule emails you about it at most once — no storms.
• Recipients share one email. Everyone on the recipient list is on the same To line of alert emails, so they can see who else was notified.

When the defaults aren’t enough

Want an alert for just one mailbox, only for priority senders, with your own wording, or delivered in-app only? That’s a custom alert.