Notifications, push, and the notification center

Closr has two places notifications show up: the bell in the topbar (the in-app notification center) and your device's native push (desktop or mobile, browser-based). Same events drive both. Push delivery isn't always reliable (DND mode, expired tokens, closed PWA), so the bell holds the history as the fallback. You'll see every notification there either way.

What triggers a notification

• •**New inbound reply** (email or SMS) on a thread assigned to you, or unassigned on your team
• •**Hot lead activity:** a contact you're working hits your tracked-domain site 3+ times in a week, or a high-intent page like a pricing page
• •**Deal stage change:** a deal you own advances or stalls (e.g., conditions auto-waived, offer accepted)
• •**Condition deadline alerts:** a financing or inspection condition is within 24 hours of its deadline
• •**Automation `NOTIFY_AGENT` actions:** anything you've set up via chat with "text me when X" or "ping me if Y" runs through this same pipeline
• •**Campaign + sequence events:** bounces, completions, replies on a drip

When you set up an automation that says "when a lead replies, text me", that "text me" is wired through the same push + notification-center pipeline. The bell, your phone, your desktop: all three light up.

Enabling push

Push works on both desktop and the web app on mobile. To turn it on:

1. 1Go to Settings → Notifications.
2. 2Click "Enable push notifications." Your browser will ask for permission.
3. 3Allow. That's it.

Behind the scenes Closr registers a Web Push subscription (endpoint + p256dh + auth keys) against your user. If you ever change browsers or clear cookies, you'll need to re-enable. Closr tracks subscriptions per endpoint so multiple devices work.

The in-app notification center

There's a bell icon in the topbar. The badge count is your unread total. Click to open:

• •Newest notifications at the top
• •Each row shows title, body, time, channel
• •Click any row to mark-as-read and jump to the linked surface (a contact card, a deal thread, etc.)
• •"Mark all read" at the top clears the badge

The bell uses realtime: when a new notification lands, the badge updates within ~500ms via Supabase Realtime broadcast (not 60-second polling). There's a 5-minute safety-net poll in case the realtime channel drops.

Silencing noisy categories

If a particular automation or category is firing too often, you have three options:

1. 1In chat, say "stop notifying me about new web visitors" or "mute hot-lead alerts for this week." Cody updates the underlying automation.
2. 2In Settings → Notifications, toggle individual categories off (web activity, deal-stage changes, condition deadlines, etc.).
3. 3For a specific automation: open it from the automations list and disable.

Browser-level Do-Not-Disturb (focus modes on macOS, focus modes on iOS) suppresses push delivery, but the bell still records the event so you don't lose it.

Mobile native app

A separate native app is in active development (Expo React Native, at `~/closr-mobile`, Bearer-token auth). It will deliver native push via APNS / FCM and is faster than the web app on mobile. Until then, the web app is responsive and Web Push covers mobile if you install it as a PWA. Same notifications, slightly different delivery plumbing.

Where to go next

• •`inbox`: triage queue for inbound that's already landed
• •`automations`: building "text me when X" rules in chat
• •`web-tracker-install`: what triggers hot-lead notifications