Before somebody confirms a slot, you can ask them a small number of things. This is the most distinctive part of the Booking Engine and the part most worth configuring properly.
What you can ask
Three things, each switchable independently.
Topics. A short set of options describing what they want to discuss.
Urgency. How soon they need this resolved.
Decision maker. Whether they can decide, or need to involve somebody.
Topics
You define them. Each has a label and an icon, chosen from a small catalog so the page stays coherent.
The set that ships is a reasonable starting point: a platform demo, pricing and scope, a technical audit, a partnership. Most organisations should replace these with their own vocabulary within a week of using it.
Writing good topics
Four or five, not ten. A long list is a survey, and people abandon surveys.
Use their words. "Pricing and scope" is what a buyer thinks. "Commercial qualification" is what you think.
Make them genuinely different. Two topics that lead to the same conversation are one topic.
Cover the awkward one. If a meaningful share of enquiries are about something you would rather not discuss, having a topic for it is better than discovering it eight minutes into the call.
Icons
Each topic carries an icon from a small fixed catalog, which keeps the page coherent rather than letting it become a collection of mismatched symbols.
Pick the closest rather than agonising. The icon is there to make the options scannable, and no visitor has ever chosen differently because of one.
Urgency
Off by default, and worth switching on where timing changes how you respond.
The argument for it is prioritisation. Two bookings on Thursday, one from somebody with a deadline and one exploring, deserve different preparation and sometimes a different order.
The argument against is that it is one more question, and questions cost bookings. Enable it if you will act on the answer.
Decision maker
On by default, and the single most useful of the three for anybody selling.
It is a checkbox rather than an interrogation. The person ticking it is telling you they can proceed; the person leaving it is telling you there is somebody else, without either of you having to make that awkward five minutes into a call.
What to do with a no is not to deprioritise them. It is to ask, before the meeting, whether the other person should join. That single question converts a good conversation with the wrong person into the right meeting.
Why ask at all
A meeting arranged by email carries context, because arranging it required a conversation. A meeting booked from a link carries none, and you arrive knowing a name and a company.
The context step buys back the useful part of that lost exchange for about fifteen seconds of the visitor's time. You know what they want, roughly when, and whether the conversation can conclude anything.
The effect on the meeting itself is larger than it sounds. You prepare for the actual subject, you skip the opening five minutes of establishing why everybody is there, and you invite the right people.
Where it appears in the flow
The context step sits between choosing a meeting type and choosing a slot.
That position is deliberate. Somebody who has picked a meeting type has already decided to book; asking before they have decided costs more of them. Asking after they have chosen a time would feel like an obstacle at the moment of commitment.
The practical consequence for you: keep it short. It sits at the point of highest intent, which is exactly where a long form does the most damage.
Do not ask twice
Whatever the context step asks, do not ask again on the call.
Opening a meeting by asking somebody what they wanted to discuss, ten minutes after they typed it, tells them nobody read it. It is a small thing that undoes the whole point of collecting the answers.
Open with what you know instead: "You mentioned pricing and that you are looking at this for the new quarter." That sentence changes the character of a first conversation more than any amount of preparation.
The trade
Every question reduces the proportion who complete a booking. That is not a reason to ask nothing; it is a reason to ask only what changes your behaviour.
The test for each question: if the answer were different, would you do something differently? If not, it is costing you bookings and telling you nothing.
By that test, decision maker usually earns its place, topics usually do, and urgency depends entirely on whether your team actually triages by it.
Keeping them current
Topics go stale faster than anything else here, because they describe what you sell and that changes.
Review them when your offering changes, and when a quarter's answers show a topic nobody selects. A booking page still offering a service you stopped providing is worse than one offering fewer options, because somebody will select it.
Five minutes, twice a year.
Reading them at scale
Individually the answers help you prepare. In aggregate they tell you something you cannot get any other way: what people think you are for.
A topic nobody ever selects is a service you believe you offer and the market does not associate with you. A topic selected by most people is the thing to lead with everywhere else.
That is worth reviewing once a quarter, and it is worth ten times more than the same question asked in a survey, because these answers were given by people who were about to spend an hour with you.
Where the answers go
Onto the booking, visible with it on your calendar and on the person's record.
They are worth reading before the call rather than during it. The whole value is in the preparation, and a topic noticed while the visitor is already talking is a topic that arrived too late to be useful.
Did this answer your question?
No, ask a person