Notification Settings

Summary

Notification Settings lets each staff member configure which notifications they receive and how they are delivered. Options include in-app toasts, browser push notifications, and a daily email digest. Each staff member controls their own preferences. Settings are per-organisation, so users belonging to multiple organisations have independent preferences for each.

Prerequisites

• You are signed in to Torqueflow.
• Any authenticated staff member can access their own notification settings (no special capability required).

Steps

Accessing notification settings

1. Click Settings in the sidebar.
2. Click Notification Settings. The page title reads Notification Settings with the subtitle “Configure how and when you receive notifications”.

Configuring notification types

The Notification Preferences card has five toggle switches under the “Notification Types” heading:

1. New Messages - toggle on to be notified when a customer sends an inbound message. Default: on.
2. Approval Queue - toggle on to be notified when a technician message needs approval. Default: on.
3. Unread Escalation - toggle on to be notified when a message has been unread past the threshold. Default: on.
4. Delivery Failures - toggle on to be notified when a WhatsApp message fails to deliver. Default: on.
5. Parts Received - toggle on to be notified when a scanned delivery note completes the parts list of one or more jobs. You get one coalesced notification per delivery, naming every job now ready to proceed. Default: on. This toggle is visible to anyone with workshop access.

Setting the escalation threshold

1. Under the “Escalation Configuration” heading, set the Escalation Threshold (minutes) field.
2. This controls how long a message can remain unread before managers are alerted. Range: 5 to 1440 minutes (24 hours). Default: 30 minutes.

Configuring delivery channels

Under the “Delivery Channels” heading:

1. Push Notifications - toggle on to receive browser push notifications even when Torqueflow is closed. When you toggle this on, the system registers a push subscription with the server.

   • A status indicator below the toggle shows the current state:
     • Subscribed (green tick) - push is active.
     • Not subscribed (grey cross) - push is inactive.
     • Permission denied (amber warning) - browser permission was denied. Change this in your browser settings.
     • Not supported (grey cross) - your browser does not support push notifications.
   • When subscribed, a Send Test button appears. Click it to send a test push notification to verify the setup.

2. Email Digest - toggle on to receive a daily summary of conversation activity each morning.

Granting browser notification permission

1. Under the “Browser Permission” heading, click Request Permission.
2. Your browser shows a permission prompt. Click Allow.
3. If you previously denied permission, you must change this in your browser’s site settings (the system cannot re-prompt after a denial).

Saving preferences

1. Click Save Preferences at the bottom of the form.
2. A success toast confirms “Notification preferences saved”.

Expected Outcome

• Notification type toggles control which events generate notifications for your account.
• Push notifications arrive even when the Torqueflow tab is in the background or closed (if the browser is open).
• In-app toast notifications appear in the bottom-right corner when you have a Torqueflow tab open.
• The escalation threshold determines the delay before unread messages trigger escalation alerts.
• The email digest sends a morning summary of conversation activity.
• Changes apply only to the current organisation.

Troubleshooting

Problem	Cause	Fix
Push toggle shows “Not supported”	Your browser does not support the Push API (e.g. older browsers, some mobile browsers)	Use a modern browser such as Chrome, Edge, or Firefox
Push toggle shows “Permission denied”	You previously denied the browser notification permission	Open your browser’s site settings for Torqueflow and change the notification permission to “Allow”, then reload the page
Test notification not received	No active push subscription found	Toggle push notifications off and back on, then try again
Test notification shows warning “No active push subscriptions found”	The push subscription record is missing on the server	Toggle push notifications off and back on to re-register
”Invalid preference data” error on save	A value is out of range (e.g. escalation threshold below 5 or above 1440)	Check the escalation threshold is between 5 and 1440 minutes
Notification preferences not loading	Server error or network issue	Refresh the page. If the problem persists, try signing out and back in
Push notifications arrive twice	Both the in-page listener and service worker are active	This should not happen by design. If it does, clear the service worker from your browser’s developer tools and reload
Save button is greyed out	A push subscribe or unsubscribe operation is in progress	Wait for the push toggle to finish, then click Save

Notes

• In-app toasts use a real-time channel and appear instantly when a Torqueflow tab is open and focused.
• Browser push notifications are delivered via a service worker (sw.js) and work even when the tab is in the background or closed. The service worker sends a heartbeat every 30 seconds so the server can deduplicate push and in-app notifications.
• The “How Notifications Work” info card at the bottom of the page explains In-App Toasts, Browser Notifications, Escalation Threshold, and Per-Organisation settings.
• Each notification includes an action button that navigates directly to the relevant item (e.g. the conversation).
• Escalation threshold validation enforces a minimum of 5 minutes and a maximum of 1440 minutes (24 hours) on both client and server.