Lone workers, night shifts, and the safety problem nobody solves well.
Every agency that runs employees into the field alone — home care caregivers on overnight visits, installers on a solo customer site, security guards walking a round — hits the same wall: how do you know they're okay, right now, without buying a six-figure lone-worker safety platform with badges, panic buttons, and GPS dongles?
Most solutions in this space are either too expensive (purpose-built lone-worker apps with per-user licenses), too complex (GPS hardware, app installs, training), or too invasive (constant location tracking your staff won't consent to). Agencies compromise by doing nothing, hoping for the best, and keeping a paper log of who's out alone.
You need a minimum-viable safety check-in — a way to verify a worker is fine during a risky shift, escalate if they don't respond, and produce an audit trail that satisfies regulators. Not a SWAT rescue system. Just a simple, reliable pulse check.
Rubi Echo is SMS-based safety check-ins.
Echo sends a text message to a worker at configurable intervals during their shift. The message is simple: "This is your Rubi Echo check-in. Reply 1 if you're OK, 2 if you need help." The worker replies. Echo logs the response. If they don't reply within the window, Echo escalates — automatically.
That's it. No app to install. No training. Works on every phone that receives SMS. The whole system is one Python service, one Twilio number, and a rule configuration pulled from your existing employee directory.
A simple, reliable pulse check — not a SWAT rescue system. That's what most agencies actually need, and what Rubi Echo delivers.
Flexible scheduling — match the rule to the risk.
Not every shift needs the same check-in frequency. A 12-hour overnight visit in a private home needs a different cadence than a 4-hour solo installation. Echo's rules let you configure:
- Interval-based — check in every 2, 4, or 6 hours across the shift
- Time-offset — first check 30 minutes after shift start, second at halfway, third at shift end
- Fixed windows — check in at specific times (e.g., 23:00, 02:00, 05:00 for overnight care)
- Per-role rules — caregivers get one pattern, installers get another, security staff get a third
- Per-client exemption — some client sites are low-risk and don't need check-ins at all; others need tighter cadence
Escalation that actually escalates.
When a worker doesn't reply, Echo doesn't just log "no response" and move on. It runs a configurable escalation ladder:
AlayaCare integration — no duplicate scheduling.
Rubi Echo doesn't have its own schedule. It reads from AlayaCare (or Q360, or NetSuite) and uses visit tags to decide which shifts require check-ins. Tag a visit "lone-worker," "overnight," or whatever label your team uses, and Echo automatically applies the matching rule. When scheduling changes, Echo sees the change. Zero double-entry.
You don't need to monitor every visit — just the risky ones. Tag-based rules let the scheduling team flag visits once at creation, and Echo handles the rest. Supervisors never have to "remember to turn on check-ins."
Compliance without the theater.
Several jurisdictions — particularly in Canadian provinces and European markets — legally require lone-worker monitoring for healthcare and security staff. Echo produces a clean audit log of every check-in, every response, every escalation, and every outcome. When a regulator asks "prove you're monitoring your lone workers," you hand them the log.
It's also common for agencies to go beyond the legal minimum because staff welfare is a retention tool. Caregivers who know someone's watching out for them on a 3am visit are less likely to burn out.
Use cases.
- Home care overnight visits — confirm the caregiver arrived, is awake, and is fine during the shift
- Solo installation jobs — AV integrators, security installers, field technicians on remote sites
- Night-shift supervision — building managers, security guards, warehouse ops
- Travel risk — staff on long solo drives between client sites
- Post-incident follow-up — temporary high-cadence monitoring after a safety event to ensure recovery
Frequently asked questions.
Immediate escalation — same ladder as a non-response but skipping the nudge steps. Office gets a red-priority alert with the worker's name, location, and last known context. Supervisors can respond within seconds.
Echo retries when the SMS bounces back as undelivered. If the worker's phone is out of coverage for the entire window, Echo escalates the same way it would for a non-response — which is the safer default.
Yes. Echo can take shift data from any source that exposes an API, a CSV, or a webhook. The integration layer is the flexible part — the check-in engine is the same.
You pay Twilio directly for SMS + voice. A typical overnight home care agency with 50 monitored shifts per week lands around $40-60/month in Twilio charges plus our platform fee. An order of magnitude less than dedicated lone-worker platforms.