Keep the final say
The sample review puts the next step with reception, not an automatic booking. Your team checks the request before deciding how to respond.
For specialist practices
Explore a considered approach to online specialist appointment requests. An easier starting point for patients. The final say stays with your practice.
An appointment request
Patient-side illustration
Booking requests
A sample request
Returning patient · preferred time
Confirm · Offer another time · Ask for more · Decline
How it works
Follow the intended path from patient preference to practice review. The sample illustrates the workflow; real intake and live messaging are not active.
Patient chooses
Explore choosing a specialist, a new or returning visit, and a sample time. Live practice availability is not connected.
Details in context
The planned intake brings practice questions, mobile verification and a GP referral into one request. Real intake is disabled until referral safety scanning is connected.
Your team reviews
Explore a sample review: confirm, offer another time, ask for more or decline. A request is never a confirmed appointment.
The designed workflow
Booking requests need more than a time picker. Explore a workflow shaped around the checks, choices and follow-up of a specialist practice.
Sample previewThe sample review puts the next step with reception, not an automatic booking. Your team checks the request before deciding how to respond.
The queue is designed to highlight requests waiting more than four opening hours, so closed evenings and weekends don’t count towards that priority.
The patient flow is designed for embedding on your practice website. Explore the sample journey here before configuring a live practice setup.
The designed workflow uses approved messages for updates and optional day-before reminders. Live email and SMS require publishing and verified senders.
A few useful answers
A clear view of what’s in the sample and what still needs to be connected.
No. This is a sample preview, not a live intake service. Real request submission is disabled on the server because a genuine referral malware scanner is not connected. Please use fictional details only in the sample. Publishing alone does not enable real intake.
No. The walkthrough uses sample times, not availability from your practice’s booking system. A separate practice-system connection is needed for live times. Nothing is booked simply because a patient chooses a time or sends a request; reception retains the decision.
No. AI referral reading is off. The intended workflow helps reception review referral details, but it needs the practice owner’s model-tier choice and a working referral safety-scanning flow before it can be enabled. The sample does not demonstrate a live AI assessment.
Live email and SMS need a published app, practice configuration, a verified sending domain for email and an approved, verified SMS sender ID for texts. The intended optional day-before reminder includes the practice phone number so patients can call to change or cancel. This sample does not send live patient reminders.
The intended setup embeds the patient request flow on your existing website, with your practice details and approved website origins configured. Reception and practice managers use a separate signed-in workspace. Live intake, referral scanning and availability connections still need to be completed before using it with patients.
Request access
Book a 30-minute conversation with Nimesh to discuss Bookings by Akuru and access for your practice.