Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Website

Slot Hold and Abandonment Logic in Online Booking: Why Patients Lose Their Slot at Step 3

A teardown of slot hold timers, OTP delays and mobile back-button loss in online booking flows, with the events to log and the decision rules to fix each one.

Slot Hold and Abandonment Logic in Online Booking: Why Patients Lose Their Slot at Step 3

Many hospital booking flows lose patients at the same place. The patient picks a doctor, chooses a slot, types their details and reaches the OTP step. Then something quiet goes wrong: the SMS arrives late, the patient switches apps to read it, comes back to a reset page, and the slot they chose is gone. They do not file a complaint. They call another hospital.

This teardown is for hospital digital heads, web product owners and developers who run or build online booking. It looks at the three mechanisms that cause most step-three losses: hold timers, OTP verification and the mobile back button. It is a method, not a set of results. We do not publish a benchmark for abandonment at each step because it depends on the audience, device mix and doctor demand. What you get is what to log, how to read the logs and what to change.

It assumes the basics from appointment booking optimisation and the form-level fixes in accessible clinic appointment forms. Here we focus on the state machine behind the form.

Map the flow as states, not screens

Draw the booking as states with timers, not as a sequence of pages. A typical flow has these states:

  1. Browsing: slots visible, nothing reserved.
  2. Held: the patient selected a slot; the system has reserved it for a limited time.
  3. Details entered: patient name, phone and reason are filled.
  4. Verifying: an OTP has been sent to the phone; waiting for entry.
  5. Confirmed: the booking exists in the scheduling system.
  6. Expired or released: the hold lapsed or the patient abandoned.

The bug pattern is nearly always a mismatch between the timer that governs the Held state and the real time the later states take. A 5-minute hold is fine if the patient types quickly and the SMS arrives in seconds. It is a trap if a first-time patient on a slow mobile connection takes 4 minutes to fill the form and the OTP takes another 90 seconds. (These numbers are hypothetical, chosen to illustrate the arithmetic.)

Failure one: the hold timer starts at the wrong moment

Ask three questions of your current flow.

  • When does the timer start? At slot selection, at form open, or at OTP request? A hold that starts at selection covers all the time the patient spends reading, typing and verifying.
  • Is it visible? A hidden timer produces a surprise failure at the final step. A visible countdown produces anxiety, but also warning. If you show one, show it from the start and say what happens at zero.
  • Does it extend? Extending the hold when the patient requests an OTP, or when they resend one, aligns the timer with the real task. Cap the total extension so one patient cannot hold a slot indefinitely.

A sound rule is to set the initial hold from measured completion time, not from instinct. Compute the 90th percentile of time from slot_selected to otp_verified for patients who did complete, then set the hold above that with a margin. Extend by a fixed amount on OTP request, and release the slot promptly on explicit abandonment (closing the tab cannot be detected reliably, so rely on the timer).

Also decide what an expired hold does. The worst outcome is a generic error at the end of a long form. A better one preserves the patient's typed details, shows the next free slots with the same doctor, and lets them select one without retyping.

Failure two: the OTP step

OTP verification protects against fake bookings, and it is also the point where the patient leaves your page. Four things commonly go wrong.

Delayed or missing SMS. Delivery depends on the SMS gateway and the carrier. You cannot control the carrier, but you can measure the delay: log otp_requested and otp_verified timestamps and look at the distribution, not the average. A long tail means a group of patients are sitting on a countdown they cannot beat.

Resend design. If "resend" is disabled for 60 seconds and the hold expires in 90, the patient has almost no recovery path. If resend generates a new code, the old code should either stay valid for a short overlap or fail with a clear message; otherwise a patient who types the first code that finally arrived is told it is wrong.

Switching apps. On a phone the patient may leave the browser to read the SMS. Mobile browsers can discard or reload the page in the background, and form state is lost. Where possible, let the page recover its state from the server using the booking attempt's ID.

Typing errors in the code. Use a numeric keypad (inputmode="numeric") and the HTML autocomplete="one-time-code" attribute, which lets browsers offer the code from a received SMS. MDN's page on the WebOTP API explains the further option of reading the code directly. It needs HTTPS, the last line of the SMS to be formatted as @your-domain #123456, and it has limited browser availability, so treat it as an enhancement with the autocomplete attribute as the fallback. Google's guide to SMS OTP forms walks through the same pattern.

Also consider whether OTP should come before or after the slot is held. If a patient must verify a phone before they see slots, the hold timer can start later and be shorter. The trade-off is one more step before any reward.

Want this applied to your practice? Get a free website audit.

Book my free audit

Failure three: the mobile back button

Most booking flows on phones are single-page flows that change the screen without changing the URL. When the patient presses Back, the browser may leave the booking entirely, drop the form, or return to the doctor listing. The slot hold stays alive on the server, so the patient returns to find it "taken" by themselves.

The browser's History API gives you the tools. Calling history.pushState when the patient moves from slot choice to details gives each step its own back entry, and a handler for the popstate event can restore the correct step from stored state. replaceState replaces the current entry without adding a new one, which suits corrections such as updating a URL without adding another step to Back. Note that these calls only change the URL and history; your code must render the matching view.

Concretely:

  • Give every booking attempt an ID and store the in-progress state (selected slot, entered details, step) on the server or in session storage.
  • Push a history entry per step, so Back goes to the previous step instead of out of the flow.
  • On returning to the flow, check whether the hold is still valid for that attempt and, if so, resume it. If not, offer the nearest alternatives.
  • Make sure the booking confirmation is idempotent so that a double tap or a reload does not create two bookings. This overlaps with the duplicate-prevention logic in the HIS integration.

Instrument it: an event schema for the teardown

You cannot fix what you cannot see. Log these events, each with attempt_id, doctor_id, location_id, device type, and a server timestamp:

EventWhenUseful parameters
slot_selectedPatient picks a slotslot start, minutes to slot
hold_createdServer reserves the slothold expiry timestamp
details_submittedForm is validtime since hold_created
otp_requestedSMS sentattempt number, gateway ID
otp_verified or otp_failedCode resultseconds since request, failure reason
hold_extendedHold lengthenednew expiry
hold_expiredTimer ran outstate at expiry
booking_confirmedScheduling system confirmsbooking reference
back_pressedpopstate fired in flowstep left, step arrived at

Then read three cuts.

  1. Funnel by step and device. Where do mobile patients drop compared with desktop? If step three is the cliff only on mobile, suspect the app-switch and back-button issues.
  2. Time distributions. Plot seconds from otp_requested to otp_verified, and from hold_created to hold_expired. Overlay the hold duration. Any mass of verifications arriving just after expiry is the direct evidence of a timer mismatch.
  3. Expiry state. For every hold_expired, record which state the patient was in. If most are in Verifying, fix the OTP experience. If most are in Held with no details, the timer is not the problem; the form is.

A hypothetical reading: suppose a 5-minute hold, and the log shows many OTP verifications between 5 and 7 minutes after hold creation, mostly from mobile. That pattern says the hold is too short for the real journey. Extending on OTP request and measuring again would test the fix. The numbers here are invented to show how to read the chart.

Use analytics tracking to send these events to GA4 or your warehouse, and join them to confirmed bookings in your scheduling system, since a confirmed booking is the real conversion.

A fix order that avoids guesswork

  1. Log the events above for two weeks without changing the flow.
  2. Identify which of the three failures dominates from the cuts.
  3. Change one thing: hold start and extension, OTP resend and overlap, or history handling.
  4. Compare the same funnel steps for the next period. Treat shifts in doctor availability, campaigns and seasonality as confounders.
  5. Repeat.

The cities and audiences matter too. Patients arriving pre-researched, as described in our note on Bangalore patients and clinic websites, tend to know which doctor they want and are less tolerant of a flow that loses their choice. Whatever your audience, the principle is the same: the system should hold the patient's intent for as long as the patient legitimately needs it.

Filed underappointment booking slot holdbooking abandonment OTPonline appointment booking funnelslot reservation timermobile back button booking form

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 13 pages

WhatsApp AI Chatbot for Hospitals (14-Day Deploy)

The 14-day WhatsApp booking-bot implementation playbook.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free website audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to slot hold and abandonment logic in online booking why patients.

Explore client work →