Skip to content

Business Operations & Automation

Notification system: delivery you can prove

A leak at 10 p.m. and a paid invoice arrive as the same kind of text, so the urgent one gets missed and the routine ones wake people up. A notification system tracks every urgent alert until a person acknowledges it, climbing from text to push to a call to a backup person when they don't, and holds routine alerts for a digest. We build it around your urgent alerts, your rota and the people who need to hear.
Talk through your alertsFollow one alert ↓
URGENT · water leakAcme, 220 Lake St · Unit 4BAL-905 · raised 22:14 · on call: T522:14SMS · T5sent…no reply in 5 min22:19Push · T5sent…no reply in 5 min22:24Call · T5ringing…no answer22:29Backup · T2, SMS and callcalling…acknowledged 22:31T5 and the office lead told: covered by T2Routine · tonightheld until morningINV-2270 paidQ-266 viewed by customerR-1104 booked for ThuPR-14 boiler deliveredT3 timesheet submittedSA-91 signedMorning digest · 07:306 updates · to the office leadnothing urgent waiting

Sent is not the same as seen

Most tools can send a text when something happens, and most businesses end up with dozens a day: payments, bookings, quote views, timesheets. The one that matters, a leak at night or a customer with no heat, looks just like the rest. If the person it went to is asleep or out of signal, nobody knows it wasn't seen until the customer calls again.

A notification system treats urgent and routine alerts differently. Urgent alerts are tracked until a person acknowledges them, and climb a ladder of channels and backup people on a timer if they don't. Routine alerts are held for a digest at a sensible hour. Every alert has a record of where it went, when, and who saw it.

Today, and with a notification system

Today

  1. 01Every tool sends its own texts and emails.
  2. 02Urgent and routine alerts look the same.
  3. 03Nobody knows if an alert was seen.
  4. 04If the on-call person misses it, nothing else happens.

The urgent alert was sent. Nobody saw it.

With a notification system

  1. 01Every alert comes through one place.
  2. 02Urgent alerts wait for an acknowledgement.
  3. 03No reply climbs the ladder: push, call, backup.
  4. 04Routine alerts gather into a digest.
  5. 05Every alert has a record of who saw it, and when.

An urgent alert ends with a person, not a sent message.

One alert, end to end

The leak from the top of the page, from the building manager's report to the closed job.

Events

Alert · AL-905

Status
raised
Event
water leak, urgent
Sent to
—
Channels
—
Acknowledged by
—
Resolved
—

Event 1 of 7: alert.raised

Who's first, and who's next

Weekdays, 07:00–18:00The office leadThe operations manager
Weeknights, 18:00–07:00The on-call technician (this week T5)T2
WeekendsThe on-call technician (this weekend T3)The operations manager
Payment failuresFinanceThe office lead
Failed syncs and stuck automationsWhoever's on callThe operations manager

What changes from one business to the next

Urgent or routineWhich events need a person now, and which can wait
The ladderWhich channels, in what order, and how long between steps
The rotaWho's first and who's backup, by time and kind of alert
DigestsWhen they go, and to whom
Quiet hoursWhat never goes out at night, whatever happens

A common starting point is Twilio for texts and calls, push through the app your team already uses, n8n or Trigger.dev for the ladders and timers, and PostgreSQL for the alert records and rota. These are starting candidates, not requirements.

Is a notification system the right fit?

Good fit

  • Some alerts can't wait, and some come at night.
  • Your team gets so many routine alerts that urgent ones get lost.
  • You've had an urgent alert that nobody saw.

Avoid when

  • Nothing you handle is urgent outside working hours.
  • A single tool's alerts already reach the right person reliably.

How we'd approach it

Most of the early work is sorting urgent from routine, setting the escalation ladder and the rota, and agreeing quiet hours.

  1. 01

    Understand

    As much as the problem needs

    We map how the work runs today: who does what, which systems hold the records, and where it breaks.

  2. 02

    Design

    Decided before it's built

    Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.

  3. 03

    Build

    Connected to what you use

    We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.

Related systems

The capabilities underneath

Questions about notification systems

How does someone acknowledge an alert?

By replying to the text, tapping the push notification or pressing a key on the call. Whichever they use, the ladder stops.

What if nobody acknowledges at all?

The last rung of the ladder is someone who always answers, usually the owner or operations manager, and the alert stays open on the command center until it's handled.

Will this send more alerts, not fewer?

Fewer. Routine alerts move into digests, and urgent ones go to one person at a time instead of everyone at once.

Can customers get these alerts?

Customer messages are handled by communication orchestration, from the job's state. This system is for your team.

Make sure the urgent ones are heard

Tell us which alerts get missed today and which wake people up for nothing. We'll show you how each would be delivered.

Start a project