If not working on mobile, try reinstalling the PWA, deleting it, installing again, and restarting.
If not working on mobile, try reinstalling the PWA, deleting it, installing again, and restarting.
Yes, ensure you allow notifications in browser settings. In Chrome, check under Privacy and Security > Site settings > Notifications.
Notifications are sent only if the last agent in the conversation is offline and Human takeover is active.
No, notifications are not supported on iPhone and iOS devices.
Agents with no assigned department receive notifications for conversations not assigned to any department.
Notifications are sent only to agents assigned to that department if a user conversation is assigned to a department.
If Routing is active, only the assigned agent receives notifications. If Queue is active, only the assigned agent gets notifications; not for queued user messages.
No, Push notifications are not supported in the WordPress admin area. Access the Chat.RPAiX admin area directly for notifications.
No, if the Dialogflow App’s Human takeover is active and the chatbot knows the answer, no Push notifications are sent.
Yes, when a user sends their first message, Push notifications are sent to all validated agents. Subsequent notifications are sent only to the last agent in the conversation.
When an agent clicks a Push notification, the admin area in Chat.RPAiX opens with the relevant conversation selected. No new tab opens if the admin area is already active.
No, a browser must be running to receive Push notifications.
If they’re not working, disable them and try again. Remember, they require an active browser process.
On Android and mobile devices, if Desktop notifications aren’t working, use Push notifications.
When Push notifications are active, they replace Desktop notifications.
Desktop browsers need to be running to receive push messages.
Clicking the notification opens the last visited page automatically, with the chat also open.
Push notifications work only for full HTTPS websites. They may work on localhost for development.
Push notifications are supported on Mac, Windows, and Android devices. They are not supported on iPhone and iOS devices.
Based on the latest informration, Pusher is free for up to 1000 concurrent subscribers. Depending on your site traffic, you might need a paid plan for user Push notifications.
Download the service worker file, upload it to your site, and set the Service Worker URL in Chat.RPAiX settings.
Visit https://dashboard.pusher.com/accounts/sign_up to create a Pusher account.
From your dashboard, choose Beams and follow the steps to get the Instance ID and Primary key. Enter them in Chat.RPAiX settings.
Chat.RPAiX uses Pusher for Push notifications. It’s free to use for admin notifications and for up to 2000 users/devices when sending notifications to users.
Push notifications are always active, visible until closed, and are sent from a server. They require an external service. Chat.RPAiX uses Pusher for this purpose.
Push notifications come from a server and work even when your device is offline or Chat.RPAiX is not open. Desktop notifications are client-requested and may not be persistent.