Confirm-first care escalation

Vision spots the moment. The ladder picks the next human-safe step.

Camera cues - stillness, a covered lens, a fall signature - start a ladder that asks the person first, then pages the right human on the channel they already use, and waits for an answer before climbing. Every step is timestamped and auditable.

Cue
stillness noticed · confidence scored
Voice check-in · answered
"I'm fine, thanks - just resting." most incidents stop here · nobody is paged
Page caretakers
Slack · Teams · WhatsApp · Telegram
Await acknowledgment
one tap in chat stops the climb
Escalate
next contact, then a real phone call
Emergency · fail-closed
never dialed automatically

The person answers first. Everyone else is plan B.

Before any alert leaves the building, Care Ladder asks the person directly - through a speaker check-in. The response decides what happens next, and the response itself is the product's core signal.

Positive reply

Closes in place

"I'm fine" by voice resolves the incident at rung two. Staff and family are never paged; the transcript is kept for review.

illustrative demo script · 38s
Negative reply

Raises priority, jumps the queue

"No... I can't get up" is classified as a negative reply: priority is raised and caretakers are paged immediately, with the wait rungs skipped.

negative class raises priority · lead can correct
Silence

Escalates on a timer

No answer inside the window pages caretakers with a countdown. No acknowledgment, and the ladder climbs to the next human - visibly, on the record.

plan-defined ack window · every hop audited

Two very different customers, one engine

The same engine serves a daughter checking on her mother and a floor lead running a ten-room wing. Different surfaces, same honesty.

For families · Home plan · chat runtime rolling out

The care conversation belongs in your chat app

Nobody opens a console when Mom might need help. Care Ladder is being rolled out as a bot thread in WhatsApp or Telegram - today's live demo runs the same ladder with one-tap acknowledgment links:

  • Inform with a countdown - blurred frame, plain words, "we'll call you, then Sarah"
  • One-tap acknowledgment - "I'm on it" stops the escalation, from the acknowledgment link (chat buttons rolling out with the Telegram runtime)
  • Update by replying - roadmap: "she's fine, balcony again" becomes the case note
  • Evening recap - roadmap: check-ins answered, calls placed, response times
See the family experience →
For facilities · Starter and Growth plans

A command center that only interrupts when the floor can't cope

Pages route to the shift channel first. The console is triage, cases and audit:

  • Alert center - priority queue, aging timers, assign, override, de-escalate
  • Cases - acknowledged, handled, closed with required documentation
  • Audit - time-to-ack, handling times, response transcripts, CSV export
  • Shift aware - breaks respected, coverage warnings when the shift thins
See the facility console →

What page-and-acknowledge looks like at home

An evening when the check-in went unanswered. The whole incident, handled inside one thread - the console stayed closed. Design preview: the in-chat runtime is rolling out; today's live Home demo runs the same ladder with one-tap acknowledgment links.

CL
Care Ladder · Mombot · silent unless it matters
Check-in not answered. No movement in the living room for 15 minutes. If nobody responds in the plan-defined window, I'll call you, then Sarah. 21:17
Escalation stopped. You acknowledged in 52s. 21:18
called her back - she's fine, balcony again 21:26
Closed · all fine. Cue 21:12 → page 21:17 → you acked in 52s → closed 21:26. Clip: 3 frames, faces blurred (design preview). 21:26

Paging that meets people where they are

One router, four delivery channels, honest per-channel status: adapters are built into the engine, and this demo runs them in stub mode - every delivery result, real or stubbed, is recorded in the incident audit trail.

S

Slack

incoming webhook · supervisor mentions
configured · stub in demo
T

Microsoft Teams

Workflows webhook
adapter present · not configured in demo
W

WhatsApp

Cloud API adapter · text pages
adapter present · not configured in demo
TG

Telegram

Bot API adapter · text + inline buttons when configured
adapter present · not configured in demo

Per-camera, per-household pricing. No per-seat tax on family.

Checkout runs live via Stripe (test mode during the Galuxium build).

TierPriceWhat you get
Home
Solo families
$9/mo 1 household · 1 camera · voice check-in ladder · caregiver notify · full audit trail
Facility Starter
Small assisted-living
$49/mo Up to 10 rooms · shift channel queue · alert center, cases and audit · CSV export
Facility Growth
Multi-unit operators
$99/mo Unlimited rooms · multi-tenant admin · learning schedules on the Growth roadmap · priority support

Reserved fictional phone numbers are used throughout the demo; telephony is stubbed and emergency dialing ships disabled and fail-closed.

Built to be defensible, not just impressive

Every claim the product makes is one a care operator can stand behind.

Privacy before persistence

Frames are blurred or silhouetted before anything is stored. Person tracking uses shape geometry only - never identity. Clips state their retention window.

Every hop on the record

Cue, check-in, page, acknowledgment, call, close - each step is timestamped in a per-incident audit trail, exportable for review and shift handover.

Fail-closed by design

Emergency numbers are never dialed automatically; the emergency rung ships disabled and stays behind a human gate. Unsigned billing webhooks are rejected outright.

Questions people actually ask

Does it call emergency services by itself?

No. The emergency rung is fail-closed: it ships disabled and never dials on its own. A human always decides. In every demo the numbers dialed are reserved fictional ones.

Is this a medical device?

Care Ladder is a wellness workflow, not a medical device. It does not diagnose, does not score clinical risk, and never presents itself as one.

What happens if nobody acknowledges?

The ladder climbs on timers: after the acknowledgment window expires, the next contact is paged, then called - each step visible in the console and recorded in the audit trail.

What does the camera actually see?

Cues are behavioral: stillness in a zone, a covered lens, a vertical-to-horizontal transition that resembles a fall. Frames are privacy-transformed before persisting, and tracking never identifies individuals.

Can staff step away without breaking it?

Responders set breaks from the staff console; auto-routing shows their status and countdowns, and the floor lead can pull someone off break as a logged override. (Chat-side break commands are on the roadmap.)

Try the live demo

Two pre-seeded accounts, one click each. This is a sandbox: stub notifications, reserved fictional numbers, emergency fail-closed. Or open the consoles directly: family console · facility console.