For a clinic
Coordinate appointment enquiries, administrative requests, preparation information and patient follow-up.
A better patient experience.
A more coordinated operation.
VOCA gives patients an Arabic- and English-speaking coordinator that answers from approved information, performs authorised actions through connected systems, and brings staff in when their expertise is needed.
Proposed capabilities. What follows describes what VOCA is designed to offer clinics and hospitals. Each capability is enabled according to the organisation’s integrations, operating policies and clinical approvals, and is marked available, request-only, awaiting connection or awaiting approval. Today, VOCA records appointment and administrative requests for your team; live booking and access to patient systems are scoped per project.
01 / One front door
One front door for patient services.
Patients should not need to understand your organisation to get help. They explain what they need in their own words, by voice or text.
| Patient need | The experience VOCA can provide |
|---|---|
| “I need an appointment.” | Find the requested service, explore available appointments where connected, read back the details, and confirm only after the booking succeeds. |
| “I need to change my visit.” | Verify the caller, check the existing booking, and arrange the change without releasing the original appointment too early. |
| “What should I bring?” | Give the clinic-approved documents, arrival information and preparation instructions for the visit. |
| “Are my results ready?” | After appropriate verification, share the permitted availability status and the approved collection or access process. Never the results themselves. |
| “I need a refill or a letter.” | Record the request for the responsible clinical or administrative team, with a reference and an expected next step. |
| “I have a billing question.” | Explain approved billing information, retrieve permitted account details, or provide a payment link through a connected system. |
| “I need to speak to someone.” | Offer a staff handoff with the conversation context, or explain the callback process and real availability. |
Patients get clarity. Staff get structured requests. Management gets visibility.
02 / Appointments
Every enquiry reaches a visible outcome.
VOCA supports the administrative journey from the first enquiry to a confirmed appointment.
- Explain approved services, doctor profiles, locations and published prices
- Capture preferences, referral requirements and new-or-returning status
- Offer live availability where the scheduling system supports it
- Record appointment requests when direct booking is unavailable
- Support cancellation, rescheduling and waiting-list workflows
- Send authorised confirmations and preparation information on enabled channels
- Support consented reminders and follow-up on missed appointments
Every enquiry ends in one ofIllustrative
BookedThe connected system recorded success.
Awaiting staffA request is with the team, with an owner.
Waiting listThe patient is contacted when a slot opens.
DeclinedWith a stated reason.
UnresolvedStill has a named owner.
This shows where demand is served, and where patients are still waiting.
03 / Your staff
A useful starting point, not “please call the patient”.
A structured request helps someone act. The staff workspace should bring together:
| What staff see | Why it matters |
|---|---|
| Reason for contact and requested service | The receiving team knows what the patient needs. |
| Verified identity and access status | Completed checks are distinguished from checks still required. |
| Relevant details already collected | Patients do not have to start again. |
| Actions attempted and their results | Staff can see whether a booking succeeded, a system failed or approval is pending. |
| Assigned owner and response deadline | Requests have accountable next steps. |
| Handoff acceptance status | Sending an alert is distinguished from someone accepting the request. |
| Conversation summary and authorised history | Context is recovered quickly. |
| Internal notes and takeover controls | Teams can coordinate and continue the conversation. |
Overdue or unaccepted requests escalate according to the organisation’s policy.
04 / Clinic or hospital
The needs of a clinic, and the complexity of a hospital.
Each department can have its own approved knowledge, permissions, working hours, escalation contacts and service commitments.
For a hospital
The same foundation extends across departments and locations, with approved routing, hours and escalation for each.
Central enquiries and switchboard
Approved department routing, opening hours, entrances and contact pathways.
Outpatient services
Scheduling support across specialties and facilities.
Diagnostics
Laboratory and imaging appointment coordination, with approved procedure-specific instructions.
Admissions
Authorised pre-registration and administrative document collection.
Visitor services
Visiting hours, access rules, parking and directions.
Patient-location enquiries
Only where disclosure is authorised and supported by hospital policy.
Medical records
Requests for copies and documents, routed through the appropriate release process.
Discharge follow-up
Approved questions, with escalation to the responsible clinical team.
Recurring-care administration
Authorised reminders for scheduled reviews and tests.
Routine transport coordination
Requests passed to the responsible service, confirmed only when accepted.
05 / Safety
Safety is part of the workflow.
VOCA’s role is administrative coordination and approved information. Clinical decisions stay with authorised professionals.
VOCA does not diagnose, interpret results, recommend medicines or approve prescription refills.
When a caller describes a potentially urgent concern, VOCA follows a clinically approved escalation protocol. It does not imply that it can recognise every emergency, and it does not delay emergency guidance while waiting for identity checks or a staff response.
Approved information
Named owners review service information and patient instructions.
Verified action results
“Confirmed” means the connected system recorded success.
Read-back before consequential changes
Callers review key details before authorised actions proceed.
Identity and authority checks
Access depends on who the caller is and what they are permitted to do.
Minimum necessary disclosure
Spoken messages and notifications avoid unnecessary clinical detail.
Defined fallback behaviour
Unavailable systems or unanswered handoffs lead to an explicit next step.
Traceable activity
Authorised staff can review what was requested, attempted, completed and escalated.
Human control
Staff can take over according to the service’s operating model.
Clinical wording, privacy rules, recording practices, retention and communication policies require approval for the intended deployment.
06 / Language and channels
Arabic and English, with continuity across channels.
Patients use the supported language and channel that works for them.
- The intended experience is consistent across phone, web chat and approved messaging channels: the same service rules, the same access controls and the same accountable requests
- Language quality is tested against real conditions: regional accents, mixed Arabic and English, names, appointment dates, interruptions and background noise
- When a patient moves between channels, context is preserved only after identity-linking checks. Recognising a phone number alone does not unlock sensitive information
07 / Leadership
An operational view for management.
The management dashboard should answer practical questions.
| Management question | Useful measurement |
|---|---|
| What are patients asking for most? | Ranked services and request categories, including unclassified requests. |
| When is demand highest? | Hourly usage and day-of-week patterns in the organisation’s local timezone. |
| Where are appointment enquiries getting stuck? | Requests progressing to confirmed bookings, with unresolved reasons. |
| Which teams need attention? | Unassigned, unaccepted and overdue requests by department. |
| How quickly are requests handled? | Median and slower-case acceptance and completion times. |
| Where does staff intervention occur? | Handoff reasons, acceptance rates and completion status. |
| Which systems are disrupting service? | Booking errors, failed actions, delivery failures and connection health. |
| How do facilities compare? | Volumes and service measures by site, with workload differences made visible. |
| Are patients attending? | Cancellations and no-shows, where reliable attendance data is connected. |
| What do patients think? | Collected feedback, complaints and survey responses. |
No invented numbers. No invented satisfaction scores, assumed revenue or unsupported claims of time saved. Business impact is measured against an agreed baseline.
08 / Rollout
Start with a focused, measurable deployment.
A credible rollout begins with a defined service and expands after its performance is shown. The organisation chooses the scope.
| Stage | Scope | Evidence required before expansion |
|---|---|---|
| 1. Patient-services pilot | One clinic or department; approved FAQs, appointment requests, administrative requests and staff handoffs. | Accurate information, complete requests, reliable ownership, and successful Arabic and English testing. |
| 2. Connected scheduling | Live availability, booking, rescheduling, cancellation and authorised confirmations. | Verified calendar writes, duplicate prevention, failure recovery and clear appointment status. |
| 3. Connected patient administration | Selected billing, records-request, results-availability and identity workflows. | Access-control testing, auditability and approval of each data flow. |
| 4. Multi-department expansion | Additional facilities, switchboard routing and approved follow-up programmes. | Department readiness, escalation coverage and measured service performance. |
Each capability is explicitly marked as available, request-only, awaiting connection or awaiting approval.
09 / Success
What a successful pilot should show.
Before launch, agree the baseline, the targets and the measurement method. Then evaluate whether VOCA:
- Helps more enquiries reach a documented next step
- Captures the details staff need to act
- Reduces repeated administrative work
- Keeps appointment and request status accurate
- Routes unresolved work to an accountable owner
- Handles system failures and urgent concerns according to approved procedures
- Provides a usable experience in both Arabic and English
- Gives management evidence for deciding whether to expand
Financial impact can then be assessed from observed booking outcomes, measured staff effort and actual operating costs.
Start with one service
From the first enquiry to a verified outcome.
Tell us your clinic or hospital and the first service VOCA should handle. We’ll scope a pilot around it.