> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.chrisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to solve an issue with notifications

****As a messaging platform, Crisp takes notification delivery issues seriously. Most of the time, these issues can be fixed by following this step-by-step check & fix guide:****

# 1. Has one operator read the message?

Crisp doesn't send notifications for a pending message if that message has been seen (read) by at least 1 operator. If your team is made of multiple operators, ensure nobody reads the message to test if email notifications get delivered.

# 2. Chat is assigned to an other agent

If a chat is assigned to ****agent B****, agent A won't receive notifications. Please check your assign/routing settings:

[https://help.crisp.chat/en/article/how-do-routing-assign-work-qjl2d2/](https://help.crisp.chat/en/article/how-do-routing-assign-work-qjl2d2/)

# 3. Multiple agents are not replying

Crisp is sending notifications to one operator at once to avoid flooding your team and to avoid concurrency.

We deliver notification using priorities, to an online agent first, and offline agents then. For instance:

Agent A is online, Agent B is online, Agent C is offline.

* Crisp delivers a notification to Agent A, but Agent A is not taking action.
* We deliver a notification to Agent B, but Agent B is doing something else
* We finally send the notification to agent C (only if push notifications are enabled)

# 4. Low battery mode

To prevent from killing your battery, most phone providers are slowing notification delivery to prevent battery.

# 5. Network issue

When loading Crisp on a phone, we synchronize your Phone Notification ID (generated by your phone) and push it to Crisp API. It allows then Crisp API to send you notifications.

Sometimes, a network issue might affect this precious data exchange between your phone and our servers, resulting in a notification delivery failure.

In that case, just ****Just reboot your phone and your Crisp APP****

# 6. Notifications are not enabled

You need to ensure that notifications are enabled, both on your Crisp dashboard and in your phone settings.

* On Crisp settings, check it from ****Settings > Account > Notifications****: [https://app.crisp.chat/settings/notifications/](https://app.crisp.chat/settings/notifications/)
* If your phone is running iOS or Android, check Application Settings, then search for Crisp, and ensure push notifications are enabled
* If notifications are enabled in Crisp but you still do not receive them on iPhone or Android, re-check the operating system notification permissions for the Crisp app

# 7. Do Not Disturb Mode

Please ensure that DoNoDisturb mode is not enabled on your Desktop or on your phone, otherwise, notifications will be silent.

# 8. You are using a Proxy or a VPN

From experience, VPNs and proxies can impact the notification delivery.

# 9. Inbox Tab is not focused

If you are using the Crisp Desktop App, or a browser that is not compatible with push notifications, then, you must ensure that the Crisp Inbox tab is focused. For instance, if the MagicMap tab or the Contacts tab is focused, you won't be able to receive notifications.

# 10. I don't receive notifications on Android

I this case we suggest the following procedure:

![Go to the Android Settings, then apps](https://storage.crisp.chat/users/helpdesk/website/-/d/2/3/0/d230ad6831dcf000/e130cfdc-2135-4816-84b9-5edd60_fdv0xr.png)

![Clear the data and the cache](https://storage.crisp.chat/users/helpdesk/website/-/d/7/2/4/d7244c25d31b9000/b51aed31-6994-40a7-88ba-fc80c2_14ih8ul.png)

* Go to the Android settings
* Go to Apps
* Crisp
* Delete the Crisp app
* Reinstall the Crisp App

# 11. Notification badges or unread indicators are out of sync

If you see a red or unread indicator, but there are no unread messages, or notifications are not updating correctly in the interface, the issue may be caused by outdated browser cache data.

In that case:

* Clear your browser cache
* Refresh the Crisp app page
* Check again if the unread state updates correctly

This forces the browser to load the latest data and usually resolves stale notification indicators.

# None if these cases happen to me

In that case, contact us and we'll proceed manual operations to your account to take appropriate actions.

In that case, contact us and we'll proceed manual operations to your account to take appropriate actions.