Troubleshoot Crisp notification issues across email, browser, desktop, and mobile apps.

Most notification problems come from conversation state, assignment rules, local app permissions, browser focus, battery-saving settings, or stale cache. Check each layer below before assuming the notification was not sent.

Check how Crisp decides who to notify

Crisp avoids flooding every teammate at once. Notifications are sent based on conversation state, assignment, operator availability, and whether the message has already been read.

The message was already read

Crisp does not send a notification for a pending message once at least one operator has read it. If you are testing notifications with a team, make sure nobody opens the conversation before the notification delay has passed.

The conversation is assigned to another agent

If a conversation is assigned to Agent B, Agent A will not receive the same notification. Review your assignment and routing setup if messages are consistently sent to another teammate.

Only one operator is notified first

Crisp sends notifications progressively to avoid duplicate work. For example, if Agent A and Agent B are online while Agent C is offline, Crisp may notify an online agent first, then move to another operator if no one acts.

Check notification settings and permissions

Notification delivery must be enabled both in Crisp and on the device or browser receiving the alert.

What to verify:

• Crisp settings → go to Crisp and open Settings → Account → Notifications
• Mobile permissions → in iOS or Android settings, find Crisp and allow push notifications
• Browser permissions → allow notifications for Crisp in your browser settings
• Do Not Disturb → make sure your desktop, phone, or browser is not silencing notifications

Check mobile delivery issues

Mobile notifications can be delayed or blocked by the operating system, especially when battery-saving features are enabled.

Low battery mode

Many phones reduce push notification activity to save battery. Disable low battery mode temporarily and test again.

Network synchronization

When the Crisp mobile app loads, it synchronizes a phone notification identifier with Crisp. If that synchronization fails because of a network issue, push notifications can stop arriving.

To refresh mobile notification delivery:

1. Restart your phone
2. Open the Crisp app again
3. Make sure the app is connected to a stable network
4. Send a fresh test message

Android reset

If Android notifications still do not arrive, reinstalling the app can reset the local notification state.

Recommended Android reset:

1. Open Android Settings
2. Go to Apps → Crisp
3. Remove the Crisp app
4. Reinstall Crisp from the Play Store
5. Open Crisp and allow notifications again

Check browser, desktop app, and network conditions

If you use the Crisp Desktop App, or a browser setup that cannot receive push notifications reliably, make sure the Inbox tab stays focused. If another Crisp section such as Contacts or Visitors is focused, notification behavior may differ.

VPNs, proxies, and strict company firewalls can also affect notification delivery. Test from another network if notifications fail only from one environment.

Fix stale badges or unread indicators

If you see an unread badge but there are no unread messages, or if the notification count does not update correctly, the browser may be showing outdated cached data.

To refresh stale notification states:

1. Clear your browser cache
2. Refresh the Crisp app page
3. Check whether the unread state updates correctly
4. Test again in a private browser window if needed

If none of these checks apply

If notifications still fail after checking read state, assignments, settings, device permissions, focus, network, and cache, contact Crisp support with the affected operator email, device type, notification type, and a recent conversation example.

Updated on: 03/05/2026