For hospitals
Know who is still waiting — without phoning the whole list.
Auxilis builds governed AI workers for elective, outpatient and specialist teams. Robin validates waiting lists and confirms attendance; Joe maintains treatment follow-up between appointments. Each conversation returns a structured outcome to the systems you already use — and clinical, distressed or ambiguous cases go to a named person on your team.
Validates and maintains elective waiting lists by personalised text with phone follow-up — confirming who still needs care, checking attendance early enough to protect capacity, and capturing relevant changes in condition or circumstances. Every contact returns a structured outcome to your PAS or validation workflow.
Further reading
How voice validation works on an elective waiting list Why DNAs behave like a second waiting listRuns scheduled check-ins with patients on specialist or high-cost therapies, capturing adherence, side effects and concerns for the responsible clinical team — so follow-up doesn’t disappear between appointments. Joe does not diagnose, prescribe or change treatment.
Further reading
What structured adherence follow-up involvesThe worker presents the picture. Your team decides what happens next — the worker never reprioritises a patient or makes a clinical risk decision.
Common questions from outpatient and elective teams
How does waiting list validation actually work?
Robin contacts patients on an elective waiting list by personalised text, with phone follow-up for anyone who does not reply. Each conversation confirms whether the patient still needs care, captures relevant changes in their condition or circumstances, and returns a structured outcome to the trust’s existing validation workflow.
How voice validation works on an elective waiting list What happens to patients who do not respond?
Robin tries more than once. You set the timings of those attempts and the maximum number to make, and a patient is only marked as not responding once those attempts are used up.
Spreading the attempts across different times of day, instead of repeating one, reaches the patients who are at work or in appointments when the first call lands.
Does this integrate with our PAS?
There is no fixed list of supported systems. Auxilis builds the integration per service, wherever the system offers an API and meets the interoperability requirements the NHS expects, so results land in the workflow your team already uses.
Auxilis works through the specific systems your trust runs before anything deploys, alongside your governance requirements.
Who decides whether a patient comes off the list?
The trust does. An Auxilis worker never reprioritises a patient and never makes a clinical risk decision. It gathers what the patient reports, records it and returns that to the responsible team, who decide what follows.
Can we start with a single speciality?
Yes, and that is the recommended way in. One speciality or one cohort produces a real result on your own patients before anything widens, and it keeps the first governance conversation to a scope your team can actually review.
Start with one cohort.
Begin with a defined speciality, your longest waiters or a single therapy programme. We’ll evaluate the worker against your systems, governance requirements and agreed operational measures before extending to further cohorts.