Notifications that arrive, and open the record
A badge that only appears while the tab is open is not a notification. Certainty HelpDesk sends real web push, falls back to email when nobody has push on, and every notification, on every route, opens the record it is about.
In-app, push, and email when push is not there
The bell carries the recent list and an unread count, and the notifications page holds the whole history, grouped by day, with mark-one-read, mark-all-read and paging backwards until there is nothing left.
Push is what reaches somebody when the app is closed, and it is off until they ask for it. While push is not active on any of a client's devices, status changes and new comments on their requests are emailed instead. The moment one device is receiving push, the emails stop, so nobody is told the same thing twice.
- The email fallback is automatic, and Email updates in Settings turns it off for good
- That preference belongs to the account, so it holds in every browser they sign in from
- The unread count also rides on the menu item, so waiting work is visible without a click
One notification per room, updated in place
A busy conversation used to stack one notification per line. Now each room keeps a single notification that updates in place with the latest sender and message, so ten messages in a room is one thing to look at rather than ten.
Opening any notification goes straight to what it is about: the item, the conversation, or the access request queue. That holds from the bell, from a toast and from the operating system's own notification.
- Notifications arrive faster and land on the right page
- Coming back to a backgrounded tab catches the bell up straight away
- An optional chime, per person, in Settings
Tas: can you check the export again?
One notification for the room, updated in place
Told because it concerns you, not because you exist
Sorting a request notifies the project's members that the work exists, with internal records reaching internal people only. Task notifications go to the people assigned and nobody else, so being on a project does not mean reading everyone else's task traffic. Assigning yourself still notifies you, which is what puts the work in your own list.
Being added to a project tells you so. An access request reaches everyone who can decide it, in the app, by push and by email, and the person who asked hears back the moment it is decided. Budget alerts at 80, 90 and 100 percent go to recipients configured per threshold, and project leads are nudged on Tuesday afternoon and Wednesday morning when a project still has no weekly update.
- Internal records are left out of the notification fan out entirely
- On iPhone and iPad the app has to be installed to the Home Screen for push to work
- A Send test notification button exercises the real delivery path, not a fake toast
Delivery, proved before you rely on it
The nudge before it starts, and a digest instead of a pile
Anything on the calendar with a start time reminds the people on it about fifteen minutes ahead, and again on the day: a notification for whoever has push, an email for whoever does not, and never held back, because a reminder at ten for a meeting at nine is no reminder. Clients named on a meeting get a proper email invitation carrying the day, the time in Malaysia time and a join button, and the same reminder before it starts.
Chat deliberately went the other way. A new message is a toast, a push and a red count on the sidebar item, and it never lands on the notifications page, because a page of individual messages is a page nobody reads. Where push is off on every device, one email per conversation every half hour at most. Mentions still reach the bell, because a mention is addressed to you.
- An event with nobody named on it nudges the whole team, by notification only
- Whoever made a change to an event is never notified about their own
Before it starts
Quiet evenings, for whoever asks for them
Once push is on, it arrives when it happens, at any hour, because that is what a notification is for. Anybody who would rather not hear from work in the evening switches on Office hours only in Settings, in the team workspace or the client portal: pushes raised outside 10:00 AM to 7:00 PM Singapore time wait, and arrive at 10:00 AM.
Some things are no use at ten the next morning, so they skip the hold for everybody: meeting invites, the reminder before a meeting starts, reminders people set themselves, the 6:30 PM nudge to check out, a project's missing weekly update and a credential about to expire. Whatever is held, the notification itself lands in the app straight away; only the buzz on the phone waits.
- Off by default, and a choice each person makes for themselves
- Held pushes are delivered at ten, never dropped
- Email and the bell are not held: the switch is about the phone
Settings · notifications
The things teams ask about this
Does push really work on an iPhone?
Yes, with one condition: iOS only delivers push to installed apps, so the app has to be added to the Home Screen from Safari's share menu and opened from that icon first. After that the switch in Settings works the way it does anywhere else. The install prompt inside the app walks through the three steps if somebody needs them.
How do I prove notifications work before something urgent depends on it?
Send test notification, next to the switch in Settings. It exercises the whole delivery chain rather than faking a toast in the page, so an arrival is proof that the real thing will arrive. Worth doing on each device, because push belongs to the device and the browser rather than to the account.
What happens if somebody never turns push on?
For a client, the updates arrive by email instead, automatically, while push is not active on any of their devices. That is the default rather than something to configure, and it switches itself off as soon as one device is receiving push. Email updates in Settings turns it off permanently, and that choice belongs to the account rather than the browser.
Can I stop work notifications reaching my phone in the evening?
Yes, if you want to. Office hours only in Settings holds pushes raised outside 10:00 AM to 7:00 PM Singapore time and delivers them at ten. It is off unless you turn it on, so by default a push arrives whenever it happens. Meeting invites, the reminder before a meeting starts and reminders you set still arrive at once, and the notification is in the app straight away whichever way the switch is set.
Will turning notifications on mean reading everyone else's work?
No. Task notifications go only to the people assigned, sorting a request tells the project's members that work exists, and internal records are left out of the fan out entirely, so nobody is pinged about something they cannot open. Budget alerts reach only the recipients configured for that threshold.
See it against your own work
Thirty minutes on a call, one of your real client projects on the screen, and an honest answer about whether this part of the product earns its place in how you work.
partnerships@dhcertainty.com