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

# Push notifications

> Let the people who chat with you know when your team, a bot or an AI agent replies while they are away from the chat.

Someone asks a question in your app and closes it. Or they switch browser tabs. When the answer arrives, Talqui can let them know, so the conversation doesn't die waiting.

## How it works

1. Your team, a chatbot, an AI agent or a workflow replies in a WebChat conversation.
2. Talqui waits about **20 seconds**. If the person is looking at the chat by then, nothing is sent.
3. Otherwise Talqui notifies them, the way you chose for that WebChat connection.
4. At most **one notification per conversation every 5 minutes**, and each one replaces the previous one on the device instead of piling up.

"Looking at the chat" means the chat is open and on screen: the widget open in a visible tab, the full-screen link in a visible tab, or the SDK chat visible in your app. A chat left open in a background tab or in an app sent to the background counts as away.

## Choose how to notify

In [app.talqui.chat](https://app.talqui.chat), open **Plugins → WebChat**, open the connection and go to the **Notificações** (Notifications) tab. Under **Como avisar** (How to notify), pick one mode:

| Mode | What Talqui does | You set up |
| - | - | - |
| **Desligado** (Off) — default | Nothing. The person sees the reply when they come back. | Nothing |
| **Pela Talqui** (Through Talqui) | Sends the push itself: through **your** Firebase project to your app, and as a browser notification to people using the chat link. | A Firebase service account, and two lines in your app |
| **Pelo meu sistema (webhook)** (Through my system) | Calls your backend with a signed request for each reply. You notify the person however you like: your own push, email, SMS. | An HTTPS endpoint |

Only one mode is active per connection. That is on purpose: with Talqui and your backend both sending, the same reply would notify the person twice.

> [card] [Mobile apps](https://docs.talqui.chat/guides/push-notifications/mobile-apps.md)
>
> Through Talqui, with your Firebase project.

> [card] [Browser](https://docs.talqui.chat/guides/push-notifications/browser.md)
>
> Through Talqui, for people on the chat link.

> [card] [Webhook](https://docs.talqui.chat/guides/push-notifications/webhook.md)
>
> Your backend receives each reply.

## What the notification says

* **Title:** the name of the operator who replied, or "Nova mensagem" for bots and automations.
* **Text:** the beginning of the reply (up to 140 characters), or "Enviou uma imagem", "Enviou um áudio"… for media.

To keep replies off locked screens, turn on **Esconder o conteúdo da mensagem no aviso** (Hide the message content in the notification). The text becomes "Você recebeu uma nova mensagem" and the webhook gets no preview.

## Last deliveries

The **Últimos avisos** (Last deliveries) table on the same tab lists every attempt of the last 7 days: when, through which channel, who replied and whether it was delivered, retried or failed. Message content is never stored there.

## Good to know

* Who gets notified: replies from people, chatbots, AI agents and workflows. Never the person's own messages, internal notes or system events.
* Only WebChat conversations (website, chat link and apps). Other channels such as WhatsApp and Instagram already notify through their own apps.
* Blocked contacts are never notified.
* Inside your app, the chat never shows browser notifications: the app's own push takes care of it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.