Product
Sevah gives assisted living communities a focused pilot motion: a companion that supports residents between visits and keeps families connected, plus a workflow layer that turns everyday moments into draft wellness updates and staff-reviewed follow-up.
How it works on a floor
The product is simple at the operating level: a resident has companionship and connection, families see more of the day, and the community record still belongs to licensed staff.
Companion sits in the apartment, handles simple conversation, and gives residents connection during the hours when family and staff can't be there.
Relevant observations are turned into draft wellness updates and follow-up prompts so families stay close and the next staff shift starts with context instead of reconstructing the day from memory.
Every update is reviewed, edited, and signed by a licensed staff member before it reaches families or the record. Sevah helps the experience move faster without taking authorship away from staff.
Pilot motion
One floor. A defined experience. Metrics your operators already care about. Sevah is meant to be evaluated in a real community, not sold as an abstract platform promise.
The first deployment is intentionally narrow. Pick a floor where family engagement and resident connection are already top of mind.
Companion ships with connectivity already configured, so a pilot does not depend on a community-wide network project before the resident experience can start.
You decide the metrics that matter for the pilot — resident engagement, family satisfaction, move-in interest. Sevah is there to make the experience observable, not to hand-wave generic ROI claims.
The device
On-device voice activity detection means the resident doesn't press a button. Companion listens when they speak and responds on the rhythm of conversation.
Camera-based vision context helps the model understand what's happening in the room and what the resident is doing. Vision inputs are processed in-memory and discarded. Video recordings are not stored.
Speech rate, vowel duration, and frequency profile are tuned for age-related hearing loss to make everyday conversations easier to follow.
Every device ships preconfigured with a cellular link. Community wifi is optional. IT is not in the critical path.
An explicit four-state conversation loop — listening, processing, speaking, idle — keeps interactions predictable. The resident knows when Companion is paying attention.
If a device crashes, it writes a diagnostic record to flash and uploads it on the next boot. Issues surface as tickets, not as staff complaints.
Why operators can trial it safely
The internal platform is only useful if it makes the resident rollout easier to evaluate, easier to fit into existing systems, and easier to keep inside staff-review boundaries.
Every observation becomes a draft update. A licensed staff member reviews, edits, and signs it. Nothing reaches the community record without a signature.
We route into the system the community already runs. PointClickCare, MatrixCare, and other adapter paths are there so a pilot does not start with a migration project.
Every device ships preconfigured with a cellular link, which reduces the chance that a pilot dies waiting on community wifi decisions.
The workflow layer keeps device and routing changes off the floor, so a pilot can adapt without turning every change into a hardware project.
Boundaries
Guided walkthrough
The public browser sandbox is offline. We now run a scoped walkthrough of the conversational loop, note draft, and routing flow with your staff.
FAQ
CareOS is Sevah's internal workflow layer for Companion deployments in assisted living communities. Buyers do not need to adopt a new record system to use it. It keeps each pilot configured, routes wellness updates and follow-up into the right workflow, and stays behind the resident experience.
Companion captures room conversation and limited context, then turns relevant moments into daily wellness updates families can see. Every update is reviewed by staff before it reaches families or the community record — the AI never auto-posts.
CareOS is record-system-agnostic. It routes structured observations and staff-signed updates into the system the community already runs — PointClickCare, MatrixCare, and others on request. Adapters are how we scale, not data migrations.
Companion may use camera-based vision context to understand the room, but those vision inputs are processed in-memory and discarded. Video recordings are not stored.
No. Every observation becomes a draft update. A licensed staff member reviews, edits, and signs it, and nothing reaches the community record without a signature.
Start with a 30-day pilot on a single floor. We install Companion units, route observations into your record system, and you measure resident engagement and family satisfaction on the metrics that matter to you.
Pick a floor. We install Companion units, route observations into your record system, and you measure the outcome on resident engagement and family satisfaction.