Voice and back-office work for NDIS care.
The work behind the workflow.
Staff called support workers each week to confirm appointments, capture changes and update the scheduling system by hand. A missed confirmation could become a missed shift.
Behind the calls, staff moved between systems to check records, apply business rules, trigger follow-ups and document outcomes. That administration grew with the organisation.
How the work moves.
- 01
Call the support worker
A voice agent calls the assigned worker to confirm the participant, date, time, location and service type.
- 02
Classify the answer
The model classifies the response and assigns a confidence level. Clear confirmations update the schedule.
- 03
Escalate uncertainty
Ambiguous, sensitive or non-attendance responses go to the rostering team with a transcript and recommended next action.
- 04
Receive back-office work
Operational systems, staff requests and scheduled checks feed non-voice tasks into the automation layer.
- 05
Run repeatable tasks
Bots check records, route requests and move data using defined rules. Copilot-enabled workflows prepare context for staff.
- 06
Keep approvals with staff
Routine actions run automatically. Sensitive decisions, exceptions and approvals stay with people.
What the case study reports.
The 300+ deployment count is a reported achieved result. The voice workflow results are described capabilities. The sources publish no measured time savings, cost savings or attendance improvement.
- More than 300 robotics and RPA processes deployed across the back-office program, as reported by Human Nexus.
- Routine shift confirmations can be written back to the scheduling system without manual entry.
- Uncertain call responses reach staff with a transcript, classification, confidence score and recommended next action.
The counterpart handles repeatable calls and administration. Staff keep sensitive participant decisions, approvals and anything that needs judgement.
Adapted from two published Human Nexus case studies in care: voice AI workforce scheduling and 300+ automation processes. Client names are withheld. Figures are not independently validated here, and this account does not claim a separately deployed Counterpart product or a recorded staff voice.