Once you've decided when your lone workers should check in, the next question is how. The channel isn't a technical footnote — it's the single biggest lever on whether check-ins actually happen. A method that feels natural to the person, in the environment they're actually in, gets used. One that fights their hands, their signal, or their patience gets skipped. Here's a candid look at the three main options and where each earns its place.

SMS: the lowest common denominator, in the good sense

A text-message check-in is hard to beat for reach. It works on any phone, needs no app installed, survives a weak signal that would defeat data, and everyone already knows how to reply to a text. For a worker who's reluctant about "another app", or a workforce spread across a mix of personal and company devices, SMS removes almost every barrier to entry.

The trade-offs are real, though. A text is easy to reply to without thinking — a one-word "ok" tells you a thumb moved, not necessarily that the person is safe and unpressured. It carries no tone, so distress doesn't come through. And it depends on the worker noticing the message, which a phone on silent in a pocket can defeat.

  • Best for: broad reach, mixed device estates, lower-risk routine confirmations, workers who resist apps.
  • Watch out for: reflexive replies, no sense of the person's state, reliance on them seeing the message.

The app: richer, when people keep it to hand

A dedicated check-in app can do things a text can't. It can present a clear, deliberate confirm action, capture the last location a worker checked in from, offer a discreet way to raise an alarm, and adjust intervals on the fly as the risk of the task changes. For higher-risk or more structured work, that richness is genuinely valuable.

The catch is engagement. An app only protects someone if it's installed, logged in, permitted to send notifications, and — critically — actually opened when a check falls due. Every one of those is a place compliance leaks away. Apps also lean on a data connection, which is exactly what you may not have in a basement plant room or a rural blackspot.

  • Best for: higher-risk roles, structured multi-stage tasks, teams on managed devices who'll keep the app live.
  • Watch out for: install and notification friction, data-signal dependence, the "did they open it?" gap.

The AI voice call: the one that's hard to ignore

An automated voice call flips the dynamic. Instead of relying on a worker to remember and initiate, the system calls them. A ringing phone is much harder to tune out than a silent notification, and answering it is a near-universal instinct. Our voice check-ins are handled by Zoe, an automated caller who rings a worker when a check is due and confirms they're alright.

The quieter advantage is presence. A short spoken exchange carries something a tap or a text simply can't — the difference between a relaxed "yeah, all fine" and a clipped, strained answer. It's also inclusive: it needs no app and no typing, which suits hands-full, gloves-on, screen-in-daylight realities and workers less comfortable with apps.

To be clear about what this is and isn't: an automated call confirms a worker can answer and respond. It's a strong signal of wellbeing, not a medical assessment or a lie detector — and like any channel it depends on the phone having signal and charge.
  • Best for: making check-ins hard to miss, capturing a human signal of wellbeing, workers who won't or can't use an app.
  • Watch out for: needs a working phone connection; a missed call must feed straight into escalation.

You don't have to pick just one

The most robust setups treat channels as complementary rather than rival. A routine confirmation might go by text, while a higher-risk visit warrants a voice call; a worker who ignores a notification might get a call as the fallback before anything escalates. Matching the channel to the person and the moment — rather than mandating one method for everyone — is what pushes real-world compliance up.

What matters more than the channel

Whichever channels you choose, the thing they must all share is a hard backstop: when a check-in doesn't come — unanswered text, unopened app, missed call — that gap has to flow immediately into a defined escalation ladder that reaches a real person and doesn't stop until someone responds. The channel gets people to check in. The escalation is what makes not checking in matter. See how it works to view the whole flow, and pricing for what's included at each tier.