Which Alerts Deserve a Phone Buzz
A push notification interrupts a person wherever they are. That makes it the most valuable channel an operations system has and the fastest one to ruin. A test for which alerts earn a buzz, and how to set it up row by row.
The short version
Push an alert to a phone only if it passes three tests: someone must act within hours, the person receiving it is the one who can act, and missing it costs something. Everything else belongs in the bell or a digest. In AWRA OpsHub, push is a column on each notification row, so the decision is made one alert at a time.
The first week with push notifications feels like control: every approval, every stock movement, every sync, in your pocket. By the third week the phone buzzes forty times a day and the useful buzz is indistinguishable from the rest. People respond the only way available to them — they turn notifications off for the whole app, and the one alert that needed them goes with it.
The three-question test
-
Does someone have to act within hours?
A delivery overdue today, an approval holding up a payment run, a branch about to run out. A weekly summary does not.
-
Is the person receiving it the one who acts?
A push to someone who can only forward it is an email with a vibration.
-
Does missing it cost something?
Money, a deadline, a customer. If the answer is “they will see it tomorrow anyway”, it belongs in the bell.
A starting manifest
| Alert | Push | Why |
|---|---|---|
| Approval waiting on you | Yes | You are the one blocking it, and it has a deadline |
| Purchase orders overdue for delivery | Yes | Somebody has to phone the supplier today |
| Low stock at your branch | Yes | A reorder placed today is a stock-out avoided |
| Integration sync failed | Yes, to the person who fixes it | It will not mend itself |
| Weekly HR summary | No | A summary is read, not acted on in the moment |
| Pending approval digest | No | The individual approvals already pushed |
| Sync succeeded | No | Success is not news |
How it is set up
AWRA OpsHub runs on Android phones through Google Play. In Settings → Notification preferences, push is a column beside in-app, email and the chat channels, and it starts switched on for every row, so the first job is to switch it off where it fails the test above. WhatsApp and SMS start switched off; Slack, Microsoft Teams and the other chat channels need their connector first.
A push follows the person’s own in-app notification, so it reaches the same people as the alert and nobody else, on the phones where they are signed in. Tapping it opens the matching screen in the app when there is one, and the page in the browser when there is not. A phone signed in to a different organization ignores a push meant for another one.
Reminders and digests carry a cadence
Rows that repeat — reminders and digests — have a cadence on the same row: daily, weekly, monthly or every so many days. Lowering the cadence is often a better answer than switching push off, because it keeps the alert and removes the repetition.
For the rest of the channel decisions, see mute the email, keep the alert; for WhatsApp and SMS in particular, WhatsApp and SMS alerts for operations.
What AWRA OpsHub does today
- Push to the AWRA OpsHub app on Android as a column on every notification row
- Pushes addressed to the same people as the in-app notification, on the phones they are signed in on
- A tap that opens the matching screen in the app, or the page in the browser
- A cadence on every reminder and digest row
More we can add to your workspace
- Per-person push choices within the workspace’s settings
- Quiet hours that hold non-urgent pushes until morning
- Push to iPhones through the App Store
Where we point you to a specialist
- Whether a phone rings, vibrates or stays silent is the phone owner’s choice in their device settings; we send the notification and respect it.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsPrune your push column in ten minutes
Which rows are summaries or digests?
Look at
Anything with “digest” or “summary” in its name.
Then
Switch push off for those rows.
Which rows report success?
Look at
Sync succeeded, confirmations.
Then
Switch push off, or the whole row.
Which rows have a deadline attached?
Look at
Approvals, deliveries, stock.
Then
Keep push on, and keep the cadence tight.
Who has turned off notifications for the app entirely?
Look at
Ask the team.
Then
Too much was pushed; prune before asking them back.
Make every buzz worth answering
Push, in-app, email and chat channels, decided one alert at a time.
Talk to usFrequently asked questions
Which ERP alerts should be push notifications?
Only alerts where someone must act within hours, the person receiving it is the one who can act, and missing it costs something, such as an approval holding up a payment or an overdue delivery. Summaries, digests and success confirmations belong in the in-app bell instead.
Does AWRA OpsHub send push notifications to phones?
Yes, to the AWRA OpsHub app on Android phones. Push is a column in the notification settings, set for each notification separately.
Who receives a push notification?
The same people who receive the in-app notification, on the phones where they are signed in. Nobody else in the workspace receives it.
What happens when I tap a push notification?
It opens the matching screen in the app when there is one, and the page in your browser when there is not.
