Open Notifications to inspect User Notification, Notification Subscription, Notification Delivery Attempt and WhatsApp Staff Notification Delivery. These records help explain whether a notification was created, dispatched or read.
Trace a push notification
- Find the User Notification for the intended staff member and event. Check its creation time, delivery state and engagement/read state.
- Inspect its Delivery Attempts for status and error.
- Check the staff member's Notification Subscription: active setting, permission state, registration/last-seen time and recent success or failure.
- Ask the employee to check notification permission on their device using the Staff App notification guide.
A notification record and a device subscription are separate prerequisites. A successfully submitted push is not proof it appeared on the device or was read. Subscription tokens and device identifiers are technical routing data; do not copy them into support messages or shared screenshots.
Send a test to your own account
In User Notification, Send Test Notification creates a test for the currently signed-in staff account. The background service dispatches it. The creation message confirms queuing, not delivery; inspect the attempt and device result afterward. The action reports an error if the service or current staff identity cannot be resolved.
WhatsApp Staff Notification Delivery records the separate WhatsApp delivery path. Check the relevant channel instead of assuming a push attempt explains a WhatsApp failure. See messaging for templates and provider-managed messages.