Notifications

Zubby keeps you informed about your store and your AI agent through two complementary surfaces: a derived activity feed that summarizes recent events across the platform, and a notifications inbox of discrete, persisted alerts you can work through and mark read. This page explains what each shows, how items are categorized, and where the delivery settings live.

Activity feed

The Notifications page is a live triage view assembled from what actually happened in your store — recent audit events, catalog and embedding sync jobs, revenue events, knowledge-document changes, and shopper handoffs. It is not a static log; it is rebuilt from those sources each time you open it.

Four summary tiles sit at the top: total events, unread, failed syncs, and billing alerts. Every item is typed, and the type sets its icon and color:

• Success — something completed cleanly.
• Revenue — checkout conversions, recovery wins, and billing-related events.
• Alert — import failures, broken handoffs, and other items that can block revenue or trust.
• Info — everything else worth surfacing.

Triage tabs

The feed groups items so you fix the important things first, not just the newest:

• Needs attention — three columns for operational alerts (routes to Imports), revenue and billing (routes to Analytics), and human follow-up (routes to Handoffs).
• Knowledge and training — recent document changes that affect how the AI answers, plus operator recommendations that tell you what to prioritize given the current mix of alerts, knowledge updates, and waiting handoffs.

Operational shortcuts at the top deep-link to the page that usually resolves a class of alert — Imports, Settings, Handoffs, Support — so notifications act as a launchpad rather than a dead-end inbox.

Actions

• Filter the list by All or Unread.
• Mark as read per item, or Mark all read.
• Dismiss an item to remove it from the feed.
• Open related page jumps to the dashboard tab that addresses the notification.

Notifications inbox

The Notifications inbox (the persisted list) holds discrete, durable alerts written when something needs your eyes: escalations, new leads, sync issues, and billing events. Unlike the activity feed, these are stored records, ordered newest-first, and capped at the most recent 100.

Each row shows a title, a kind badge (the machine category of the event), a timestamp, an optional body, and — when relevant — an Open link to the related page. Unread rows are highlighted. Clear them with per-row mark read or the Mark all read action in the header, which also shows an unread count.

Delivery channels

Both surfaces above are in-app. Out-of-app delivery is configured on the feature that owns each event, not on a single global preferences screen:

• Handoff & escalation emails — when the AI escalates a conversation to a human, notification email goes to your team. Configure recipients and routing under the inbox settings — see Human handoff.
• Weekly review email — the Monday performance digest is delivered by email. See Analytics & weekly review.
• Recovery and journey messages — shopper-facing emails and SMS are governed by Recovery, not by these notification surfaces.

Gotchas

• The activity feed reflects a recent window of events; it is not a complete historical log. For full history, use the relevant export under Reports or the audit log.
• Marking an item read in the feed does not delete the underlying event — it only changes its read state in the view.
• The inbox is capped at 100 rows; older alerts age out of the list even if unread.

Related

• Human handoff — where escalation alerts originate.
• Inbox — working conversations and SLAs.
• Analytics & weekly review — the emailed weekly digest.