Comparison
A scheduling bot serves the patient who already decided to come; Surface starts from an order nobody booked
This is the comparison that is hardest to make from the outside, because in a demo the two look almost identical: a WhatsApp conversation that ends with an appointment booked. The difference sits in who starts that conversation and in what was read before it started.
What does a scheduling bot do?
It answers at any hour with no phone queue. It shows a menu of services, checks availability, books, reschedules, cancels and sends reminders. For a patient who already knows what they want, it beats calling and waiting.
For the provider, it takes phone volume off the desk and frees the front line from the most mechanical part of the day. It is the most mature use case on the market and it works.
Who starts the conversation?
A bot serves demand that already exists. If the patient writes, the bot resolves it. If the patient left the order on the bedside table and never looked at it again, the bot never learns that order exists.
Surface's work begins before there is a patient writing. It begins in the record, with a medical order no process ever managed, and it ends when that order is completed or when the patient decides, informed, that they will not complete it.
That difference decides what can be measured. A bot reports how many conversations it handled and how many bookings it produced. Surface's denominator is how many orders were written in the period, which is the only base on which the word completion means anything.
Can a bot read what the order says?
Here is the technical difference almost nobody sees from outside. A scheduling bot maps a menu selection to a slot: the patient picks abdominal ultrasound from a list and the system looks up availability for that service.
Medical orders do not arrive in menu format. They arrive handwritten or in free text, with whatever name that doctor uses. A patient reads out gastroendoscopia con biopsia, and in the calendar that service is called something else, is grouped with others, and requires a preparation that has to be confirmed before any slot is offered.
Someone has to resolve whether it needs contrast, whether it requires fasting, how many preparation days it takes, which other exams belong in the same visit and which one goes first. That mapping lives today in the schedulers' heads and in their personal matrices. Turning it into something a machine executes precisely is half the product, and it is published exam by exam in the per-exam guides.
How do they compare, line by line?
| Dimension | Scheduling bot | Surface |
|---|---|---|
| Who starts | The patient, when they write. | The provider, when an order shows up unscheduled. |
| What it reads | The selection the patient makes from a menu. | The text of the order, with its aliases, its contrast question and its preparation. |
| What the already-motivated patient experiences | An instant answer at any hour, with no phone queue. | A conversation that starts from their pending order, with a specific slot already proposed. |
| What it costs to scale | Low. It is the most mature use case on the market. | Scales without shifts, once the clinical sources are connected. |
| What data you get back | Conversations handled and bookings made. | Completion per order, with the denominator declared. |
| Time to first result | As soon as the channel goes live. | In production in one week, extraction included. |
Can you run both?
Yes, and it is the most common setup. One covers inbound and the other generates outbound. If your WhatsApp channel is already standing with another vendor, Surface can run on top of that channel instead of asking you to replace it.
What is worth checking seriously is that both read the same availability. If two systems offer the same slot and one of them runs on a lag, the patient finds out about the lag before you do.
When is a bot enough on its own?
If your orders already come out of the system structured, somebody already works that list to the end, and your stated problem is inbound phone volume, a scheduling bot solves your whole case and you need nothing else.
The same holds if you run a single specialty with a short, stable service catalogue. The mapping problem that makes this hard does not exist in your case, and paying to solve it would be paying for nothing.
What happens to the team you already have?
The bot stays and the team stays. What gets added is the side of the flow that has no owner today: the written order nobody read, with your own rules deciding when to follow up and when to hand the case to a person.
Your people stop chasing the list and start resolving the cases only a person resolves.