Question handling
Handling appointment requests without a booking integration
The instinct is to treat this as the intent that needs a calendar connected before it is worth anything. It is not. Watch what actually gets typed and most of it is not a request for a time at all, it is a set of questions somebody has to resolve before they are willing to commit to one. Answer those and the booking largely takes care of itself.
What they are really asking
They have already decided they probably want this, and they are clearing the last one or two obstacles before committing.
- can i book an appointment
- do you have anything this week
- how do i make an appointment
- do you take walk ins
- how much is a first appointment
- how long does an appointment take
- do you take my insurance
- can i book on behalf of my mum
- do i need a referral
- are you open on saturdays
The material that answers it
An assistant is only as good as the document behind it, and for this question the document usually exists but is written in the wrong shape. What each one has to contain to be answerable:
| Every service with its duration and its price | Two facts, together, per service. Duration is asked constantly and published rarely, and it is the thing somebody needs in order to know whether they can fit this into a lunch hour. Price without duration answers half the question. |
|---|---|
| What a first appointment involves | What happens, in order, and how it differs from a follow up. A first appointment is the one people hesitate over, because they cannot picture it, and a description of the sequence removes more hesitation than any amount of reassurance. |
| The booking routes you actually want used | The online link, the phone number, the form, and which is preferred for what. If there are three routes and the assistant offers all three, it has handed the visitor a decision instead of an instruction. |
| Who you can and cannot take | Age limits, referral requirements, insurers or plans you accept, catchment area, whether you are taking new clients at all. Every one of these turns a hopeful booking into a wasted slot when it is discovered at the door instead of in the chat. |
| Opening hours including the ones that vary | Late evenings, weekend cover, holiday closures, the difference between when the phone is answered and when appointments run. Somebody asking about Saturday is asking because Saturday is the only day they can do. |
How to handle it
Answer the blocking question before anything else
Underneath can i book an appointment there is nearly always a specific worry: the cost, whether their plan is accepted, whether they need a referral first, whether their child can be seen. The assistant that leads with the booking link has skipped the part that mattered.
Material organised around those worries outperforms material organised around services, because it matches the shape of the question rather than the shape of your price list.
Give one booking route, not a menu of them
Say where to go, in one sentence, at the end of a reply that has already removed the obstacle. Offering the link, the number, the form and the email address in the same message reads as thorough and behaves as friction, because now the visitor has to choose.
Pick the route you would rather they used and write the material so that route is the one that appears.
Never imply anything about availability
The assistant cannot see a diary unless you separately connect a data source, so it must not say that there is usually space this week, that mornings tend to be quieter, or anything else that sounds like a look at the calendar. A visitor who reads a hint of availability into a reply and then finds nothing free has been misled by your website.
Publishing a genuine pattern is different from implying a live one. Wednesdays are our late evening is a fact. We usually have space on Wednesdays is a guess about next week.
Hand over with the context already gathered
When the request does need a person, the reply that comes back is only as good as what arrived with it. The assistant should prompt for the service they want, roughly when suits, and anything that affects eligibility, so the enquiry lands complete.
The widget collects a name, an email and a message, which is sent to whichever address you nominate and stored so it survives an email failure. The message field is where that detail belongs, so ask for it before offering the form.
When it stops being an answer
Anything urgent
Urgency changes the channel. Somebody who needs to be seen today should be given a phone number in the first line of the reply, not a description of how to book online. Put the number in the fallback message rather than trusting the assistant to compose it under pressure.
Any request to actually make, hold or change a booking
Book me in for Thursday is an instruction to write into a system the assistant cannot touch. The failure here is subtle: a friendly reply that does not clearly say no can leave somebody believing they have an appointment. State plainly that it cannot book, then give the route or take the enquiry.
Eligibility that has edges
An unusual insurer, a borderline age, a referral from a source you do not normally take, somebody outside your area. The assistant should state the general rule and hand the edge to a person, because the exceptions are where a wrongly confident yes costs an appointment slot and a wrongly confident no costs a customer.
How this one goes wrong
The polite dead end
A visitor asks what a first appointment costs. The assistant answers accurately, then finishes with please contact us to book. There is no number in the reply, no link, and no offer to take details. The person now has the one piece of information they were missing and nowhere obvious to put it.
This is the most common way booking questions get wasted, and it is invisible in any measure of answer quality, because the answer was correct. Every reply in this intent should end in a route: a link, a number, or a form. An answer without a next step is a conversation that ends in the same place it would have ended without the widget.
The same question, trade by trade
The pattern above holds everywhere. The wording, the escalation line and the material behind it do not, so there is a page per trade.
- For a dental clinicWhat to say when a dental visitor asks for an appointment, given the assistant cannot see the diary or hold a slot.
- For a medical practiceSame day releases, telephone slots and who to see. What a practice assistant explains, and what it must not touch.
- For a veterinary clinicNurse clinics, vaccination courses and which species you see. The vet booking questions worth settling in the chat.
- For a physiotherapy clinicSelf referral, assessment versus follow up, and picking between physio and another discipline on the same site.
- For a opticianAn opticians runs several appointment types and customers ask for all of them the same way. Telling them apart.
- For a law firmA time with a fee earner depends on a conflict check, the right department and a court diary, none of which a chat window can settle.
- For a accounting firmWhich meeting is being asked for, why the answer changes near a filing date, and why nothing here can put anything in a partner's diary.
- For a insurance brokerA review is scheduled backwards from a renewal date, and half the people asking for a meeting only need a document today.
- For a mortgage brokerThe assistant cannot take a slot. It can remove every reason somebody hesitates to book one, then hand a warm enquiry to an adviser.
- For a estate agencyMost viewing enquiries land when the branch is shut. What the assistant can settle about access, notice and hours before a negotiator sees it.
- For a recruitment agencyWalk in or by appointment, which branch, and why an interview is never the agency's to arrange. Booking answers without any diary.
- For a marketing agencyA prospect, a client chasing an account lead, a supplier and a student all type the same request. Only one of them is a discovery call.
- For a bike shopIt cannot take a slot. It can answer the four questions that come before one and hand over an enquiry ready to schedule.
- For a hotelThree diaries the hotel runs, none of them the room inventory, each with its own notice period and its own cancellation position.
- For a holiday rentalPeople do ask to look round before they book a week. Usually the answer is no, and the reason it is no is worth explaining properly.
- For a gymThe two things a club books one to one, the health form that comes first, and why a block of sessions has an expiry on it.
- For a salon or spaA colour booking has a patch test deadline attached. Raising it during the enquiry saves the appointment that would be turned away.
- For a universityOpen days, campus tours and applicant days are three different things. An assistant that can explain each one saves the enquiries team most of its inbox.
- For a private schoolThree different school visits, arranged three different ways, and nothing said in a chat window reaches the registrar's diary.
- For a driving schoolThe assistant cannot see an instructor's availability. What it can do is remove every other reason a learner has not booked yet.
- For a plumbing and heating firmA plumbing appointment is a time window, an access requirement and a charge on arrival. All three can be explained without seeing a diary.
- For a electrical contractorThe date is the easy part. The real agreement is how many hours the house has no supply, and who has to be in while it does not.
- For a removals companyA survey slot can be arranged for next week. The move date waits on a completion, so a firm pencils it and nobody commits until exchange.
- For a car dealershipA licence, a minimum held period and an insurance arrangement decide whether a test drive happens at all. Say all three beforehand.
- For a healthtech appAccess often runs through an employer, insurer or health service, which decides the answer. What to clarify before anybody tries to book.
Questions
- Is this worth using without a calendar connected?
- Yes, and arguably it is where most of the value is. Availability is rarely what stops a booking. Price, duration, eligibility and what happens at the first visit are, and all four are answerable from material you already have.
- What happens when somebody asks it to book them in?
- It should say clearly that it cannot make bookings, then give the route or offer to take their details for the team. The important part is the clarity, because a vague reply can leave somebody thinking a booking exists.
- Which single document changes the most outcomes here?
- A services list carrying duration alongside price. It is the combination people need in order to decide, and most sites publish one without the other.
Keep reading
- Handling rescheduling and cancellingNotice periods and charges are answerable. A specific booking is not. Hiding the policy produces complaints, not fewer cancellations.
- Handling waiting listsExpectation setting is the whole job: how the list is ordered, how contact is made, and whether a short notice cancellation can reach them.
- Handling group bookingsNearly always a handover, and an expensive one to fumble. Collect the date, the numbers and the requirements before it reaches a person.
- Every question typeHandling patterns for the questions every support inbox gets.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.