AI Receptionist for Pabau Clinics

Nine o'clock at a busy Pabau clinic and the phone has already asked four different questions. A woman wants filler before a wedding. A man is midway through a physio course and needs to move tomorrow's session. Someone is asking what their membership actually covers. And a fourth caller describes a reaction to a treatment and is not sure whether to worry. Four calls, four different right answers, and on most mornings one receptionist trying to hold all of them at once while the line keeps ringing.

We build the Pabau connection, and the point of this piece is what happens to those four calls when every one is answered at once and written straight into Pabau.

None of the four is hard on its own. The difficulty is the switching: a filler enquiry and a reaction report want opposite things, and a rushed desk that treats them the same is how a booking lands wrong. 2care resolves the service, the provider and the urgency from what the caller actually says, and places each call accordingly, all four answered on the first ring because there is no limit on how many the line takes at once.

The call	What 2care hears	Where it lands
Filler before a wedding	A cosmetic booking, time-sensitive	A consult or treatment slot, deposit if set
Move tomorrow's physio	A course session to reschedule	A new slot inside the course window
What does my membership cover	A terms question, no visit	Answered from the membership setup
A reaction to a treatment	A clinical concern	A clinician, in about 3 seconds, transcript attached

The reaction call is the one that matters most and the one a booking agent must not try to handle. It leaves the booking flow the moment the description crosses a red-flag line and reaches a person, with what the caller said already attached, so nobody starts by asking them to explain it again. How those lanes are set is covered in triage and routing.

Take the physio caller in more detail. "I'm on the Tuesday plan with Sarah, I need to push tomorrow." That single line carries a returning client, a named practitioner, an existing course and a reschedule, not a new booking. The agent resolves the record, finds the session inside the course, reads Sarah's live availability, and moves it to the next slot that keeps the course spacing intact, releasing the old time back to the diary. The client never has to explain that they are mid-course, because the record already says so, and the course does not quietly lose a session to a reschedule that dropped it.

Where a package or a course is won or lost

The physio caller and the membership caller are where a Pabau clinic actually makes or loses money, and both are where a rushed front desk slips. Before it books a redemption, 2care verifies the package balance in Pabau, so a client is never put into a session they have already used, and the balance updates as part of the same write. A membership question is answered from the terms the clinic set, not improvised.

A course is booked whole. The client on session three does not just move tomorrow; if they are near the end, the agent can place the remaining sessions at the clinic's cadence in the same call, each with its own reminder. A six-session course booked whole runs to completion far more often than one booked a session at a time, and on a clinic whose revenue leans on courses and packages finishing, that completion rate is the number that matters more than any feature.

Memberships are the quieter version of the same problem. A member ringing to ask what their plan covers, or whether a treatment is included, is a call a busy desk answers inconsistently and sometimes wrongly, which erodes the trust the membership was meant to build. Answered from the terms held in Pabau, the reply is the same every time and correct every time, and a renewal that is due is prompted before it lapses rather than after the member has drifted. Getting the small, repeated membership calls right is unglamorous and is exactly the kind of thing that decides whether a membership base grows or churns.

Underneath: how a Pabau booking is actually made

The four calls all resolve to the same mechanism. 2care reaches Pabau through its API, authorised with a scoped credential set during onboarding, with nothing installed at the clinic. Availability is read live, by provider, service and location, so a slot offered genuinely exists. The booking, whether an appointment, a course or a package session, is written against the resolved client and validated by Pabau against its own rules, which is why a slot taken mid-call fails honestly rather than being assumed free.

All of it runs on a native voice pipeline, not a wrapper over a third-party voice service, and that is what keeps it fast enough to pass for a person. A caller hears a reply in about 480 milliseconds, with the ninety-fifth percentile under 700, and the live read from Pabau happens inside that budget rather than adding to it. The platform holds 99.9% uptime and answers 1000+ concurrent calls, so the Saturday rush after a campaign is the same experience as a single midweek call, and the reliability that matters is not a demo that works once but a line that behaves identically at 9am and 9pm.

Two engineering details matter on a real call and are worth naming. Turn-taking uses a dual signal, the line going quiet and the words forming a complete thought, so the agent does not cut off a client who pauses mid-sentence to check a date, which a plain silence timer does constantly. And the booking write carries an idempotency key, so if the network stutters and the request is retried, Pabau still records one appointment rather than two. Neither shows in a demo, and both are the difference between a system that holds up on the hard calls and one that only looks good on the easy ones.

Identity is settled first. The caller is matched to their existing Pabau file and confirmed on a date of birth, so a returning client keeps one record; where two files are equally plausible, a person takes over rather than the agent guessing and splitting a history. That resolution is the same one described in patient matching, and it runs before a slot is ever held.

The order is deliberate. Identity is settled, then availability is read, then the slot is held, then the write is issued and confirmed only once Pabau accepts it, so nothing is ever spoken to a client as booked before it exists in the diary. Rate limits and credential refresh are the connection's job, not the conversation's, so the clinic's own Pabau performance, fast or slow on a given day, is what the caller experiences, with no shadow copy sitting in between to drift out of step with the real diary.

Keeping a UK clinic's data where it belongs

For a UK clinic the compliance question is not an afterthought, and a booking that builds a transcript, matches a client and writes to Pabau is plainly processing personal data, not passing it through.

That makes the vendor a data processor, and for US clinics a business associate under HHS guidance. So the data is held in region, a data processing agreement sits alongside the arrangement, consent and marketing preferences are captured as the clinic requires, everything is encrypted in transit and at rest, and the models behind the conversation never train on any of it. The compliance page lays out the frameworks that apply on each side of the Atlantic.

The calls that never stop, and the ones you make back

The four-call morning is not the exception; it is every morning, plus the evenings and weekends the desk is not there. Because the line has no busy signal, the Saturday enquiries that used to reach voicemail are answered and booked into the week, each on the first ring in about 2 seconds.

The same Pabau connection also makes calls back. It rings a client partway through a course before the next session slips, prompts a membership renewal that is due, confirms tomorrow's appointments against no-shows, and offers a cancelled slot down a waitlist within minutes. Every result writes back into Pabau, so a rebooked session and a renewed membership are in the record the clinic already works from, not on a list beside it. Between them, answering everything and calling the right people back is what keeps a mixed diary full rather than merely busy. A client three months past their last visit is far easier to bring back than a cold lead is to win, and those are exactly the calls a busy desk never finds time to make.

Where this is right, and getting there

The clinics that gain most run a genuinely mixed book, keep their packages, courses and membership terms current in Pabau, and already have a clinician to receive the calls that turn clinical. Given those three, the benefit lands on the first day the line goes live.

Getting there is three moves over weeks. The connection is authorised to read availability and write bookings through the Pabau API. The clinic's setup is mapped, services, providers, package and course definitions, membership terms and the clinical route. Then the line is tested against a sandbox with the team listening before it is switched over. The opening days refine the mapping against real calls, and because each escalation stores the trigger that raised it, every change rests on evidence rather than a hunch. Clients dial the same number throughout, with nothing to port and no hardware to fit.

Frequently asked questions

Can it redeem a package session on the call?

Yes. It checks the package balance in Pabau before booking, so a client is never put into a session they have already used, and the balance updates as part of the write. A membership query is answered from the terms the clinic has set rather than a guess.

Does it book a whole course at once?

Yes, where Pabau supports it. Every session in a course is placed at the clinic's cadence with a reminder against each, rather than the first booked and the rest promised, which is what keeps a course from thinning out after the first visit.

What happens to the clinical calls?

A call that describes a reaction or a medical concern leaves the booking flow and reaches a clinician in about three seconds, with the caller's own words attached. The agent never assesses or reassures, because that is a clinical judgement it is built not to make.

How is our data handled for a UK clinic?

It is held in region, under a data processing agreement, with consent and marketing preferences captured as the clinic requires. Everything is encrypted in transit and at rest, and no client information is ever used to train shared models.

Will it create duplicate records in Pabau?

No. The caller is matched to their existing Pabau file first and confirmed on a date of birth, and where two files are equally likely a person takes over rather than the agent choosing one, so a client's history stays on a single record.

Hear a mixed morning handled

The call list worth judging on a Pabau line is exactly that four-call morning: a cosmetic enquiry, a course reschedule, a membership question and a reaction, back to back, each placed correctly while the phone keeps ringing.

See how the same connection runs on other systems across integrations, or hear a mixed clinic morning handled on a live call when you book a demo.