Reporting & Analytics
Notifications & Alerts Hub
See the notice. Follow the work.
An in-app inbox, notification preferences, message templates and delivery records to help teams follow up the work that needs attention.
Residential care · Home care
In practice
The work behind notifications & alerts hub.
Review the notifications available for the program you are currently viewing and follow linked notices to their records. Configure available category and channel preferences, and use the communications log to investigate delivery status. Reading a notice and resolving the underlying work are separate actions.
Teams need to distinguish an unread notice, a failed delivery and an unresolved task. Keeping those states clear helps the responsible person decide what to check next, without treating an email as proof that the work is complete.
In-app inbox
Open the notification bell to review grouped notices and unread counts. Follow a linked notice to its underlying record, where available.
Read status
Opening a notice marks it read; the inbox also offers Mark all read. These controls manage the inbox and do not resolve the underlying incident, task or reporting obligation.
Category preferences
Choose the available in-app, email, SMS and push preferences by notification category. Incident, clinical and account categories keep their in-app switch locked on.
Channel availability
Email, SMS and push depend on the matching integration being enabled. Mandatory notification rules remain separate from ordinary category preferences; confirm the rules and recipients that apply to your organisation.
Message templates
Create, preview and edit notification templates, with channel and event-type filters. A template defines message content; it does not confirm that a message was delivered.
Communications log
Filter recorded communications by channel, status, event type or recipient. Inspect delivery states including pending, sent, delivered, read, failed and bounced. Export the log as CSV or open a delivery record to review its failure reason, retry count and template version.
The wider workflow
Where notifications & alerts hub connects.
Care, workforce, finance and governance belong in the same evaluation. Start with the workflow under pressure and agree how the surrounding records will be used.
A workflow illustration showing the broader operating context.
Explore the product tour
Evaluation
What to inspect with your team.
Bring a representative notifications & alerts hub scenario and use these questions to guide your demonstration.
Book a demo with this scenario- Walk through in-app inbox using a representative example.
- Check the permissions and review steps for read status.
- Inspect the records and outputs available for category preferences.
Requirements and responsibilities
The requirements behind the workflow.
Review how these requirements apply to your services and the responsibilities your team retains.
Reference area: Part 10
Response ownership
Agree who monitors each workflow and acts on unresolved items. Notification settings do not transfer the provider’s responsibility for meeting an applicable deadline.
Delivery evidence
Check the recorded delivery state and follow up failures. A sent message is not proof that its recipient read it or completed the required action.
Workflow context
Review the underlying record and its deadline or action status. An inbox read marker is separate from the evidence of resolution or external reporting.
Related workflows.
Explore the records and responsibilities that connect notifications & alerts hub with the wider platform.
SIRS & Incidents
Review incident deadlines and follow-up work in the incident workflow; notification delivery is a separate state.
Workforce Compliance
Follow workforce notices back to the relevant screening or certification records where linked.
Clinical Care
Review clinical notices in the context of the client record and the team’s response process.
Questions about notifications & alerts hub.
Does marking a notification read resolve the underlying task?
No. Read status manages the inbox. Review and complete the underlying incident, task or reporting workflow separately, and retain the required evidence of action.
Can users control how they receive notifications?
Users can adjust the available category and channel preferences. Incident, clinical and account categories keep in-app delivery switched on. Other channels depend on enabled integrations, and mandatory notification rules are separate. Confirm the settings that apply to your role and workflows.
How can we investigate a message that did not arrive?
Use the communications log to review the recipient, channel and recorded status, including failed or bounced messages. Check configuration and follow up through your team’s process. A sent status does not guarantee receipt or action.
See Notifications & Alerts Hub in action.
Bring a notifications & alerts hub scenario. We’ll walk through the relevant records, review steps and scope for your organisation.