Connecting an AI to your clinic's software: mirror or the real schedule

A clinic that already runs on a management program — clinical records, schedule, quotes — has a fair objection when someone offers it an assistant that answers WhatsApp or the phone: so now I have two schedules?

It is the right question, and the answer comes down to a technical detail that almost nobody explains. Let us explain it, because it is what separates an assistant that works in a clinic with a front desk from one that causes trouble within a week.

Two ways to connect, and they are not equivalent

The mirror

The assistant has its own schedule and copies it across to the other program, or the other way round. Every so often — every night, every fifteen minutes — they sync.

That is what a Google Calendar connection does, for instance, and for many businesses it is perfectly fine: if the real schedule is the assistant's and the calendar is a copy to check from your phone, there is no conflict possible.

The real schedule is on the other side

In a clinic with a front desk, it is the other way round. Reception books into its program all morning, while serving whoever is standing at the counter. There, the schedule that counts is the clinic program's, not the assistant's.

And if the assistant is working from a mirror it read overnight, the predictable thing happens: at six in the evening it offers a slot over WhatsApp that reception filled at eleven. The patient takes it, and then somebody has to ring them back to say no.

That failure is the one that burns the most trust. Missing a call is bad; giving a slot and taking it back is worse, because the patient had already arranged their afternoon around it.

The alternative is for the assistant to ask live: before offering anything, it checks with the clinic's program what is free right then, and on confirming, writes the appointment there. There are no two schedules because there is no copy: there is one schedule and someone asking it.

What to ask before you sign

Five questions. All five have short answers, and anyone who cannot give them has not solved this:

1. Do you offer slots by reading a copy or by asking in the moment? If it is a copy, how often does it refresh?
2. When the AI closes an appointment, does it appear in my program straight away or tonight?
3. And the other way round: if reception writes an appointment into my program, when does the AI stop offering that slot?
4. What happens if a notification is lost? A good answer includes a periodic pass that squares both sides, because notifications do get lost.
5. What data travels? In a clinic this is not a detail: the clinical record does not have to leave where it is.

That last one deserves a pause. Booking does not require knowing what the patient has: it requires their name, their phone number, the treatment and the time. A connector that hauls the clinical record around is moving health data with no need to, and that is a risk nobody is paying you to take on.

How it is solved in ClaudIA: the Nubimed connector

Nubimed is a dental practice management program widely used across Spain. Since September 2026 ClaudIA has a connector of its own for it, running in production with its first clinic.

It is built the second way, the asking-live way:

• The real schedule is Nubimed's. ClaudIA asks it which slots are free at that moment, with the actual duration of that treatment, and offers those. It does not offer a copy.
• On confirmation the appointment is written into Nubimed on the spot, with its patient, its dentist and its treatment. If Nubimed does not accept it — because that slot has just been taken there — ClaudIA knows before the patient hangs up and offers another time.
• It works both ways. Whatever the team does in Nubimed — create an appointment, move it, cancel it, register a patient, prepare a quote — reaches ClaudIA within seconds. If someone cancels from Nubimed, ClaudIA stops offering that slot and stops reminding the patient about the appointment.
• And there is a background pass every night that squares both sides even if a notification got lost along the way. Notifications do get lost; designing for that is part of the job.
• Dentists, their treatments and their schedules are read from Nubimed. Imported once and refreshed on their own, so there is no catalogue to maintain twice.
• The clinical record and the dental chart are not touched. They stay in Nubimed. ClaudIA talks, books and follows up; clinical data does not leave your program.

The integration runs through the API Nubimed opens to its customers, and ClaudIA builds and maintains it. That means that for anything to do with the connector, you talk to the same team that makes the product.

It is ClaudIA's first connector to a practice management program. The next ones arrive as clinics ask for them, so if yours is a different one, tell us.

With any other program, through the schedule

There is nothing to migrate here either. The general route is the schedule: if your program syncs with Google Calendar — most salon and clinic programs do — ClaudIA works with it through there, and both ways. What ClaudIA books appears in your calendar and what your team writes in is respected as busy time.

• The schedule stays continuously in sync, both ways.
• Your patients are imported in a few minutes, by exporting a file from your program, without duplicating a single record.

And either way, your data exports whenever you want. The client base is yours.

You can see how all of this works for a clinic at ClaudIA Dental.