The challenge
Safety-critical messages get lost among routine alerts, or never reach site staff who do not check e-mail. Each module sending its own messages makes it impossible to control or audit who was told what.
Platform & governance Pilot
Notifications & Escalation Engine
The right people told, on the right channel, in their language — with mandatory rules.
A single notification engine turns events from every module into messages for the right people through in-app, e-mail, WhatsApp, SMS and web push channels where configured. Clients set policy and mandatory rules, people choose their channels and can receive a daily summary, and every delivery is logged.
Pilot · Modules marked Pilot are available to selected customers while they are completed. Capabilities depend on the configuration agreed for each deployment.
Capability map
19 capabilities- Alerts12
- Integration3
- Governance4
6 workflow stagesMobile & field
Overview
Why Notifications & Escalation Engine matters
How Green Codes Pro helps
Events pass through the client's policy, permissions, channel availability, mandatory rules and personal preferences before one deduplicated delivery per person and channel is queued with retries. Templates are bilingual, critical and account messages are never held, and workflow rules drive assignment, reminder, overdue and escalation messages.
How it works
From first entry to closure
The 6 stages a record moves through, from the first entry to a verified close.
- 01
Stage 1
Event occurs
- 02
Stage 2
Policy and permission check
- 03
Stage 3
Choose channels
- 04
Stage 4
Deliver or hold for summary
- 05
Stage 5
Remind and escalate
- 06
Stage 6
Log delivery
Capabilities
What you can do
19 documented capabilities, each verified against the product.
19 capabilities
- PilotAlerts
One notification engine
Events from every module pass through client policy, permissions, channel availability, mandatory rules and personal choice, with one deduplicated delivery per person and channel and automatic retries.
- PilotAlerts
In-app, e-mail, WhatsApp, SMS and web push
Messages go out through in-app notifications and e-mail, and through WhatsApp, SMS and web push where those providers are configured.
- PilotAlerts
Notification Center
An in-app bell and inbox with notification history.
- Alerts
Personal notification preferences
Each person chooses channels per type of notification within what the client allows.
- Governance
Mandatory notifications
Clients lock notifications that people cannot switch off; mandatory messages that cannot be delivered are recorded as undeliverable.
- Alerts
One by one or a daily summary
For e-mail and WhatsApp, each person chooses individual messages or one daily summary at a time they pick, listing what waits for their action; critical events are never held.
- Alerts
Pending items digest
A periodic e-mail per person listing everything waiting on them by category — tasks, acknowledgments and open training — daily, weekly or monthly.
- PilotAlerts
Bilingual message templates
Templates per event, channel and language can be overridden, previewed, test-rendered and versioned, with only allowed variables.
- Alerts
Workflow reminders and escalation
Workflow rules send assignment, approval-required, returned, reminder, overdue, escalated and closed messages.
Mobile & field
In the field
Web push to the installed app and WhatsApp messages reach people on their phones where configured; the in-app bell works at phone width.
Business advantages
What changes for your organization
Critical messages always delivered, routine ones grouped into a daily summary on request.
People choose their channels within the rules the client sets.
Messages in English or Arabic from bilingual templates.
A delivery log for every e-mail and WhatsApp message.
Health information restricted to in-app and e-mail channels.
Who benefits
- HSE directors
- Site supervisors
- Employees
- Digital transformation leaders
- Operations directors
Notifications & Escalation Engine
See it working with your own processes
Modules marked Pilot are available to selected customers while they are completed. Capabilities depend on the configuration agreed for each deployment.