Skip to main content

Appointment Requests or Instant Booking? Choose and Explain the Right Mode

Use instant booking when the service, current capacity and acceptance conditions can be resolved reliably at the time of booking. Use a request workflow when an identified person must review a genuine unresolved condition. In either mode, show whether the patient has a request, an offer or a confirmed appointment. Payment acknowledgement, form receipt and a message delivery badge must not substitute for appointment confirmation.

By Bractis · Updated · 8 min read

Indian clinics choosing online booking modes for routine OPD, visiting consultants and services needing individual review.

Choose the mode from the unresolved decision

Instant booking is useful when the patient can select a suitable service and the system can commit a real slot under known terms. It reduces a handoff, but only when the underlying schedule and capacity are dependable. Publishing an attractive calendar does not make a visiting doctor's attendance or a required room certain.

Request-for-approval is useful when a specific decision genuinely remains: the service needs staff coordination, a visiting session is not yet confirmed, or a clinician must decide an appropriate pathway. Name that decision and its owner. A request queue should not be a permanent workaround for a calendar nobody maintains.

A single clinic can use different modes for different services. Explain the difference before the patient submits. Someone selecting a routine consultation should not discover after paying that they only joined a general enquiry list. Conversely, a request interface should not promise a fixed visit before the relevant review has occurred.

Write the patient-facing meaning of every state

List the steps from selection to the final appointment. A request can be received without being reviewed. Review can result in an offer of a different time. The patient may need to accept that offer before the reservation is final. These distinctions need clear language in the page, message and reception view.

Use the same meaning across channels. If reception says 'confirmed' while the website says 'pending', the clinic has not defined a coherent process. Staff should be able to identify the accepted date, doctor, branch, service and any remaining conditions from one record.

W3C's form-notification guidance calls for understandable success and error feedback. Applied here, a successful request submission should say that a request was received; it should not use success styling to imply the larger task of booking has finished. This state model is an original operational application, not a claim that a UI badge meets an accessibility standard.

On a narrow screen, scroll the table horizontally to read all columns.

A booking-state contract patients can understand
StatePatient-facing meaningResponsible next action
Request receivedYour request is recorded; an appointment is not yet confirmed.Named staff member reviews the stated condition.
Needs informationA defined question prevents the review from finishing.Explain what is needed and provide a supported reply route.
Alternative offeredA specific alternative is available under stated terms.Patient accepts or declines within the defined arrangement.
Appointment confirmedThe accepted service, doctor, location and time are recorded.Send a clear confirmation and preserve current capacity.
Unable to accommodateThe requested arrangement cannot be provided.Explain the outcome and appropriate next options.
Cancelled or expiredThe defined request or booking is no longer active.State whether money or another appointment remains unresolved.

Source: W3C WAI: User Notifications

Staff the promise made by a request workflow

Publish the actual review hours and an expectation the clinic can meet. 'We will contact you shortly' is unhelpful when a request arrives on a holiday and the visiting consultant is not due for a week. A request received outside monitoring hours needs truthful guidance, not an implied continuously staffed service.

In a fictional workload estimate, 24 requests each need four minutes of administrative review, or 96 minutes. Six of them also require a five-minute clarification call, adding 30 minutes. The total is 126 minutes. If only 90 minutes of staff time is available, a daily backlog is predictable even before interruptions.

Adding a request mode therefore creates a staffing decision. Reduce the avoidable review step where possible, adjust the promise or allocate capacity. Do not meet a dashboard target by approving requests without resolving the actual condition. Track the oldest unresolved request and why it remains open, not just how many arrived today.

Treat payment and capacity as separate evidence

A payment can be pending, accepted or refunded while the appointment has its own status. Decide exactly when capacity is held and for how long, and what happens if the payment result arrives late. The patient needs one intelligible outcome, but the underlying records must preserve both facts.

Test a payment acknowledgement after a hold expires, an accepted booking whose confirmation message fails, and a retry after the final page times out. A clinic should be able to recover the existing outcome without asking the patient to pay again or creating another reservation just because a receipt screen was lost.

Do not present an administrative approval as clinical suitability. The responsible clinician decides whether an in-person or remote service is appropriate where that judgement is required. A form that asks for symptoms is not automatically a triage assessment, and a patient reporting urgent needs should not be told to wait for an ordinary approval queue.

Keep changes explicit when the original request cannot be met

If the requested doctor or time becomes unavailable, offer the alternative clearly rather than silently changing the accepted request. A different branch may add substantial travel. A different clinician or visit mode may be unacceptable to the patient even if it looks equivalent in the calendar.

Retain the original request and the later decision as related events. Record who proposed the change, what was communicated and what the patient accepted. When a telephone conversation resolves an online request, staff should update the same appointment process rather than leaving the digital request open to be handled again.

Expiry requires a definition. An unanswered enquiry, an unaccepted temporary offer and a confirmed booking that the clinic later cancels have different consequences. The interface should explain which event occurred and whether the patient still holds another appointment or has money awaiting resolution.

Evaluate the mode with complete journeys

Measure time from request receipt to a resolved outcome, separating staff waiting, patient clarification and unavailable capacity. A fast first acknowledgement is useful, but it is not resolution. Report declined or withdrawn requests alongside confirmations so a shorter queue cannot hide lost access.

Run a small trial before changing every service. IHI's testing approach supports observing changes under local conditions. Include reception cover, an after-hours request, a missed callback and a doctor-session change. A polished happy-path demonstration cannot establish how the clinic will handle those exceptions.

Keep the mode choice revisable. If staff approve nearly every request using rules that could be resolved at selection, instant booking may be worth evaluating. If automated confirmations frequently require later correction, investigate the underlying service or capacity model rather than simply adding more apology messages.

Source: IHI: Model for Improvement — Testing Changes

A fictional visiting-consultant request

A clinic has advertised a Saturday specialist session but is still confirming the consultant's travel. It collects clearly labelled requests without representing them as booked appointments. Once the session is confirmed, staff offer actual times through a defined acceptance process. A patient who cannot attend the offered time receives an explicit outcome and keeps any existing arrangement. The clinic does not use a payment receipt or the consultant's name on a calendar as evidence that an earlier appointment was already guaranteed.

Specify your appointment confirmation rules

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Decision map
For each service, identify what can be resolved at selection and what requires a person. Remove review steps with no defined purpose.
Patient contract
Write the exact meaning of request received, offered and confirmed across the website, messages and reception.
Capacity budget
Estimate review and clarification minutes against staffed time, then define a realistic coverage promise.
Exception trial
Test concurrent selection, lost confirmation, late payment, changed doctor and a patient declining the alternative.

Questions doctors ask

Is instant booking always better for a small clinic?

No. It is useful when the relevant service conditions and capacity can be resolved reliably at booking time. A request workflow may be appropriate for a genuine unresolved decision, provided it has an owner and an honest response process.

Can a successful request form say the appointment is confirmed?

Only if the appointment has actually reached the defined confirmed state. Otherwise it should acknowledge the request and explain the review and next step. Success of the form submission is a narrower event.

How quickly must staff approve an appointment request?

This guide establishes no universal deadline. Publish a service expectation based on actual review hours, staffing and the decision required, and provide an appropriate route for needs that cannot wait for that process.

Can staff move a request to another doctor or branch?

They can propose an appropriate alternative, but should explain the changed arrangement and record acceptance where required. Do not silently treat a different doctor, location or visit mode as the patient's original choice.

Sources and scope

Updated on . Original service-design analysis and fictional staffing arithmetic. No clinical triage, legal response deadline, payment integration or booking capability is inferred from the examples. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Compare one routine consultation with a visiting-specialist request. Ask Bractis to show the patient-visible states, review queue, capacity decision and recovery after a lost confirmation using synthetic appointments.

Request a clinic demo