Lead Capture7 min read

Dental Practice Intake Form Templates and Field Checklist

Copy-ready dental intake form templates and a field-by-field checklist — a short public booking form plus secure medical, dental, and insurance intake.

Farhad · Founder, GHL Spark

August 1, 2026

Cover illustration — a clean form outline on a dark green background, marked GHL Spark, Lead Capture

In short

A dental new patient form works best as two layers, not one. The public form on your website should be short — name, contact, reason for visit, preferred time — so people actually finish it and book. The clinical detail, meaning full medical history, medications, allergies, and insurance, belongs on a secure intake form the patient completes after booking, ideally through an encrypted portal rather than a public web page. This guide gives you three ready-to-copy field templates using square-bracket tokens, explains which fields to ask and why, and shows where to embed each one so you capture more patients without exposing protected health information.

Key takeaways

Split intake into two forms — a short public booking form to win the appointment, and a secure clinical intake sent after booking
Keep protected health information off any public web page — collect medications, allergies, and history behind a secure, encrypted portal
Ask only what you need at each stage — every extra field on the public form lowers completion and costs you bookings
Design mobile-first — most dental new patient forms are filled on a phone, so use large tap targets, minimal typing, and a single column
Add a clear consent and privacy line, and let one tool host the form, book the appointment, and send reminders so nothing falls through

Some links to tools we rate — including HighLevel — are affiliate links. If you start a trial through them we may earn a commission, at no extra cost to you. We only recommend tools we would set up for our own clients.

A dental new patient form should do one job on your website: get the right person onto the schedule. The mistake most practices make is asking for everything up front — full medical history, insurance, a wall of fields — on a public page. That both tanks completion and puts protected health information somewhere it should never live. The fix is to think in two layers. A short public form captures the booking; a secure clinical intake, sent after the patient commits, gathers the detail. Below are three ready-to-copy field templates, a checklist of what to ask and why, and guidance on where to embed each one.

What is the difference between a public form and a clinical intake?

The public form is a marketing asset. It lives on your homepage and landing pages, and its only purpose is to identify a prospective patient and get them booked. It should ask for the minimum — name, contact, reason for visit, preferred time — because every extra field costs you completions.

The clinical intake is a different animal. It collects medical history, medications, allergies, past dental work, and insurance — all of which is protected health information. That form should be served over a secure, encrypted connection, hosted by a vendor willing to sign a business associate agreement, and reached by a private link in the booking confirmation rather than embedded on a public page. Keeping these separate is the single most important decision in your intake design. If you want the broader playbook, see how to capture leads with forms.

Template 1 — the public new-patient booking form

This is the form that goes on your site. Keep it to a single short screen. Copy the field list and drop it into whatever form builder you use:

[Full name]
[Mobile phone]
[Email address]
[Reason for visit] — dropdown: Checkup and cleaning / Tooth pain or problem / Cosmetic / New patient / Other
[Preferred day and time] — dropdown or date picker
[New or returning patient] — buttons
[Consent checkbox] — I agree to be contacted about my appointment by text and email

That is it. Notice what is not here: no date of birth, no medical history, no insurance. Those belong on the clinical form. The reason-for-visit dropdown does double duty — it routes the enquiry and gives your front desk useful context without free-text typing on a phone.

Template 2 — the secure medical and dental history intake

This form is completed after booking, through a secure link. It can be longer because the patient is already committed. Group it into clear sections:

Patient details

[Full name]
[Date of birth]
[Home address]
[Emergency contact name and phone]

Medical history

[Current medications]
[Known allergies] — include latex and anesthetics
[Medical conditions] — checklist: heart condition / diabetes / high blood pressure / pregnancy / bleeding disorder / other
[Primary care physician]

Dental history

[Reason for today's visit]
[Date of last dental visit]
[Current dental concerns or pain]
[Do you experience dental anxiety?] — yes / no
[How did you hear about us?]

Because every field above is clinical, this form must never sit on a public URL. Serve it securely and store it in a system that meets your compliance obligations.

Template 3 — the insurance intake

Insurance can be its own short secure form or a section of the clinical intake. Many practices choose to verify by phone instead of storing card images online — decide based on your workflow:

[Insurance carrier]
[Member ID number]
[Group number]
[Policyholder name]
[Policyholder date of birth]
[Relationship to patient]

Keep this behind the same secure connection as the medical intake, and avoid asking patients to upload photos of cards on a public page.

Which fields do you actually need, and why?

Here is a field-by-field reference across all three templates, so you can decide what to include and where.

Field	Why you ask	Required?
Full name	Identifies the patient and personalizes follow-up	Yes — public
Mobile phone	Enables reminders and quick rescheduling	Yes — public
Email address	Sends confirmations and the secure intake link	Yes — public
Reason for visit	Routes the enquiry and preps the front desk	Yes — public
Preferred day and time	Speeds booking and reduces back-and-forth	Recommended — public
Consent checkbox	Permission to contact; compliance	Yes — public
Date of birth	Confirms identity; clinical records	Yes — secure
Current medications	Safety before any treatment	Yes — secure
Allergies	Prevents adverse reactions	Yes — secure
Medical conditions	Informs safe treatment planning	Yes — secure
Dental history	Context for the exam	Recommended — secure
Insurance details	Billing and eligibility	As needed — secure

The pattern is consistent: contact and intent on the public form, anything clinical or financial on the secure one.

How do you make the form mobile-first?

Most dental new patient forms are filled on a phone, often while the person is sitting on your website deciding whether to book. Design for that. Use a single column so nothing gets lost side-to-side. Use large tap targets and the correct input types, so a phone field brings up the number pad and an email field the email keyboard. Replace free-text with dropdowns and buttons wherever you can — thumbs hate typing. And keep the public form to one screen with an unmissable submit button. A form that is fiddly on mobile loses bookings silently; you never see the people who gave up halfway.

Consent is not a formality — it is what gives you permission to text and email the patient, and it is part of staying compliant. On the public form, a single plain-language checkbox is enough: state that the patient agrees to be contacted about their appointment by text and email, and make it explicit rather than pre-ticked. That one line unlocks your entire reminder sequence.

On the secure clinical intake, add the fuller consent and privacy language your practice requires — how you use and store the information, and any acknowledgements a first visit needs. Keep the wording readable rather than a wall of legalese; a patient who understands what they are agreeing to is a patient who trusts you. Store a record of the consent and the timestamp, so you can honor an opt-out immediately if someone replies STOP or asks to be removed.

What are the most common dental intake mistakes?

The biggest one is a single monster form that asks for medical history on a public page. It scares people off and creates a compliance exposure at the same time. The second is free-text everywhere — asking a patient to type paragraphs on a phone guarantees drop-off. The third is burying the form: if a visitor has to scroll or click twice to find how to book, many will not bother. And the fourth is collecting information you never use. Every field should earn its place by feeding a real step in your workflow, whether that is booking, treatment safety, or billing. When in doubt, cut a field from the public form and move it to the secure intake, or drop it entirely.

Where should you embed each form?

Put the public booking form where intent is highest: your homepage, a dedicated new patient page, and any landing page you send ads or dental practice marketing traffic to. The moment a visitor decides, they should be able to act without hunting for a phone number.

Send the secure clinical intake as a private link in the booking confirmation email and in appointment reminders, so the patient completes it before they arrive and your front desk is not typing it in at check-in. For more tactics across the whole patient journey, browse the Dental Marketing hub.

Can one tool host the form, book the appointment, and send reminders?

You can stitch together a form builder, a scheduler, and a texting app — but that is three logins and three places for a lead to fall through. An all-in-one platform lets a patient submit the booking form, pick a time, and then receive automatic confirmation and reminder messages, all from one system. HighLevel is one option that does this. Honestly, its appeal is not the lowest sticker price — it is the consolidation. Replacing several disconnected tools with one that captures, books, and reminds usually saves more in wasted leads and admin time than the subscription costs. If a single connected system fits how your practice runs, you can start a free HighLevel trial and test it against your current setup.

Whichever tools you use, the design principle holds: capture the appointment with a short public form, gather the clinical detail through a secure channel, and keep protected health information off any public page. That combination books more patients and keeps you on the right side of privacy.

Want help wiring this up for your practice? See our pricing or book a call and we will map the intake flow with you.

Frequently asked questions

What is a dental new patient form?

A dental new patient form is the information a practice collects from someone visiting for the first time. In practice it is usually two forms — a short public form on the website that captures name, contact details, and reason for visit so the person can book, and a longer clinical intake form the patient completes before or at the first appointment covering medical history, medications, allergies, and insurance. Splitting it this way lifts completion rates and keeps sensitive detail off public pages.

What fields should a dental intake form include?

At minimum, capture the patient's full name, phone, email, reason for visit, and preferred appointment time on the public form. The secure clinical intake then adds date of birth, medical history, current medications, allergies, past dental history, and insurance details. Only ask for what you will actually use at each stage — a public form should stay short, while the clinical form can be thorough because the patient has already committed.

Is an online dental intake form HIPAA compliant?

It can be, but the public form on your marketing site should never collect protected health information. Keep medical history, medications, diagnoses, and similar detail on a secure intake form served over an encrypted connection, hosted by a vendor willing to sign a business associate agreement. A short public booking form that only gathers name, contact, and reason for visit carries very little risk because it holds almost no clinical data.

What is protected health information on a dental form?

Protected health information is any detail that links a person to their health, care, or payment for care. On a dental form that includes medical conditions, medications, allergies, diagnoses, treatment history, and insurance and billing details tied to the patient. A name and phone number submitted to request an appointment is contact information, not clinical data, which is why a short booking form is lower risk than a full history form.

How long should a dental new patient form be?

The public booking form should be short — four to six fields is ideal, enough to identify the person and get them on the schedule. The secure clinical intake can be longer because the patient has already booked and is motivated to finish it before their visit. The rule is to match length to stage — brief to capture, thorough once committed.

Should medical history go on my website form?

No. Medical history belongs on a secure intake form the patient completes after booking, ideally through an encrypted patient portal rather than a public web page. Putting full history on a public marketing form both lowers completion and creates a compliance exposure. Capture the appointment first with a short form, then send the clinical intake through a secure link.

How do I collect insurance details safely?

Collect insurance information on a secure intake form after the appointment is booked, never on the public page. Ask for the carrier, member and group numbers, and the policyholder's details, and serve the form over an encrypted connection from a vendor that will sign a business associate agreement. Many practices simply verify insurance by phone or at check-in to avoid storing card images online.

Why split intake into two forms?

Two reasons — conversion and compliance. A short public form gets far more people to finish and book because it asks very little. Keeping clinical detail on a separate secure form means your marketing site never holds protected health information. You capture the lead first, then gather the detail through a secure channel once the person is committed to the visit.

Where should I embed a dental intake form?

Put the short booking form on your homepage, your new patient page, and any landing page you run ads to, so a visitor can act the moment they decide. Link to the secure clinical intake from your booking confirmation email and appointment reminders, so the patient completes it before arriving. Keeping the public embed short and the clinical form behind a link serves both goals.

Can one tool handle the form, booking, and reminders?

Yes. Platforms that combine forms, scheduling, and messaging let a patient submit the booking form, pick a time, and then receive automatic confirmation and reminder messages without manual work. HighLevel is one such option. The value is not the lowest price but the consolidation — one system instead of a form builder, a scheduler, and a texting tool stitched together.

How do I make a dental form mobile-friendly?

Assume most patients fill the form on a phone. Use a single column, large tap targets, and the right input types so the correct keyboard appears for phone and email fields. Minimize typing with dropdowns and buttons where you can, keep the public form to one short screen, and make the submit button unmissable. A form that is awkward on mobile quietly loses you bookings.

Do I need patient consent on an intake form?

Yes. Include a short, plain line stating how you will use the information and how the patient can be contacted, with a checkbox to agree — especially for text and email reminders. On the clinical intake, add the consent and privacy language your practice requires. Clear consent protects the patient, keeps you compliant, and gives you permission to follow up.

About the author

Farhad

Founder, GHL Spark

Farhad is the founder of GHL Spark, where he builds and white-labels GoHighLevel SaaS platforms for agencies and SaaS operators. He writes about the parts of GoHighLevel that actually break in production — A2P registration, onboarding, support load and automation.