Appointment requests for your clinic.
Explore an AI voice or chat pilot for private hospitals, specialist clinics and surgery centres. Start with appointment requests and reception questions, with a clear route to your clinical team.
Discuss your clinic's callsAppointment requests during a busy shift
Reception handles arrivals, calls and changes to the schedule. Appointment requests need a clear record; clinical questions need the right member of your team.
- Example
A patient asks for an appointment
Someone wants a follow-up visit while reception is checking in another patient. A contact number and preferred time give staff the details they need to respond.
- Example
A patient needs to move a visit
The request identifies the appointment and a contact number. It stays pending until the clinic confirms the change.
- Example
A patient asks about preparation
A question about medication or preparation for a procedure belongs with the clinical team. Reception needs an approved contact route for that question.
Appointment requests for staff to confirm
A first pilot can cover one reception task, using your questions and appointment rules. Your team decides which requests it can accept.
New requests
A name, contact details and preferred time prepare the request for reception. Staff confirm the appointment unless a calendar connection has been agreed and verified.
Changes and reminders
Identify the visit a patient wants to move or cancel. If reminders are included, their timing, permission and administrative wording follow the clinic’s approved rules.
Waiting-list requests
A patient can ask for an earlier appointment without losing the current one. Your team reviews the request before offering an opening.
Patient information and clinical boundaries
Appointment details and clinical information need different handling. Before real patient use, we agree on the fields, access and route to your clinical team.
Administrative details
The proposed intake covers approved appointment fields. Medical histories, test results and symptom assessment remain outside this workflow.
Access and retention
Your clinic defines who needs access, whether calls should be recorded and how long records should remain. Those requirements need confirmation in the selected service before use.
Review with your privacy advisor
Your team and its advisors need to review the applicable requirements, notices and provider agreements. The pilot does not establish your clinic's compliance.
Details a patient shares unexpectedly
Patients may volunteer sensitive information. Recording and transcript controls need specific review; avoiding clinical questions alone does not keep those details out of stored records.
Urgent and clinical requests
This pilot is not an emergency or triage service. Your clinical team must approve the referral wording; do not rely on an automatic transfer for urgent care.
Common questions
Does it replace my receptionist?
The proposed pilot covers a defined administrative task. Your reception team still confirms exceptions and handles patients who need personal attention.
Does it handle clinical questions?
Clinical advice, diagnosis, prescriptions and interpretation of results are outside this pilot. Agree on where those questions should go.
What if a caller describes an emergency?
The pilot is not an emergency contact route. Review the message and referral path with your clinical team before launch, including what happens if nobody answers.
Which patient languages can we include?
Tell us which languages your patients use. Each language and any human support needed must be selected and tested for your pilot.
Can we use our current calendar?
We first review its permissions and connection options. Until a booking connection passes testing, an appointment request needs staff confirmation.
When could the pilot start?
The schedule depends on the task, system access, privacy review and testing. We can discuss those requirements in the first conversation.