Water requested
How it works
From a resident's words to a closed task.
Six steps, each visible to your team — and a clear answer for what happens when something goes wrong.
The six steps
- 01
The resident presses start
The room device is paused until the resident presses its button. Its light shows when it's listening. Nothing is heard or sent before this — the resident is in control.
- 02
They say what they need
In their own words — “Could I get another blanket?” Short clips of speech are sent; silence isn't. The device detects speech on its own, so quiet periods aren't uploaded. Pausing clears anything not yet sent.
“It is really cold in here. Could I get another blanket?”
- 03
The clip is sent securely
Over an encrypted connection to private storage. The request is accepted right away, even before AI has looked at it. If the Wi-Fi drops, the device holds a short buffer and retries; a repeated upload never creates a second task.
Room 108 Encrypted Private storage - 04
AI understands the request
Request, category and a short summary — or, if it's unclear, a review item for a person. Then the audio is deleted. Several needs in one sentence become separate tasks. Television and visitor chatter create nothing.
Understood
Request · Comfort
Summary: “Another blanket — room is cold”
Audio deleted
- 05
Staff are alerted
A task appears on the station board, and staff phones covering that unit receive “New care request”. The lock screen never shows the room, the resident or the request — staff sign in to see details.
Wednesday 14 October
2:14
AskLightnow
New care request
Open AskLight to see details
- 06
Someone claims it and completes it
One tap to claim. Everyone sees who's on it. Completion is recorded with a timestamp. Supervisors can reassign, cancel with a reason, or reopen. Nothing is ever completed automatically.
‹ Board
Room 108 East Wing
Another blanket
Comfort
What the resident said
“Could I get another blanket?”
- Request created · 2:14
- Claimed by you · 2:15
StartComplete
When things go wrong
Designed to fail visibly, never silently.
Every system has bad days. Here's what AskLight does on its worst ones.
No one claims a request
After a set time (two minutes by default, configurable) it's marked overdue and escalated in the supervisor view. Escalation is shown on screens — it isn't a guaranteed page or phone call.
The AI isn't sure
Unclear speech goes to a review list. A supervisor approves it as a task, edits it, or dismisses it — and the decision is recorded.
Pillow fell on the floor
AI processing is down
The board shows that voice processing is degraded. The device's long-press still sends a help request with no audio and no AI, and existing tasks keep working.
Wi-Fi or power drops
The device shows its state with its light, and the admin screen shows it as offline or faulty. A short buffer is retried when the connection returns; anything too old is discarded, and the gap is reported.
For emergencies, use your nurse call system. AskLight is not an emergency system. Keep using your nurse call system and emergency procedures for emergencies.
Frequently asked questions
How fast does a request reach staff?
Our engineering target is a few seconds from the end of speech to a task on the board, but network and AI provider delays vary. We'll measure real times with you during a pilot rather than promise a number.
Who gets alerted?
Staff whose app covers that unit receive a phone alert, and the request appears on that unit's station board. Claiming is always an explicit action — receiving an alert never counts as accepting it.
What if two staff tap Claim at the same time?
Only one claim succeeds. The server decides, and everyone's screen updates to show who owns it.
Can staff add requests themselves?
Yes. Staff can enter a request on the board or app — for example one a resident mentions in person — so it's tracked the same way.
See AskLight on one of your units.
Tell us about your nursing home. We'll walk through how a pilot works and whether AskLight is a fit — no commitment.