Care pathways and home visits
Successive steps, prerequisites, several workers or locations, home visits and confirmation that somebody has taken over: exactly the shape of agency work.
AlayaCare
Coordinating a home visit is not deciding on care. The request is written into Zenvox under your roles sheet; no access contract is established at the vendor.
7 days, 20 answered calls, no card
Where your service call lands
The request is written into Zenvox: the person receiving care, the person asking, the person paying, what is being asked, and the caller standing to ask it. AlayaCare keeps the truth of the care plan and of visit scheduling; nothing is written there, and no access contract is established. Coordinating a visit is not deciding on care: the receptionist passes it on, the clinical team decides.
On access, plainly: external public documentation cites a care plan and a scheduler, but reading and writing visits, assignment and exact status remain to be confirmed, and both the access contract and credentials remain to be established. This research line is retained from an earlier pass and was not re-checked: it is given for what it is.
AlayaCare holds the care plan and visit scheduling for home support and nursing agencies; the person receiving care, the person asking and the person paying are three different people, and the receptionist reads your roles sheet before writing anything down.
Read, create, update, cancel
The status below reflects documentary research that was not re-checked, and the absence of an access contract. It tightens as soon as real access is obtained.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | External documentation cites a care plan and a scheduler. Reading a planned visit or the assigned worker would require a customer or partner contract and credentials that are not established. |
| Create | Zenvox native mode | Scheduling a visit commits a qualified worker, physical equipment and sometimes a funder. The coordinator confirms the assignment; the receptionist prepares the request with person served, requester, location and access constraints. |
| Update | Zenvox native mode | A replacement or a schedule change is decided by somebody at the agency. Visit and absence events are unverified; without them, a driven change would leave no reliable trail. |
| Cancel | Zenvox native mode | A missed visit has care consequences. The cancellation is taken, time-stamped and escalated to the agency on-call line. The visit stays marked uncovered until a person has explicitly picked it up. |
What is included, what needs an add-on
Answering, telling the person served apart from requester and payer, applying your roles sheet, collecting availability and access constraints, and escalating an absence all sit in your healthcare base. Coordinating a multi-visit pathway and running recalls are named add-ons.
The authorisation, and what holds the truth
Here the most important authorisation is not technical: it is that of the person on the line.
- The roles and permissions sheet is written before day one: who may ask for what, on whose behalf
- An unauthorised relative is heard with respect, but no schedule change and no care detail is confirmed to them
- Zenvox asks for no credentials; while no access contract exists, no data from your platform is read
- The coordinator confirms assignment and service scope; the receptionist gives no clinical advice
- A worker absence raises the on-call alert, and the visit stays open until a person explicitly picks it up
Early morning, the agency office is closed. The daughter of a client calls. No platform data is read.
CallerHi, it is about my mother. Her worker was supposed to come this morning and she has not arrived.
ReceptionistLet me take your name, your relationship to her and a callback number, then your mother name and her address.
ReceptionistI am sending this to the agency on-call line right now. I cannot confirm a replacement myself: the coordinator assigns it, and they will call you back.
The on-call line gets the alert with person served, requester, relationship, address and time. The visit stays marked uncovered. Nobody promised a worker the agency had not yet assigned.
When the access contract is not there
That is today status, and the service runs fully in Zenvox native mode.
- The request is created inside Zenvox with person served, requester and payer kept distinct
- Your roles sheet filters what may be said to whom, and the instruction is applied as written
- An absence triggers escalation to the on-call line, with the time and content of the call
- You find the call, its transcript and its reason in the app
- No capability in your base depends on the scheduling platform
Questions about this connection
Does Zenvox read the care plan?
No: while no access contract exists, no data from your platform is read. External public documentation cites a care plan and a scheduler, but reading and writing visits, assignment and exact status remain to be confirmed.
Who may ask for a change on behalf of a client?
That comes from your roles and permissions sheet, written before day one: who may ask for what, on whose behalf. An unauthorised relative is heard with respect, but no schedule change and no care detail is confirmed to them.
What happens if a worker misses a visit?
The absence raises the on-call alert, with the time and content of the call, and the visit stays marked uncovered until a person explicitly picks it up. A missed visit has care consequences, so nothing closes itself.
Does the receptionist schedule the visit?
No. Scheduling a visit commits a qualified worker, physical equipment and sometimes a funder. The coordinator confirms the assignment; the receptionist prepares the request with person served, requester, location and access constraints.
What is the status on this page based on?
On documentary research retained from an earlier pass that was not re-checked, and on the absence of an access contract. It is given for what it is, and it tightens as soon as real access is obtained.
Where to next
See the practice concerned, or the full list of software studied.
AlayaCare