Do we have to leave Pabau?

No. Pabau stays your system of record for the calendar, the client records and the charts. We build around it.

Does this change how my team books?

No. Bookings land in the Pabau calendar the way they always have. The difference is how many of them there are, and that no one at the desk had to stop a treatment to take the call.

What if something is not available through an API?

Then that piece runs from the booking link and the exports Pabau already provides, and we tell you which pieces those are before we start.

Can you work with Pabau and another platform at the same time?

Yes. Many practices run a record system plus a messaging or marketing tool. The system reads from both and keeps one record of every patient conversation.

Pabau AI Receptionist, Reactivation and Reports for Med Spas

Your numbers, your strategy, and every call answered, on Pabau.

Pabau is a practice management system for clinics and medical spas; it stays. NorthCore reads the numbers out of Pabau: revenue by provider and treatment, utilization and who is due. With your supply invoices and payroll, it puts the margin to the dollar beside them. The ninety-day strategy comes from that; the system executes it: phones and DMs answered and booked, the comeback timed, parties and memberships priced from that margin, the dashboard. We build on Pabau the same way we build on every booking and record system: we read what it holds, write back what it needs, and leave your team's screens alone.

Updated 2026-10-26

Everything your team trusts stays in Pabau

All of it stays where it is: the calendar, the client records and the charts. Your team keeps the software it knows, and no booking is entered twice. If a patient books with the voice agent at 9 pm, it is on the Pabau calendar at 9 pm, with the notes. Your front desk sees it the way they see every other appointment.

What an EMR like Pabau holds that the system builds on

The record itself, the calendar, the client records and the charts, stays in Pabau. The system reads the visit history it needs for timing and writes nothing into a chart.
The booking is linked to the record, so the provider opens one screen on the day, not two, and the front desk sees the note the agent took on the call.
Last treatment and last visit by patient, which is what the comeback calendar runs on. Pabau keeps the clinical record; the system keeps the schedule of who is due and sends the message.
The calendar inside Pabau is the only calendar. Bookings from calls, DMs and texts land there, with the notes, so the provider and the desk see the same day.

What the system does around it

Reads the numbers out of Pabau: revenue by provider and treatment, utilization and who is due. With your supply invoices and payroll, puts the margin to the dollar beside them on one page.
Builds the strategy from them: which treatment carries the practice, which party can afford a discount, which membership credit is safe.
Answers every call, DM and text in seconds, qualifies the patient and books into the Pabau calendar.
Times the comeback from the last treatment in the Pabau chart, in the provider's voice, and writes nothing back into the clinical record.
Checks that written consent to marketing texts is on record before any text goes out, and keeps the message clear of anything clinical; what counts as consent is for counsel to confirm.
Puts every number that matters on one page: calls, bookings, no-shows, reactivations, revenue.

How the connection works

Every platform exposes its data a little differently: an API, scheduled exports, a booking link, or some mix of the three. We confirm what we are connecting to in Pabau on the first call and build on what it exposes. Nothing is written into a patient record until the data flow is agreed in writing. Where a piece of data is not available through an API, the system works from the booking link and the exports, and you are told which is which before anything goes live.

What we need from you

An integration login for Pabau, or the API key Pabau issues, scoped to the calendar and visit dates. The chart stays closed to the system. A scheduled export covers the rest.
The phone number and the social accounts the system should answer for.
Thirty minutes with whoever runs the front desk, so the scripts sound like your practice.

Scoped in writing, built in weeks, covered by the promise

Scoped in writing on the call and built on top of Pabau in weeks rather than quarters. Covered by the same promise as everything we build: results in 90 days, or we keep working until you have them.