Integrations

Works alongside the EHR you already run.

No rip-and-replace. The receptionist answers your phones, books on your schedule, and hands your team call summaries and tasks. Booking works from day one on the schedule kept in the dashboard; the EHR connection is added at onboarding.

No rip-and-replace

Booking works from day one on the schedule kept in the dashboard.

Confirm the connection before a live booking.

A FHIR interface does not guarantee that every scheduling action is available. Validate the workflow your practice actually needs.

Access and permissions

Identify your EHR version, API access, patient-matching rules, and the permissions needed to read availability and change appointments.

A complete test visit

Book, reschedule, and cancel a test visit. Confirm the right provider, visit type, duration, and status appear in the system your staff uses.

Failures and conflicts

Test an expired connection, an unavailable slot, and two callers choosing the same time. Agree which cases need staff review.

One schedule of record

Without a validated EHR connection, bookings stay in the Callinzo dashboard. Assign a reconciliation process before enabling live scheduling.

EHR and practice management

Systems to evaluate during onboarding, not a claim of a completed connection for every practice. Access, vendor approval, and supported scheduling operations must be confirmed and tested.

At onboarding

Epic

Confirm your API access and scheduling workflow

At onboarding

athenahealth

Confirm your API access and scheduling workflow

At onboarding

eClinicalWorks

Confirm your API access and scheduling workflow

At onboarding

ModMed

Confirm your API access and scheduling workflow

At onboarding

AdvancedMD

Confirm your API access and scheduling workflow

Built

FHIR R4 adapter

Tested against a stand-in server; validate against your system

Phone lines

Keep your number and forward it, or take a number from us.

Built

Your carrier, by SIP trunk

Twilio and other carriers, digest credentials and encrypted media

Built

A number from us

Provisioned in minutes, inbound

Built

Concurrent calls

Capacity per deployment, with admission controls

Messages

Confirmations, reminders, and expiring links. Keep clinical concerns out of message bodies; review the templates and recipients for your practice.

Built

Text messages

Twilio, from your number

Built

Email sign-in codes

Your SMTP sender

In the pipeline

WhatsApp

Built, awaiting account approval

Speech and languages

Hosted vendors under agreement, chosen per language.

Built

Live languages

Hosted listening and speaking with your practice's vocabulary; the languages page lists what is live

In the pipeline

More languages

Each on its own speech vendor under the same terms, switched on per practice as it goes live

Data out

Your records are yours.

Built

Reports export

CSV from the Reports screen

Built

Learning set

De-identified records in your own region's store, only where allowed

Don't see your EHR?

The receptionist's routing is configurable, and after-hours coverage runs without any integration: every call answered, your escalation criteria applied, the on-call texted a secure summary link. Booking without a connection lands on the schedule kept in the dashboard, which your staff can run from day one. Tell us your system and we will tell you honestly what we can commit to.

Your systems, your questions.

Can Callinzo book, reschedule, and cancel visits in our existing EHR?

That depends on the access and scheduling operations your EHR supports. Callinzo has a FHIR adapter; a named EHR on the integrations page is not a preconfigured connection for every practice. During onboarding, confirm permissions and test patient matching, availability, booking, changes, and cancellations against your system. Without a validated connection, bookings stay on Callinzo's dashboard schedule and your staff needs an agreed reconciliation process.

Can scheduling follow each provider's visit types, durations, and booking rules?

Yes. Configure providers, hours, visit types, appointment lengths, and scheduling rules for your practice. Specialty packs provide starting points, not automatic approval of every appointment. The booking workflow checks availability and rules before confirmation. Requests that cannot satisfy a rule need staff review; verify representative new-patient, follow-up, and procedure-related scenarios before forwarding live calls.

Can we keep our number and use AI only for overflow or after-hours calls?

You can keep the practice's number and configure forwarding with your phone provider. Agree whether all calls, unanswered calls, or calls during closed hours should forward, and test how to return the line to staff. Overflow forwarding and your billing plan are separate choices: confirm the right plan for your hours. Calls handled during open hours on the nights-and-weekends plan still incur the same usage rate.

Can an AI receptionist handle several patient calls at once?

Yes, within the capacity configured for your deployment and phone carrier. Callinzo supports concurrent calls with admission controls; capacity is not unlimited. Share your busiest hour and peak simultaneous calls during onboarding, and test the limit and overflow route. A useful acceptance test includes several callers booking the same available time, so capacity and scheduling conflicts are checked together.

Browse all questions and answers

Tell us what you run.

We will tell you honestly what we can commit to, and what works on day one without a connection.