Solutions / AxiomCode Notify
Instant WhatsApp and email alerts for the events that matter.
AxiomCode Notify watches the data in your systems. The moment an event happens or a value changes beyond a limit, the right people get a WhatsApp message or an email. Every alert is logged, and no one gets the same alert twice.
- In production, monitoring 1,000+ assets
- Runs 24/7
- WhatsApp and email
AxiomCode NotifyBusiness accountVolume: 16.5 L (Capacity: 602 L)
Date: 2026-10-02 16:30:00
Location: maps.google.com/?q=…16:31 ✓✓
Volume: 41.0 L (Capacity: 400 L)
Date: 2026-10-02 17:05:00
Location: maps.google.com/?q=…17:06 ✓✓
Volume: 22.0 L (Capacity: 400 L)
Date: 2026-10-02 18:12:00
Location: maps.google.com/?q=…18:13 ✓✓
The problem
Your systems see the problem first. Your people find out too late.
- Events go unnoticedDashboards only help when someone is looking at them.
- Alerts reach the wrong peopleOne shared inbox for every site, vehicle or team means nobody owns the alert.
- Repeated or missing alertsSystems that re-send events, or go quiet during downtime, erode trust in alerts.
- No record of what happenedWhen someone asks “why wasn’t I told?”, there is no answer.
How it works
From your data to the right phone in minutes
Connect your data
We connect Notify to the system that holds your events, usually through its API.
Set the rule
A value crosses a limit, changes by more than a set amount, or a specific event occurs.
Choose who is told
Group your assets and give each group its own WhatsApp and email recipients.
Delivered and logged
Each alert goes out once, and every decision is recorded for review.
Features
Built for alerts people can rely on
WhatsApp and email
Approved WhatsApp Business templates and HTML email, with an optional address copied on every email.
Exactly once
Each alert reaches each person once, even when the source system re-sends the same event.
Never misses an event
After any downtime, Notify recovers the missed period, and it re-checks for late-arriving events.
The right people, per group
Assets are tagged to groups. Each group has its own WhatsApp and email recipients.
Limits you control
Change an alert limit from the admin screen. It applies from the next check, with no redeployment.
Every decision explained
Each event is logged with its outcome, so “why wasn’t I alerted?” has an answer on screen.
Self-healing
A watchdog detects a stalled schedule and restarts checking automatically.
Service health
A live status, every polling run and every system issue, in one place.
Secure admin console
Admin and user roles, test sends, and password resets that sign a user out on every device.
Inside the console
See every alert, and why it was sent
| Vehicle No | Event | Volume | Percentage | Event Date/Time | Sent Date/Time | Channel | Recipient | Status |
|---|---|---|---|---|---|---|---|---|
| MH 04 AB 1234 | Drain | 16.5 L | 2.7% | 02 Oct, 16:30 | 02 Oct, 16:31 | +91 98XXX XX101 | DELIVERED | |
| MH 04 AB 1234 | Drain | 16.5 L | 2.7% | 02 Oct, 16:30 | 02 Oct, 16:31 | ops@example.com | DELIVERED | |
| GJ 01 CD 5678 | Drain | 41.0 L | 10.3% | 02 Oct, 17:05 | 02 Oct, 17:06 | +91 97XXX XX202 | DELIVERED | |
| RJ 14 EF 9012 | Drain | 22.0 L | 5.5% | 02 Oct, 18:12 | 02 Oct, 18:13 | +91 99XXX XX303 | FAILED |
Illustrative screen · sample data
| Vehicle No | Volume % | Outcome | Reason |
|---|---|---|---|
| GJ 01 CD 5678 | 10.3% | SENT | Above 5% limit |
| KA 05 GH 3456 | 1.8% | BELOW THRESHOLD | Below 5% limit |
| MH 04 AB 1234 | 2.7% | DUPLICATE SKIPPED | Already sent |
| TN 09 JK 7890 | 6.1% | NO RECIPIENT | Vehicle not in a group |
Illustrative screen · sample data
| Start Time | End Time | Events Found | Notifications Sent | Status |
|---|---|---|---|---|
| 17:30 | 18:00 | 14 | 3 | SUCCESS |
| 17:00 | 17:30 | 9 | 2 | SUCCESS |
| 16:30 | 17:00 | 11 | 4 | SUCCESS |
| 16:00 | 16:30 | 7 | 0 | SUCCESS |
Illustrative screen · sample data
Where it fits
Any event, any value, any industry
Notify runs in production for fuel-drain alerts. The same engine can be set up for your events.
- IN PRODUCTION
Fleet fuel drain
Alert managers when fuel drops beyond a set share of tank capacity.
DG sets and tanks
Low fuel, unexpected consumption or long run-hours at remote sites.
Manufacturing
Machine stopped, output dropped, or temperature out of range.
Cold chain
Temperature excursions in storage or in transit.
Inventory
Stock below reorder level at any location.
Finance
Failed payments, overdue invoices or unusual transactions.
IT operations
A server, service or integration stops responding.
Your own event
If your system records it, Notify can alert on it.
Pricing
Pay for setup once, then only for alerts sent
Connecting your data source, configuring rules, groups, recipients and WhatsApp templates.
You pay for the alerts Notify delivers. Ask us for a quote based on your expected monthly volume.
Questions
Frequently asked questions
Which systems can Notify connect to?
Any system that makes its events available, usually through an API. We set up the connection for your system as part of onboarding.
Do I need a WhatsApp Business account?
Alerts go out as approved WhatsApp Business template messages. We help you set up the account and templates.
What happens if the service goes down?
When it comes back, Notify works out which period it missed and processes those events in order, so nothing is skipped.
Will people get the same alert twice?
No. Each alert is reserved for each recipient before it is sent, so repeats from the source system are skipped.
Can we change the alert limit ourselves?
Yes. Administrators change it on the settings screen, and it applies from the next check.
Who owns the alert data?
You do. Your event data and alert history belong to you.
See it working
Book a demo of AxiomCode Notify.
We’ll show you live alerts, the console, and how your events would be set up.