Implementing automated scheduling with Surface takes three weeks: setup on day 1, production in one week

The question comes up in the first meeting and it almost always carries a bad experience behind it: the last integration took nine months and ended in a pilot nobody used. For Surface the answer is three weeks, and the calendar can be written with concrete dates before anything is signed.

1. Day 1. Setup.

   We receive the file of pending orders and your scheduling rules. The catalogue, the locations, the preparation requirements and the exclusions all get configured.

2. Days 2 to 5. Dry run.

   The agent drafts complete conversations on real cases and your team reads them before a single message goes out. Wording, hours and rules get corrected the same day.

3. After one week. Production.

   The first messages go to real patients under your brand. The first bookings land on your schedule that same week.

4. Week 3 onward. Results.

   There is enough volume to read the funnel stage by stage and decide what to expand: more exams, more locations, wider outreach hours.

What happens on day 1 and what does the provider have to supply?

Day 1 is a working session we walk out of with the system configured. What we need from your side is four things, and none of them requires opening an IT project.

• The pending orders. A file with patient identifier, phone number, exam ordered, date of the order and referring location. If a read integration already exists we use it; if not, a CSV you export and you control is enough to start.
• Your scheduling rules. Which exam is done at which location, what preparation each one requires, which studies go together and which cannot share a day, and which patients are excluded from outreach.
• Your brand and your tone. The number the messages come from, how the patient is greeted and the things the agent never says.
• One operational contact. Someone on your team who can answer a scheduling question the same day it comes up.

What we do not ask for: data migration, changes to your clinical system, or anyone on your team learning a new tool. Surface operates on top of what already exists, and when your records system is ready for a real integration, we build it.

What happens during the rest of week 1?

Week 1 is translation work. The name the doctor wrote in the record has to reach the service your catalogue knows how to book, and that mapping is not one to one: there are aliases, there are abbreviations, there are exams that exist at one location and not at the one next door.

In parallel, the agent starts drafting complete conversations on real cases without sending anything. Your team reads them as if they had already gone out, marks what they would change and we correct it the same day. It is the step nobody expects and the one that decides whether production works.

Towards the end of the week a small controlled batch goes out, reviewed case by case. Starting small is an operational advantage: it lets you be wrong cheaply while the volume still does not matter.

What does being in production after one week mean?

Production means messages going to real patients with your brand on the sender, slots being taken on your schedule, and a dashboard showing the funnel with data you can audit the same day. The booking happens in your system, with your slots and your rules.

The first conversation looks like this: the agent identifies itself as your centre, names the specific exam left pending and how long it has been pending, asks whether the patient still needs it, offers real times to choose from, explains the full preparation and confirms. If the patient asks not to be contacted, they drop out instantly and we never write again.

The first bookings appear in the first days of that week. The first patients seen appear when their appointment comes around, and that depends on your schedule availability.

What happens from week 3 onward?

From week 3 there is enough volume to read the funnel stage by stage: how many orders were found, how many patients were contacted, how many replied, how many booked and how many were seen. The last number is the one that counts, and the methodology we use to calculate it is written out in how we measure.

The adjustment cycle is weekly: outreach hours, wording that does not land, exclusions that were missing, new exams entering scope. The natural expansion is by unit, one service at a time, and each one fails in its own way: radiology, laboratory, gastroenterology, cardiology and dental have nothing in common operationally.

Why is it this fast?

The critical path does not run through your IT department. A read-only export is something your team can produce without opening a project, without a committee and without waiting for the next release window. We build the real integration anyway once your system is ready, and it runs in parallel without blocking anything.

The second reason is that there is no learning curve to pay for. Training time for a scheduling team is working hours the units do not have, and there are fewer of them every year. Your schedulers keep working in the system they already know; the agent absorbs the repetitive work and what reaches them is the case that needs a person.

What could make it slower and who controls that?

Three weeks is the calendar when the decisions on the provider's side get made on time. What stretches it is almost always on this list, and the list is short and known in advance.

• Legal review. The data processing agreement and your legal team's review under Chile's health data law is the longest item and the hardest to speed up from outside. Worth opening the day the decision to proceed is made.
• The WhatsApp account under your brand. Verification depends on your institution and on the channel provider. You can start with a provisional number while it is resolved.
• Rules nobody has written down. If the scheduling rules live in the team's memory and in personal cheat sheets, someone has to sit down and write them. It is a day of work, and the document ends up yours.
• An initial scope that is too big. Starting with every exam across the whole network stretches week 1 without changing what you are going to learn. One specialty and a couple of locations give you the same signal sooner.
• Bad contact data. Incomplete or outdated phone numbers do not get fixed by a better agent. They show up in the first batch and get corrected at the source.

None of these is a hidden risk. The calendar gets written with dates in the first meeting, and if it slips, it slips for a reason both of us can name.