Providers & support coordination
A check-in call that actually happens, every day.
Welfare checks and roster changes are high-frequency, low-complexity calls to people for whom a missed call has real consequences. They are the first thing dropped when staff are short.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a aged & disability care organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Aged & Disability Careyour systems of record
Care managementclients, plans, goals
Rosteringshifts and support workers
Incident systemreports and escalation
Funding / claimsplan budgets and claims
Family contactsauthorised representatives
Only the bottom layer is specific to aged & disability care. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
Check-ins stop being the thing that gets skippedThey happen on schedule regardless of roster pressure, which is precisely when they matter most.
Deterioration is noticed earlierA consistent daily conversation surfaces change that a fortnightly visit does not.
Families are informed without extra staffingRoster changes reach the people who need to know, every time.
Coordinators spend their time on escalationsNot on confirming that tomorrow is still Tuesday.
What the agent actually does
Daily welfare check-insA short, consistent conversation, with anything concerning escalated to a coordinator immediately and recorded.
Roster changesTell the client and the family when a support worker changes, and confirm they heard it.
Appointment and transport remindersOutbound reminders with rescheduling handled in the same call.
What keeps it deployable
No clinical or care adviceA hard boundary; anything clinical transfers to a qualified person immediately.
Distress escalationDetected distress ends the script and reaches a human, and the transfer is auditable.
Consent and representativesWho may be told what is enforced from the care record, not assumed.
A daily check-in is only protective if it actually happens on the days when staffing is worst.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.