Patient Onboarding

The question isn't whether an AI can ask about allergies. It's whether a nervous new patient will answer.

How a phone intake is designed so it doesn't feel like an interrogation: choosing which questions get asked, asking them conversationally instead of as a script, what happens when a patient would rather not answer, and how the phone path sits alongside a portal.

You define the question set: allergy screening, medication list, reason for visit, past medical history, smoking status, and whatever else your specialty needs
Questions are asked conversationally rather than read from a rigid script, so the call sounds like a conversation instead of a form being completed
A patient who would rather not answer is not pushed; what they will share is logged, and a callback or an in-person form is offered for the rest
The appointment time, provider name and reason for visit are repeated back before the call ends, so the patient leaves the call certain about all three
Staff can review the intake summary before the patient arrives and flag anything missing or worth a follow-up question
Practices running a patient portal keep it: the phone path and the web path both end in the same reviewed workflow

How it pays back

Your questions, not a generic questionnaire

A pediatric intake and an orthopedic intake are not the same conversation. Defining the question set yourself is what stops the call asking things that do not apply and skipping the one thing your clinicians always want to know.

Declining is a supported answer

Some patients will not discuss medications with an automated caller, and pushing them is how you lose both the intake and the appointment. Logging what they will share and offering another route keeps the booking intact.

Repeating it back ends the ambiguity

Hearing the time, the provider's name and the reason for the visit read back is what prevents the patient who arrives on the right day expecting a different doctor. It costs ten seconds at the end of a call.

The portal is not the competition

Some new patients will always prefer to book online and type their own history; others will always call. Running both paths means you are not asking a patient to use the channel that suits your workflow rather than theirs.

Structured intake captured

Chief complaint, allergies, meds, past medical history—all documented in one call

New patient created automatically

Name, DOB, phone, address written to EMR; demographics ready for clinical staff

Insurance contact logged

Caller provides insurance information; staff can verify before appointment arrives

Pasteable clinical summary

AI-generated intake note ready for staff review and chart filing

Frequently asked questions

Will a new patient really answer medical questions to an AI on the phone?

Many will, and the design of the call is what decides it. Questions asked conversationally, in an order that makes sense, with a clear reason for asking, get answered. A rigid script read at someone gets a short call and a half-empty summary.

What if a patient is anxious or does not want to answer?

The call stays warm and does not press. What the patient is willing to share is logged, and the option of a callback from your staff or completing the rest in person is offered. The appointment still books; the intake is what gets deferred.

Can we choose which questions get asked?

Yes. You define the intake questionnaire — allergy screening, medication list, reason for visit, past medical history, smoking status and anything else you want covered — and the questions are asked conversationally rather than read verbatim.

Does the AI write the clinical note?

No. It captures information and returns it as a structured, pasteable summary. Your clinical staff decides what belongs in the official note and files it. That boundary is deliberate, and it is what keeps clinical oversight with your clinicians.

We already have a patient portal. Does this replace it?

No. Phone intake complements a portal rather than competing with it. Patients who prefer to schedule online and complete forms there still can; the phone path covers everyone who picks up the phone instead, and both end with your staff reviewing structured data.