Handle more patient-contact work without adding pressure to your frontline team.

Defined patient-contact work: answering an inbound request, preparing a review before a clinician sees the patient, running a scheduled check-in between appointments, or confirming whether a patient on a list still needs to be seen.

A worker holds the conversation, gathers what the service needs and completes the actions its approved pathway allows. What comes back is a completed action or a structured record in the system your team already uses.

No. An Auxilis worker does more than answer a question, collect a form or route a call.

It holds the patient conversation, follows the pathway your service has approved, gathers the information required and can complete permitted actions in the systems your team already uses. The result is work completed — or a structured handover when a person needs to take over.

The worker cannot simply decide to do something outside that pathway.

No. A worker adds capacity alongside the existing team, not in place of it, and takes on routine patient-contact work that would otherwise consume their time.

The people stay in control. What changes is how much of their day has to be spent carrying out predictable, repeatable conversations and administration.

Anything outside the approved pathway goes to the appropriate person with the information already gathered.

No. A worker can gather information, ask the questions defined by an approved pathway and prepare a structured picture for the responsible team. It can also complete administrative actions where the pathway allows.

It does not diagnose, prescribe or make clinical decisions. When clinical judgement is required, the worker hands the patient or the information to the appropriate healthcare professional.

The worker presents the picture. A healthcare professional decides what happens next.

It hands over.

Every worker has defined boundaries and escalation conditions. If a request falls outside its approved pathway, needs human judgement or reaches a point where the worker must stop, it routes the interaction to the appropriate team with the information already gathered.

The aim is not to make the AI handle everything. It is to let it complete the work it has been approved to do and bring in a person when they are actually needed.

Yes. Patients are told at the start of the conversation that they are speaking with an AI assistant.

They are not expected to mistake a worker for a person, and where a patient wants or needs human help, the worker follows the service’s configured route for handing the interaction to the team.

Yes. Jackie answers inbound patient calls in NHS general practice today and proves the model the other Auxilis workers are built on.

We publish measured results from live deployments, including what Jackie handled, how much work was completed without reception involvement and how much call-handling capacity was returned to the practice team.

Auxilis workers are designed to work inside the telephony, messaging, clinical and operational systems your team already uses, rather than creating another interface for them to manage.

The exact integrations depend on the worker and pathway. Auxilis assesses the systems involved as part of deployment and connects the actions and records the worker needs to complete its approved job.

Yes. A recorded patient call with Jackie is published in full — including the moment she reaches a request she cannot complete and hands the patient to a person.

You can hear how the conversation works before speaking to anyone at Auxilis.

Start with one defined pathway, not everything at once.

Auxilis works with your service to define the conversation, what the worker needs to gather, what it may complete and where it must hand over. We then configure, connect and test it against that pathway before it handles live patient contact.

You can expand from there when the evidence, your systems and your governance requirements support it.