Skip to content
Timelee home

Use case

Being on call means someone has to actually be reachable

Being on call is a promise that you're reachable, not just that your phone has an app installed. A notification that fires while you're asleep, driving, or in a dead spot has not kept that promise, whatever the app's logs say.

Start with GoogleSee phone call reminders

The job is being reachable, not having an app installed

On-call rotas exist because something might need a person, and the whole arrangement only works if that person can actually be reached when it matters. Most tools that support this treat 'reachable' as a solved problem the moment a notification is sent. It isn't. A push notification is silent by design if the phone is on silent, and a phone on silent at 2am is not a failure of the system, it's what silent mode is for.

The handover, the escalation, the swap request — none of these are optional reads. They're the actual mechanism of the rota working. When the primary is unreachable, the point is that someone else needs to know quickly, not eventually.

This page is about making the reminder itself match the stakes: a plain alarm for the routine handover, and something that reaches through silence for the moment someone actually needs to be woken.

Three moments where reachability actually gets tested

None of these are hypothetical if you've ever done a rota.

  • The handover happened at the end of a long day

    The outgoing person sent the notes and assumed they'd been read. The incoming person's phone was face-down on the charger.

  • The escalation window closed unnoticed

    Primary didn't respond within the agreed time, and nothing automatically told the backup that the window had opened for them.

  • A swap request sat unanswered

    Someone asked to trade a night, it went into a message thread, and by the time anyone replied the shift had already started.

Match the delivery to what's actually on the line

Not every on-call reminder needs the loudest channel. Escalation is a choice per reminder, not a default.

  1. notif_type 1

    Regular

    A plain alarm for a routine handover — the notes are ready, nothing urgent, just a prompt to read them before the shift starts.

  2. notif_type 2

    App Call

    A full-screen ring inside Timelee for anything you want acknowledged properly, like a swap request that needs an actual answer.

  3. notif_type 3Recommended

    Important

    The alarm, then the app call if unacknowledged. A reasonable default for a shift start reminder.

  4. notif_type 5Premium · uses credits

    Critical

    Alarm, then app call, then a real phone call if it's still unacknowledged ten minutes later. For the escalation itself — the moment someone genuinely needs waking.

The handover and the swap are shared reminders, not messages

A shared reminder, assigned to the incoming person, is a different thing from a message: it arrives as a push notification, and they accept or decline it. You can see which. That distinction matters more here than almost anywhere else — a handover that was read is not the same as a handover that was acknowledged, and a rota needs to know the difference.

For a swap request, assign the reminder to the person you're asking, with the details in the note. They accept or decline, and it's visible rather than buried in a thread with everything else that week.

None of this replaces whatever formal on-call software your organisation already runs for pages and incidents. It's a lighter layer for the human coordination around a rota — the handover conversation, the swap, the reminder that your shift starts at 22:00.

  • Shared reminders record accept and decline, not just delivery
  • A note carries the handover detail with the reminder itself
  • Assign to one person, or to whoever's covering that day

What this is built from

Three features, working together.

  • Shared reminders

    Assign the handover or the swap, and see whether it was accepted, not just sent.

  • Per-day repeats

    A rota that changes week to week fits per-day toggles better than a weekly repeat that assumes the same pattern every time.

  • Phone call reminders

    For the escalation itself: a real call that reaches through silent mode and a locked phone.

Only verified numbers get called

Escalating to a colleague's phone works because they've verified their own number with a one-time code first. Nobody can be added to an escalation chain and start receiving calls without confirming the number themselves.

Questions about on-call reminders

Can I escalate to a colleague if I don't respond?

Set a Critical reminder pointed at your own number, or a separate Phone Call Only reminder pointed at a colleague's verified number as a backup step.

Will a phone call wake someone through silent mode?

It rings on the phone network rather than as a push notification, which is why it reaches a phone that's silenced or locked. How your specific handset handles it is worth testing once with a reminder set a couple of minutes ahead.

Can I see whether a handover was actually read?

Share or assign it, and you'll see whether it's pending, accepted or declined — a clearer signal than whether a message shows as read.

Does this replace our incident paging system?

No. It's a lighter layer for the human side of a rota — handovers, swaps, shift reminders — not a replacement for dedicated incident or paging software.

Set your next handover as a shared reminder, not a message

Sign in with Google, assign the handover to whoever's coming on, and give the escalation step a real phone call.

Start with GoogleSee how delivery works

Keep reading