Patient Intake

Which questions to ask, in what order, and where the follow-ups branch

The script is the product. How a Fresno clinic decides required versus optional fields, orders the questions so callers stay with it, and sets the conditional follow-ups that fire when an answer needs one.

Required versus optional: decide which fields a call is not allowed to end without
Order the script so demographics come first and clinical detail comes once the caller has settled in
Conditional follow-ups do the real work: a reported allergy prompts medication screening, a symptom prompts risk questions
Specialty variants let primary care, orthopedics and cardiology run different question sets in one clinic
An unclear answer gets a clarifying question while the caller is still on the line, not a blank field at check-in
Where the script cannot resolve an answer, the gap is flagged so staff can close it deliberately

How it pays back

The script belongs to your clinic

Questions, required fields and risk flags are set by your practice rather than inherited from a template. If your intake asks something unusual because of how your clinic works, the script asks it too.

Follow-ups fire where a paper form stops

A form takes 'penicillin' and moves on. A script can branch into a medication screening question the moment an allergy is reported, so the follow-up happens while the patient is still there to answer it.

Specialty question sets without a second system

An orthopedic intake and a cardiology intake can differ in required fields and risk flags while producing the same structured summary format for staff to review.

Unanswered is labelled, not silent

When information stays incomplete after a clarifying attempt, staff receive a note naming the gap. A missing field your team knows about is a two-second question at the window; one nobody flagged is a delay in the room.

The script is meant to be rewritten

After the first weeks, the questions your staff keep re-asking are the ones to add, and the ones nobody uses are the ones to cut. Changes apply to the next call without rebuilding the workflow.

Structured intake on first call

Demographics, insurance, medical history, symptoms captured intelligently

Insurance information captured

Handed to billing staff for pre-verification—not auto-populated to EMR

Summary returned to staff

Your team reviews, verifies, and files into patient record

No paper forms at arrival

Fresno patients check in with intake complete

Clinical data ready for review

Chief complaint, allergies, medications, and history in structured format

Conditional logic

Follow-up questions adjust based on patient responses

Frequently asked questions

What belongs in the intake script, and what should be left for check-in?

Put anything you would otherwise collect by phone or on a clipboard into the script: demographics, insurance, allergies, medications, reason for visit. Leave signature-dependent steps and anything your staff must verify against a physical document for the desk.

How do conditional follow-up questions actually work?

Answers trigger branches you define. Reporting an allergy prompts medication screening; describing a symptom prompts the risk questions attached to it. The branch is part of the script, so every caller who gives that answer gets the same follow-up.

Can the question set differ by specialty inside one clinic?

Yes. You can set intake questions by specialty, flag risk conditions, and define required versus optional fields per set, so a primary care call and an orthopedic call do not have to share one questionnaire.

What happens when a caller gives a vague or partial answer?

The script asks a clarifying follow-up in real time. If the answer is still incomplete, your staff receives a note flagging the gap so it can be closed at check-in or before the clinical visit.

How long should a new patient intake script be?

Roughly as long as the information you collect today by another route. The useful test is whether your staff re-asks a question anyway; questions that get re-asked belong in the script, and questions nobody uses belong out of it.

Who owns the script once we are live?

Your practice does. Questions, required fields and risk flags are configuration, so the office manager or clinical lead who owns your intake workflow can change them as that workflow changes.

Bring this to your practice

See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.

Book a Demo Contact Us

Want the numbers first? See plans and pricing