The request form trades speed to lead for control, and both have a price
A request form exists because someone once booked the wrong thing: a first-time filler patient into a treatment slot, or two consults on top of each other. The form puts Priya between the patient and the calendar, which fixes that and creates a queue. Every request waits there until a person opens it, and the speed-to-lead guide covers what waiting costs. The decision is how much of the control can be written as a rule and how much needs a person.
What a request costs while it waits
A request made at 9 pm is read at 9 am, and the patient who sent it also sent one to the practice down the road at 9:01. The cost is the share of requests that never become a visit and the time each one waited, both of which the queue records. A median wait in hours on a form that promises a quick reply explains the quiet weeks; the after-hours share explains why the queue is longest on Monday.
What self-booking gives up, and how the rules get most of it back
- Treatment to provider: each treatment maps to the providers who perform it, so a self-booked laser session cannot land with an injector.
- Consult first: a new injectable patient books a consult, not a treatment, when your medical director says the consult comes first; the page offers a first-time patient only the consult.
- Room and device: each is a resource with its own column, so two sessions cannot share it; the double-booking guide has the one-calendar rule.
- Deposit or card on file: on the slots your no-show data says need one, collected at booking, with terms counsel has read.
- Buffers and blocks: charting time and lunch as blocks the page cannot see, so a self-booked slot does not start the minute the last one ends.
What to measure before choosing, from your own queue
| Measure | Formula | Where it lives | What it says |
|---|---|---|---|
| Request conversion | Requests that became a held appointment, divided by requests | The request queue and the calendar | How much of the demand the form loses before a slot is held |
| Wait to first reply | Minutes from the request to the first human or system reply, median and longest | The queue timestamps | How long a patient with three tabs open was left alone |
| Wait to held slot | Minutes from the request to a confirmed time | The queue and the calendar | How many back-and-forths a booking takes |
| After-hours share | Requests created outside open hours, divided by requests | The queue timestamps | How much of the demand arrives when the desk is closed |
| Self-booking corrections | Self-booked visits the front desk had to move, divided by self-booked visits | The calendar change log | Whether the rules are catching what the form used to catch |
When the request form is right, and when self-booking is
- Request is right when a treatment needs a clinical decision before a slot exists, such as a new injectable patient or a laser candidate who needs a skin check. Your medical director makes that call; the queue is only where it waits.
- Request is right when the calendar is full and the question is who gets the cancellation, because a person can rank the queue and a page cannot.
- Self-booking is right for returning patients on a treatment they have had before, for consults, for facials, and for anything whose only risk is the room, the provider or the device.
- Self-booking is right whenever the queue's median wait runs in hours and conversion sits below what the calendar could hold; the control cost more than it protected.
How the answering system works with either form
The answering system runs the same way under either form. It answers the call, the text and the DM in seconds, trained on the menu, the pricing and each provider's schedule, and hands off to a person the moment it should. With a request form, it replies inside a minute with two times that fit the rules and books the one the patient picks. With self-booking, it catches the patient who calls instead, the one who texts with a question, and the one who books the wrong thing, under the same rules. Either way the booking lands in your calendar, intake is collected before the visit, and a no-show is caught within fifteen minutes.
A worked example, labeled illustrative
Say the queue shows 60 requests in a month in this illustrative example, and 34 became a held appointment. Say the median wait to first reply was four hours and 22 requests arrived after 7 pm, in a month with open slots. The 26 requests that went nowhere are the price of the form, and the four-hour median is why. Say the practice opens self-booking to returning patients and keeps the form for first injectable visits, with the answering system replying to those inside a minute.
How to measure yours this week
- Export the request queue for the last ninety days: created time, first reply time, outcome, and the time a slot was held.
- Priya builds the four numbers from the table: conversion, wait to first reply, wait to held slot, after-hours share.
- Pull the calendar change log for the same period and count self-booked visits that were moved, by reason.
- Put the median wait beside the conversion and decide which treatments keep the form; the rest go to self-booking with the five rules above.
What to do next
NorthCore's Answer every patient replies to each call, text, DM and request in seconds and books under your rules into your calendar; Fill the calendar collects intake and catches the no-show. Both are scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.
