Virtual receptionist

The questions that separate booking from message-taking

Every provider on the market says it books. These five are asked on the sales call, in this order, and the answers sort them inside ten minutes — before anybody quotes you.

• How do you charge — per call, per minute, or per booking? Only one of those puts your incentive on the same side as mine, and it is not the one that gets offered first.
• Show me where the rules live. If they live in a script an agent reads, they are not rules — they are suggestions with somebody's mood attached.
• Show me a week of real bookings, including the ones a person had to fix afterwards. Any provider proud of the first number has the second one too, and the ratio is the whole story.
• Who picks up when it books somebody into the wrong slot at seven on a Friday? A name and a route, not a support address.
• What do I get to see afterwards — the recording, the transcript and the reason for each decision, or a monthly summary? A system you cannot audit is a system you cannot correct.

The measure that actually matters

Nearly every service is sold on how the call was handled: answered in three rings, friendly, professional. None of that is the number. The number is what share of calls ended with something in your diary, and almost nobody reports it because almost nobody can do it.

Booking requires access to your real availability, your real rules about who can be seen when, and the ability to write into the system your business actually runs on. Taking a message requires none of those, which is why it is what gets offered.

What booking properly requires

• Your real diary, not a copy. Read and write, live. A parallel calendar that gets reconciled later produces double-bookings, and one double-booking undoes a month of goodwill.
• Your rules, written down. Who can be booked with whom, how long each kind of appointment takes, what needs a deposit, what cannot be booked without a person. Two weeks of decisions, and more of the value sits here than in anything technical.
• Recognising the caller. An existing customer, an outstanding order, a lapsed appointment — known before the conversation starts, because starting from nothing is what makes it feel like a switchboard.
• A hard line for what it must not take. Complaints, emergencies, anything clinical or legal, anything about a price beyond your published one. Written first, tested before it goes live.
• The escape hatch, tested before launch. First ask, no loop. Every service claims this and it is worth testing before you sign anything.

Where it has to stop and hand over

• Name a figure nobody wrote down. Your published prices it can repeat. A quote assembled on the call is a promise you did not make and will still be held to.
• Handle a complaint. Anything with anger in it goes to a named person immediately. A machine being calm at somebody who is upset makes it worse, reliably.
• Give advice of any kind that a professional gives. Clinical, legal, financial. It takes the details and puts a person on it, and that boundary is written down before anything is built.
• Book outside your rules because the slot looked free. An empty slot is not the same as an available one, and the difference is exactly what your rules encode.

Three ways to waste the money, and all of them are the diary

If the diary is a paper book or lives in one person's head, that is the first project and it is a small one — nothing on this page works without it, and doing that alone may be enough. If you are booked three weeks out with no way to add capacity, answering faster only makes the queue longer: the constraint is somewhere else and this will not move it.

And if nobody has decided the rules, decide them before buying anything. Where two people in your business would book the same caller differently, a system does not settle it — it picks one of them and applies it to everybody, consistently, which is worse than the argument you were avoiding.