> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bubblav.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Push & Message Notifications

> Get browser push and in-app bell notifications when visitors message you, request support, submit forms, or hit quota

# Push & Message Notifications

BubblaV can alert you the moment something needs your attention — a visitor message, a support request, a form submission, or a quota threshold. Notifications flow through three channels you control per type:

* **Web** — the in-app notification **bell** (a persistent inbox).
* **Push** — **browser push notifications** on desktop and mobile, even when the tab is in the background.
* **Email** — sent to your account email.

<Note title="Push notifications require a Pro plan">
  Browser push is available on **Pro** and **Custom** plans. The in-app bell inbox is available on every plan.
</Note>

## The notification bell (inbox)

The **bell icon** lives at the bottom of the left sidebar. Click it to open the notification panel.

* **Inbox** shows unread and recent notifications, newest first.
* **Archive** holds notifications you've archived.
* Each row shows an icon, title, a short preview, and a relative timestamp. An **unread dot** marks items you haven't opened.
* **Click a row** to jump straight to its source — for example, the live-support conversation that triggered a message notification.
* **Hover a row** to reveal an **archive** button. Use **Archive all** to clear the inbox, and **Mark all read** to clear the unread badge.
* The **gear icon** (top-right) links to [Account Settings → Notifications](/user-guide/account-settings).

The bell updates in real time: when a new event arrives, the unread badge updates and the row appears at the top without a refresh.

## Enable browser push

Push is **per browser, per device** — you enable it on each browser where you want notifications.

<Steps>
  <Step title="Open Account Settings">
    Go to **Dashboard → Account Settings → Notifications** (or click the gear icon in the bell panel).
  </Step>

  <Step title="Make sure the Push master toggle is on">
    Under **Notification channels**, ensure **Push** is enabled. This is the master switch for all browser push notifications.
  </Step>

  <Step title="Enable push on this browser">
    In the **Browser push status** panel, click **Enable on this browser**. Your browser will ask for permission — choose **Allow**.
  </Step>

  <Step title="Repeat on other devices">
    Open BubblaV in each browser/device where you want push and repeat these steps.
  </Step>
</Steps>

You'll also see a one-time **enable push** prompt in the sidebar. You can dismiss it and enable later from Account Settings.

<Note title="If push is blocked">
  If you previously blocked notifications, the status panel shows **Blocked**. Unblock the site in your browser's site settings, then return to Account Settings and click **Enable on this browser** again.
</Note>

## How message notifications are delivered

When a **visitor sends a message** in live support, BubblaV notifies your team. The owner and all accepted team members can receive the notification across the channels they've each configured:

| Channel   | Behavior                                                                                                                                                              |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Web**   | A row appears in the bell inbox immediately.                                                                                                                          |
| **Push**  | A browser push fires immediately to anyone with push enabled.                                                                                                         |
| **Email** | Sent to the **agent assigned** to the conversation (or falls back per your live-support routing), with a short delay so we don't email you for every rapid follow-up. |

The other notification types work the same way — **support request**, **form submission**, and **quota** — each routed through the channels you pick for that type.

## Configure which notifications you get

Open [Account Settings → Notifications](/user-guide/account-settings) to set up your **channel × type** matrix:

1. **Master channel toggles** — turn off an entire channel (e.g. **Push**) to stop it for every type.
2. **Per type** — for each of Messages, Quota, Support request, and Form submission, check **Web**, **Push**, and/or **Email** independently.
3. **Quota extras** — set an alert **threshold (%)** and an optional **CC email** for quota notifications.

Click **Save preferences**. Preferences are per-user — each team member configures their own.

## Troubleshooting

<AccordionGroup>
  <Accordion title="I enabled push but get no notifications">
    * Confirm the **Push** master toggle is on in Account Settings.
    * Confirm the relevant type has its **Push** checkbox checked.
    * Confirm **Browser push status** shows **Enabled on this browser** (push is per-browser).
    * Check your OS/browser isn't in Do Not Disturb or Focus mode.
  </Accordion>

  <Accordion title="I turned a notification type off but still see old ones">
    Toggles affect **future** notifications. Existing items remain in your bell inbox until you read or archive them.
  </Accordion>

  <Accordion title="Email notifications for messages go to the wrong agent">
    Message emails follow your **live-support assignment** — they're sent to the agent assigned to the conversation, not the whole team. See [Email Notifications](/user-guide/live-support/email-notifications).
  </Accordion>

  <Accordion title="The bell shows no badge but I have notifications">
    The badge reflects **unread** notifications. Click the bell and use **Mark all read**, or open each row, to clear it.
  </Accordion>
</AccordionGroup>