> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-text-agents/inbox/desktop-alerts.md).

# Desktop alerts

Get a desktop alert when a chat is assigned to you or a customer replies on WhatsApp in one of your chats, even when Dapta isn't the tab in front.

Inbox can alert you on your desktop, so you don't miss a customer while you work in another tab. Alerts are set per browser: turn them on in each browser where you answer chats.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6a7ad2f8da11c58e0c8f412b358844e81aa65c32%2Ftext-agents-inbox-desktop-alerts.mp4?alt=media>" %}

{% file src="/files/eVWH9GFpKs5ORwTriuwi" %}

***

## When you get an alert

| You get an alert when                                    | Good to know                                                                                                                            |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| A chat is assigned to you                                | Not when you assign it to yourself.                                                                                                     |
| A customer replies on WhatsApp in a chat assigned to you | Only while a person handles the chat. While the AI is answering it, nobody gets an alert. Replies in website chats don't send an alert. |

Click an alert and Dapta opens that chat in Inbox. If Dapta is already open, it switches that tab to the chat, so a reply you were writing elsewhere isn't lost.

***

## Turn alerts on

**Step 1:** Open **Text Agents → Inbox**.

The first time you open Inbox in a browser, a banner at the top of the list asks: **Don't miss a customer**.

***

**Step 2:** Click **Turn on alerts**, then click **Allow** when your browser asks to show notifications.

The banner closes and a bell appears at the top right of the list.

If you click **Not now**, the banner hides for 14 days and the bell appears instead. You can turn alerts on from the bell at any time.

***

**Step 3:** Click the bell to check.

The menu shows whether alerts are on, the **Alerts in this browser** switch, and what you're alerted about.

***

## Read the bell

| The bell              | What it means                                                    |
| --------------------- | ---------------------------------------------------------------- |
| A plain bell          | Alerts are on in this browser.                                   |
| A crossed-out bell    | Alerts are off. Click it and turn on **Alerts in this browser**. |
| An amber bell         | Your browser blocks notifications from Dapta. See below.         |
| No bell and no banner | This browser can't show desktop alerts. Use another browser.     |

To stop alerts, click the bell and turn off **Alerts in this browser**. It only changes this browser.

***

## Alerts follow you, not the tab

* **One workspace per browser.** Alerts come from the workspace where you last opened Inbox in that browser. If you work in two workspaces, open Inbox in the one you want alerts from.
* **Keep the browser open.** The Dapta tab can be in the background, but alerts reach you only while your browser runs.
* **Signing out turns them off** for that browser. After you sign back in, turn them on again from the bell.

***

## If alerts don't arrive

| What you see                              | What to do                                                                                                                                                                                                                                                                    |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| An amber bell, or **Blocked** in its menu | Your browser blocks Dapta. Click the lock icon in the address bar → **Notifications** → **Allow**, reload the page and turn on **Alerts in this browser**.                                                                                                                    |
| **Failed** in the bell's menu             | Desktop alerts work in Chrome, Edge, Firefox and Safari; other browsers can fail here. In one of those, turn **Alerts in this browser** off and on again, and reload the page if it still fails.                                                                              |
| The bell is on, but nothing arrives       | Check that the chat is assigned to you and that a person is handling it. Replies in website chats never send an alert; only WhatsApp replies do. Then check that your computer's notification settings, such as Do Not Disturb or Focus, let your browser show notifications. |
| Alerts from the wrong workspace           | Open Inbox in the workspace you want alerts from.                                                                                                                                                                                                                             |

{% content-ref url="/pages/Yd8Dr1GnzSTVXV8kBdd6" %}
[Inbox](/ai-text-agents/inbox.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/ai-text-agents/inbox/desktop-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
