Fixed quote after a free call

Digital intake, medical history and insurance prep for dental practices

We build a workflow that sends your intake and medical history forms a few days before each appointment, chases the ones that are not returned, highlights what changed since last time for the clinician and lines up insurance details so staff can verify eligibility before the patient sits down. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.

The problem

Why paper intake slows the dental schedule

Before a patient sits in the chair the practice needs an up-to-date medical history. Forms sent ahead are not always returned, and paper updates completed in the waiting room leave little time to spot a new medication or condition before the dentist needs it.

In the US, insurance adds a second chase: subscriber details, plan, group number and an eligibility check before the visit. Eligibility inquiries and responses have a standard electronic format (the X12 270/271 transaction), but someone still has to collect the right details from the patient and look at the answer.

What we build

What our online dental intake includes

Forms sent before the visit

Your own intake, consent and medical history forms sent automatically a few days before each appointment.

Polite chasing

One or two reminders for forms not returned, then a flag on the day list for the front desk.

Changes highlighted

A short "what changed since last time" summary for the clinician to review, not to act on automatically.

Insurance details ready

Subscriber, plan and group details collected and placed where staff run the eligibility check through your clearinghouse or payer portal.

Into the practice system

Completed forms attached to the patient record through the integration your system offers, or a clean PDF for staff to file.

Day-before check

A list each afternoon of tomorrow's patients with missing forms or unverified insurance.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Appointment booked

    The workflow sees the new appointment in the practice system.

  2. 02 Automated

    Forms sent and chased

    The patient gets a secure link to your forms, with up to two reminders.

  3. 03 Automated

    Changes summarised

    Differences from the last medical history are listed for clinical review.

  4. 04 Staff review

    Staff verify

    Front-desk staff check insurance eligibility and fix any missing details.

  5. 05 Dentist or owner decides

    Clinician reviews

    The dentist reviews the medical history and decides what it means for treatment.

How it behaves

How online intake behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the patient sees

  • A secure link to the practice's forms a few days before the visit
  • Up to two reminders if they have not finished
  • Help at the desk if they prefer paper or a tablet

What staff see

  • A day-before list of missing forms and unverified insurance
  • Insurance details ready for the eligibility check
  • Completed forms attached to the patient record or ready to file

What the automation does

  • Watches for new appointments and sends the right forms
  • Lists what changed since the last medical history for the dentist
  • Never acts on clinical information by itself

Edge cases and fallbacks

Patient never completes the form
They appear on the day-before list and complete it on arrival.
Insurance details missing or wrong
Flagged for staff before the visit, not on the day.
Form submitted twice
The latest version is kept and staff see both.
Write-back to the practice system fails
A clean PDF goes to staff and the failure is logged and retried.
Patient is a minor
Forms go to the parent or guardian contact on file.

Architecture

Patient intake and insurance prep at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Appointment Practice system n8n workflow Send and chase Secure forms History, consent Change summary For clinician Insurance details For eligibility Front desk Verify, fix gaps Patient record Forms attached
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 A new appointment in the practice system starts the workflow.
  2. 2 The patient receives a secure link to the practice's forms, with polite reminders if they are not completed.
  3. 3 Completed forms produce a short summary of what changed and the insurance details staff need.
  4. 4 Staff verify insurance and fix gaps, the clinician reviews the history, and the forms are attached to the patient record.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Digital intake, medical history & insurance prep project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Current forms, where they are stored, how insurance is verified today and what your system can accept.

  2. 02

    Design

    2 to 3 days

    Form fields, reminder timing, change summary format, day-before list and data retention.

  3. 03

    Build

    About 2 weeks

    Secure forms, n8n workflow, practice-system connection and the day-before list.

  4. 04

    Shadow run

    About 1 week

    Forms go to a test group or new patients only while staff compare against the paper process.

  5. 05

    Launch

    1 to 2 days

    Roll out to all appointments and walk the team through the day-before list.

  6. 06

    Support

    Ongoing

    Form changes, new consent wording and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HIPAA- or GDPR-suitable form tool Open Dental API Dentally API Your clearinghouse or payer portals for eligibility Claude or OpenAI for change summaries (under a BAA or processor contract)

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, wording, data flows and the written specification.

    $200 – $400

  • Build

    The n8n workflow, logic, AI step and error handling.

    $500 – $1,300

  • Integrations

    Practice system, phone or messaging and alert channels.

    $150 – $400

  • Testing and shadow run

    QA against acceptance criteria and a side-by-side run with your team.

    $100 – $250

  • Launch and training

    Switch-on, team walkthrough and run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Writing forms back into some practice systems needs an approved integration route; if it does, we quote that part separately. Form and hosting costs are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Form tool: A form provider that signs a BAA or processor agreement, on its published plan, unless your practice system has its own forms module.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; for short sorting and drafting steps usually a small monthly amount at practice volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: HIPAA business associates

Form tools, automation hosts and AI providers that handle patient information need a written business associate agreement before PHI flows.

Source: www.law.cornell.edu

US: eligibility transaction standard

The X12 270/271 eligibility benefit inquiry and response is the HIPAA standard for asking a health plan about an enrollee's coverage; HHS adopted Version 5010 in January 2009.

Source: cms.gov

US: patient right of access

Patients can ask for their records, and covered entities must act within 30 days (one 30-day extension allowed), so forms must be stored where staff can find and export them.

Source: www.law.cornell.edu

EU and UK: health data

Medical histories are special category data under Article 9 GDPR and UK GDPR, so we keep collection to what the practice needs and storage with contracted processors.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Digital intake, medical history & insurance prep questions, answered.

No. At most it lists what changed since the last form so the clinician can find it quickly. The dentist reviews the history and makes every clinical decision.

It gets the right details in front of staff and, where your clearinghouse or practice system supports electronic eligibility checks, prepares them. A person still reads the response and handles anything unclear.

One that will sign a BAA in the US or a processor agreement in the UK and EU, and that your practice system can accept. Some practice systems have their own forms module, and if yours does we connect to that instead.

Some will, so the paper or tablet route stays. The day-before list shows staff who has not completed forms so they can help on arrival.

Attached to the patient record in your practice system where the integration allows, otherwise in a storage location you control. We do not keep copies.

Share of forms completed before the visit, how many patients arrive with unverified insurance and how much check-in time the front desk spends on paperwork.

Free 20-minute call

Want this for your dental practice?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call