Skip to content

Integrations

It works with what you run.
You don't do the work.

Most tools in this category mean something specific by "integration": here are the credentials, here's a settings page, good luck. This one means we connect it, test it, and keep it working — and your team never opens it.

What connects

Five connections, and who they're for.

Your calendar

Bookings land in the calendar your practice already runs on, entered the way your own front desk would enter them — service, provider, duration, and the notes you asked for. This is the connection that matters most and it's on every tier, because a booking that doesn't reach your calendar isn't a booking.

Every plan

Your phone number

Callers keep dialling the number on your door, your listings and your ads. We configure the routing so nothing changes for them and nothing changes on your printed material. You keep the number.

Every plan

The systems you keep records in

Call details and captured leads flow into the system you already use to track patients, so the record of a 9 PM enquiry is where your team looks in the morning rather than in a separate inbox. What that looks like depends on what you run — which is a conversation before you commit, not a promise on a page.

Growth and Pro

Webhooks, API and Zapier

Most modern practice software exposes one of these, and where yours does, it's usually how the connection gets made. It's also the honest answer to "do you integrate with X" for a long tail of systems nobody has a logo for: often yes, and we'll confirm yours specifically rather than guess.

Where a system supports it

Text messaging

Confirmations, reminders and follow-ups send from your business number once U.S. carrier registration clears — typically 10–14 business days from the day we receive your EIN. We file it; you don't. See the A2P guide for what that process actually involves.

Every plan, after carrier registration

Why this is the part to compare

"Integrates with" is doing
a lot of work in that sentence.

Nearly every product in this category can claim it. The difference is whose evening it is when the connection needs building, testing, and fixing.

The full comparison: vs. DIY AI tools →

The integration work is ours

This is the part worth comparing. Self-serve AI receptionist tools integrate in the sense that they give you the credentials and a settings screen — connecting, testing and maintaining it is your evening. Here it's onboarding: you tell us what you run, we build against it, and we're the ones who fix it when something changes.

Nothing for your team to install or learn

No new dashboard, no logins to distribute, no software project. Your existing scheduling stays the source of truth; LunaFront feeds it around the clock.

It changes when you change

Add a service, move a provider, switch systems entirely — you tell us and we update the configuration. There's no migration on your side and nothing to re-learn, because you were never operating it.

We confirm your stack before you commit

If you run something less common or custom, that gets checked on the consultation — before you sign, not after. A clear "that one we'd need to look at" is worth more to you than a logo wall that turns out to mean a CSV export.

Questions

Asked before signing.

Do you integrate with the system I already use?

Usually, and the answer is worth getting specifically rather than generally. Tell us what you run on a consultation and we'll confirm it before you commit — including telling you if it's one we'd need to look at first.

Do I have to change how my practice schedules?

No. That's the design. Your existing scheduling stays the source of truth and LunaFront feeds it; the alternative — moving your practice onto someone else's calendar to suit their software — is the thing we're avoiding.

Who sets the integration up?

We do, during onboarding, and we maintain it afterwards. There's nothing for you or your staff to install, connect or monitor.

What if I switch systems later?

You tell us and we reconfigure it. No migration on your side, and nothing to re-learn, because you were never the one operating it.

If it doesn't cover its plan fee in 30 days, we refund that fee.

If LunaFront doesn't book enough in your first 30 days after go-live to cover your monthly plan fee, we refund that month's plan fee. The one-time $299 setup fee is not refundable.

No lock-in

Every plan is month-to-month. Cancel any time, no cancellation fee.

A known worst case

The most you can be out is the one-time $299 setup.

Tell us what you run

Fifteen minutes, and you'll know whether your stack is a fit before you commit to anything.