Dot's Thursday, door to door.
The call
Dot · demo clientKate · the engine
voice into actionAround Dot
ride · family · nurseSimulated demonstration. No real call, text, booking or ride happens on this page. Dot, her family, the drivers and the nurse are made-up demo characters, and no transport provider is named or implied.
A ride is care too.
Mary hears the worry. Kate checks the care plan and books the ride. The client decides, and the people who need to know are told, with permission.
- 1The worry is heard early.Routine calls are where people say they are stuck. Kate matches it to the appointment already on the care plan.
- 2Mobility needs travel with the booking.A walking frame, door to door help or a ground floor pickup reach the driver as part of the request.
- 3The client says yes, twice.Once to book and once to confirm the read-back, and again before anyone in the family is told.
- 4Late is handled, not discovered.If a driver misses the pickup window, Mary calls within a minute while Kate rebooks and warns the clinic.
- 5The appointment is not the end.Mary asks how it went. A changed tablet goes to the nurse and pharmacy before the next dose.
Getting there safely.
Booking a vehicle is the easy part. The care is in everything around it.
Door to door, not kerb to kerb
Frames, walkers and wheelchairs are recorded in the care plan and passed to the driver, so help starts at the front door.
No yes, no booking
Nothing is booked on a guess. Each yes is recorded on the case, with the time and how it was given.
Budgets respected
Rides stay inside the budget the care manager has set, so there are no surprise charges for the client or the family.
A plan for the bad morning
If a driver is late or cancels, a replacement is requested at once and the clinic is told before the client is late.
Family told with permission
Mary asks before she texts anyone, and keeps messages short, calm and factual.
Outcomes are captured
If the doctor changes a medicine, that goes to the nurse and pharmacy, so the pack is right before the next dose.
What a request looks like.
One structured request per trip, with only what is needed to deliver safely. This is a simulated example for discussion.
// transport_request (simulated) { "event": "transport_request", "simulated": true, "client": { "first_name": "Dot" }, "trip": { "pickup_window": "Thu 9:30 to 9:45", "pickup_place": "client's door (address released at dispatch)", "destination": "Hip clinic", "appointment": "10:30 am", "return": "on request" }, "mobility": { "aid": "walking frame", "help": "door to door", "wheelchair_access": false }, "funding": { "source": "client budget", "cap": "set by care manager" }, "authorised_by": { "client_yes": "by voice, 2:20 pm" }, "signature": "signed by careplans AI" }
- →Accept, propose another time, or decline.Kate tells the client, the family and the care team, in plain words.
- →Status as the trip moves.Assigned, on the way, picked up, arrived and home. A delay event lets Kate act within minutes.
- →One return request.The client asks when ready, and Kate books the ride home against the same trip.
- →The same rail as meals and medicines.Transport, food and pharmacy share one governed flow, so a single conversation can set several things moving.
A ride, handled well.
The goal is simple: when someone says they cannot get to an appointment, a safe ride is arranged within minutes, and everyone who needs to know is told.