Reminders That Know When to Stop
A reminder that never stops is worse than none, because people learn to filter it and then miss the one that mattered. Every reminder AWRA sends has a short, fixed list of things it is allowed to say, says each one once, and goes quiet the moment the record no longer needs it.
The finance controller at a clearing and forwarding firm in Mombasa has an email rule that moves anything with “Reminder:” in the subject into a folder she opens on Fridays. She made it in her second month, after the old accounting system sent her the same overdue-invoice notice every morning for six weeks about a client who was already on a payment plan. The rule works. It also means that the reminder about a supplier bill falling due on Wednesday is read on Friday.
Nobody sets out to build a reminder like that. It happens because sending is the easy half. A job runs every morning, finds what is due and sends it. Deciding what not to send, and when to stop, is the half that keeps reminders worth reading, and it is the half this post is about. We set out what AWRA reminds people of in reminded before the date. Since then the list has grown from eleven reminders to twenty-five, and every one of them stops in the same few ways.
Each reminder has a fixed vocabulary
Every reminder records what it has said, against the workspace and a short key naming the record and the thing said about it. The key is the whole trick. A customer quote can be said to be expiring, and that is all: one key, one message, ever. A stock count can be due today and then overdue: two keys, so at most two messages. Once a key is recorded, nothing will send it again, however many times the job runs.
| Shape | Example | Most it will ever say |
|---|---|---|
| One stage | Quote three days from expiry; sales order past its date | Once per record |
| Two stages | Count due today, then overdue | Twice per record |
| Weekly backlog | Bills past due; last month not closed; timesheets open | Once a week while the backlog exists |
| Escalation | An exception past its SLA | Once per level, three levels at most |
A backlog is the one shape that repeats, and it repeats by calendar week rather than by day. Overdue supplier bills are one message a week listing them, not one a morning per bill. A message listing several things goes out when at least one of them has not been said before in that form, so a digest is never sent only to repeat itself.
Escalation that tops out
Escalation is a reminder that changes its audience, and it needs a ceiling more than anything else does. An operations exception that passes its SLA reaches level one when it breaches and rises one level for each further full day it stays open, up to level three. Level one goes to its owner, or to the people who can open that module if nobody owns it. From level two, the people who hold the escalation permission are added. Each level is announced once. After level three there is nothing further to say, because by then everyone who can act has been told. A helpdesk ticket that breaches its SLA climbs a ladder of its own, and how that ladder is set for a team too small to have one is in escalation paths that fit a six-person team.
A reminder is allowed to get louder. It is not allowed to get louder forever.
Stopping is worked out, not remembered
There is no step in which someone cancels a reminder. Each morning at 07:40 every reminder reads the records afresh and asks what is due now. A bill that has been paid, a claim that has been submitted, a count that has been closed or a quote that has been accepted is simply not in the answer, so nothing is sent about it. Fixing the record is the only way to end its reminders, and it is also the only way that should.
The same morning pass is careful about the past. Overdue reminders look back a short window, fourteen days for counts and thirty for sales orders and draft expense claims, so a workspace with two years of history is not told on its first morning about an order that slipped last March. And a reminder only goes to people who are still active members of the workspace, never to an address belonging to someone who has left.
Off means not asked
Each reminder is one row in notification preferences, with its own switches for email, the in-app bell and push. If every channel is off for a workspace, the reminder is not even asked what is due there, and nothing is recorded as said. Switching it back on later resumes from the records as they are on that morning.
The channels are independent in the direction people actually use them. Turning off the email keeps the bell copy, and the phone notification is sent from the bell copy, so a team that lives in the app can drop the email without losing the reminder. The same rule applies to every workspace email in AWRA: if either the email or the bell is on, the bell copy is written, and the email goes only if the email is on.
The one you cannot switch off ends by schedule
Billing reminders from AWRA to your workspace are mandatory, so they are the most careful about stopping. They go on fixed days around the plan end, such as fourteen, seven, three and one day before, and one, seven, fourteen and thirty days after, never two within three days, then monthly for at most a year. A renewal restarts the clock, and a healthy plan that renews on its own hears nothing.
Ask these of any system that reminds your staff
How many times can one record be reminded about?
Answer to listen for
A fixed number of stages, each once.
Why it matters
“Every day until it is done” is how reminders end up in a folder nobody opens.
What stops an escalation?
Answer to listen for
A top level, after which it stops.
Why it matters
An escalation with no ceiling ends up mailing the managing director about a stock count.
If we switch off the email, do we lose the reminder?
Answer to listen for
No, the in-app copy stays.
Why it matters
Channels that are switched off together get switched off entirely.
What does it send on the first morning?
Answer to listen for
Only recent items, within a look-back.
Why it matters
Otherwise day one is hundreds of messages about things nobody can fix.
The short version
In AWRA each reminder can say a small number of things about a record and says each once. Backlogs repeat weekly while they exist, escalations stop at level three, and every reminder ends on its own when the record is dealt with. Each one can be switched off per channel, and switching off the email keeps the bell.
What AWRA OpsHub does today
- Twenty-five scheduled reminders, run each morning, with operations exceptions also checked hourly.
- A record of what was said, per workspace, reminder and key, so nothing is sent twice.
- Stage keys, weekly backlog keys and escalation levels, each with a fixed most-it-will-say.
- Escalation capped at three levels, level one at the breach and one more per further full day.
- Reminders that end when the record is dealt with, with no cancel step.
- Short look-backs on overdue reminders, and recipients limited to active members.
- Per-channel switches, where turning off email keeps the bell and the phone notification.
- Mandatory billing reminders on fixed milestone days, spaced and ending after a year.
More we can add to your workspace
- Lead times your workspace sets, such as seven days before a bill rather than three. Commission it
- One morning summary per person gathering every reminder they are due. Commission it
- Snoozing one record’s reminder until a date you choose, such as a bill on hold for a dispute. Commission it
- A page listing what each reminder sent, to whom and when, for the people who manage notifications. Commission it
Where we point you to a specialist
- We do not let a reminder repeat daily about the same record. A message that arrives every morning teaches people to filter all of them, including the ones that matter.
The sent-reminders page is a short piece of work, because every message is already recorded with its workspace, reminder and key.
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 needsSee notifications and reminders
Every reminder, alert and digest AWRA sends, and the switches for each channel.
Explore notificationsFrequently asked questions
Will AWRA send the same reminder every day?
No. Each reminder records what it has said about a record and says each thing once. Only backlog digests, such as overdue bills, repeat, and they repeat weekly while the backlog exists.
How do reminders stop?
They stop when the record no longer needs them. Every morning each reminder re-reads the records, so a paid bill or a submitted claim is simply not reminded about. There is no separate step to cancel a reminder.
How far does an escalation go?
Operations exceptions past their SLA reach level one at the breach and rise one level for each further full day, up to level three. Each level is announced once, and from level two the people who hold the escalation permission are added.
If we switch off email reminders, do we lose them?
No. The in-app bell copy is still written and the phone notification is sent from it. The email is sent only when its own switch is on.
Can we switch off billing reminders?
No, billing reminders from AWRA are mandatory. They are sent on fixed days around the plan end or a failed payment, never two within three days, then monthly for at most a year.