Notifications

Zubby keeps you informed about your store and your AI agent through two tabs in the Notifications hub: 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.

Workspace activity tab

The Workspace activity tab 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 merchant 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.

Alerts tab

The Alerts tab (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 severity badge for the ones that matter (Urgent or Action needed), 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. A Settings button in the header opens the delivery preferences described below.

Delivery channels & preferences

Out-of-app delivery is configured in one place: Settings → Notifications (open it from the Settings button on the notifications inbox, or go to /app/<storeId>/settings/notifications). The in-app inbox always records every event; these controls govern the fan-out:

• Slack - post alerts to a channel via an incoming webhook (the URL must be a hooks.slack.com address).
• Email - send alerts to one or more recipient inboxes, comma- or newline-separated.
• Daily email digest - one summary email per day instead of an email per event; in-app, SMS, and push stay real-time.
• SMS - text the configured numbers (E.164 format) for important alerts only. Requires the SMS plan entitlement, a connected Twilio integration and provider fees.
• Browser push - desktop notifications even when the tab is closed. Turn on the channel, then enable it on each device you want notified.

Below the channels sits a Notify me about… card with a per-event switch for each of the fifteen alert types - from conversation escalations, handoff requests, new leads, and ticket activity through low chat ratings, AI-attributed orders, high-value abandoned carts, AI-budget warnings, integration and webhook problems, low stock, low product reviews, and failed catalog syncs. Every event defaults to on; flip off the ones you don’t want fanned out and click Save notifications.

Set up delivery in four steps

1. Open Settings → Notifications and enable the channels your team actually watches - an alert nobody sees is worse than none, because you assume you’re covered.
2. Paste the Slack webhook URL and/or recipient emails, and save.
3. Turn on the daily digest if per-event email is too noisy; urgent channels (in-app, SMS, push) stay real-time.
4. Prune the Notify me about… switches to the events you would act on today - you can re-enable the rest as the store grows.

Gotchas

• The activity feed reflects a recent window of events; it is not a complete historical log. For older incidents, inspect the related feature page or ask support. Detailed audit records are restricted to platform administrators.
• 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.

Investigate an older unresolved alert

The latest-100 display limit is not a retention promise or a full historical export. Follow the related Imports, Billing, Tickets or connection page for current state. If the original alert is no longer visible, ask support with the store ID, approximate time and affected record. Detailed operational audit records are restricted to authorized platform administrators.