Verify the request
Run the configured identity and permission checks before showing appointment details.
AI workforce orchestration · Use case
Help patients complete the next administrative step
A governed patient access workflow for administrative questions, appointment changes, and clinic-approved information, with clinical matters owned by staff.
WHAT STARTS THE WORK
A patient asks for an appointment or an administrative update.
AI agents
- Access worker
- Scheduling worker
- Clinical contact router
- Clinical staff
- Access supervisor
Workflow steps
- Identify the requestAccess worker
- Route clinical contactClinical contact router
- VerifyAccess supervisor
- Answer or offer a choiceScheduling worker
- Check the change and notificationScheduling worker
- Resolve exceptionsScheduling worker
4 operating rules · 4 decision rules · 4 channels · records to verify
THE RESULT TO CHECK
An accepted scheduling request or qualified-staff handoff with its confirmation status recorded.
On this page
The operating problem
Access teams spend time repeating clinic hours, directions, required documents, and appointment-change steps. Voxistry coordinates an AI workforce with staff, clinic-approved information, and appointment systems so routine requests have a clear path and follow-up is visible when a change or notification needs attention.
- Patients wait while staff move between scheduling, patient administration, approved information, and the phone.
- Appointment changes need a dependable record and a separate check that the patient notification was delivered.
- Clinic-approved directions, hours, and required administrative documents are repeated across channels and can become inconsistent.
Fictional example: changing a Tuesday appointment
In this fictional scenario, a patient asks to move a Tuesday appointment. The workflow offers an available choice, records the saved appointment change, and checks notification delivery separately.
Offer a choice
Show an available time for the permitted appointment type; availability alone is not a booking.
Confirm the saved change
Record whether the appointment change was saved in the scheduling system, then check whether the patient notification was delivered.
Keep failures pending
If the message fails, the appointment change may still be saved; follow up with staff rather than retrying the appointment change blindly.
Who handles the work
Example division of work between AI workers and your team.
Access worker
Answers administrative questions using clinic-approved directions, hours, required documents, and service information.
- Approved administrative information
- Acts within policy — clinic-approved information only
Scheduling worker
Shows choices for an agreed appointment type and requests permitted changes; checks that the appointment system saved the change separately from notification delivery.
- Permitted appointment administration
- Acts within policy — agreed appointment types and tested permissions only
Clinical contact router
Flags clinical, symptom, medication, triage, and safeguarding language for the qualified staff path.
- Clinical contact routing
- Acts within policy — staff review owns judgement and urgency
Clinical staff
Takes clinical questions, symptom descriptions, medication questions, triage, and safeguarding disclosures.
- Clinical judgement and safeguarding
- Full authority
Access supervisor
Reviews routed contacts, failed saves, notification status, and approved information for policy fit.
- Access governance and review
- Full authority
How the work could flow
Use this sequence to agree the workflow and test each step before launch.
Identify the request
Is this an administrative request supported by approved content, or does qualified staff need to assess it?
Route clinical contact
Has the contact raised urgency, symptoms, medication, triage, safeguarding, or another clinical matter requiring qualified staff? If staff are unavailable, use the agreed fallback.
Verify
Has the configured identity and permission check passed for the requested administrative detail or change?
Answer or offer a choice
Is there clinic-approved information or an available appointment choice for the agreed appointment type?
Check the change and notification
Was the appointment change saved in the scheduling system, and was the patient notification delivered? Keep these confirmations separate.
Resolve exceptions
Did the save, identity check, or notification fail, or is staff unavailable? Create the agreed staff follow-up with the available context.
Decisions your team keeps
Proposed operating requirements to configure and verify, including what happens when a system or human handoff is unavailable.
- Clinical, symptom, medication, triage, and safeguarding contacts leave the administrative flow for qualified staff judgement.
- Workers provide clinic-approved administrative information and do not provide medical advice or make clinical assessments.
- Agree and test the information access, identity checks, and permissions required for each task with the clinic and system owner.
- An available appointment choice is not a booking. Check whether the appointment system saved the change and whether the notification was delivered as separate results.
- Role-limited knowledge with clinical content excluded from worker scope.
- Clinical contact routing to qualified staff, with staff-owned triage, symptoms, medication, and safeguarding judgement.
- Task-scoped data access, identity, and permission checks that are agreed and tested before use.
- Separate records for available choices, saved scheduling changes, notification delivery, and staff follow-up on failures or unavailable staff.
Systems & channels
Systems to connect
Scope these around the selected implementation.
- Scheduling system
- Patient administration system
- Reminder & messaging gateway
- CRM
Channels to evaluate
Select and validate the required provider pathways.
- Voice
- Web chat
- SMS
What to measure
Pilot measurement definitions, not claimed customer results.
Access rate
Measures whether administrative contacts receive clinic-approved information or a staff handoff, with unresolved and failed paths visible.
Appointment completion
Track choices offered, changes saved in the appointment system, and notifications delivered separately; an available choice is not a booking.
Staff handoff
Reviews clinical, symptom, medication, triage, and safeguarding referrals for the right staff owner and complete context.
A bounded rollout
Baseline administrative contacts
Start with clinic-approved directions, hours, and required administrative documents. Measure repeat contacts and unanswered requests, and test staff acceptance and the fallback when no one is available.
Test one appointment type
Offer choices and permitted changes for one agreed appointment type. Check separately that the appointment system saved the change and that the notification was delivered, with staff follow-up for failures.
Widen from measured evidence
Add another agreed appointment type or exception path only when routing, saved changes, notification delivery, staff acceptance, fallback handling, and patient-reported measures support the change.
Questions about this workflow
AI WORKFORCE ORCHESTRATION FOR ENTERPRISESBring one business process.
Request a demo