01What your booking app already holds, and where it stops
A dental booking app, or the practice management software behind it, already holds the appointments, usually the patient records and often the reminders. It knows everyone who has come. It tends to know nothing about people who have not booked yet: the enquiry from the website form that nobody called back, the message on Instagram, the patient who was given a treatment plan and said she would think about it. We have not compared dental software and name none, because features differ and change. Ask your vendor three things. Can it list patients due for a check-up who have no appointment? Can it record where a new patient came from? Can it hold a follow-up date on an enquiry that is not an appointment yet?
- Appointments, records and reminders: usually already in the booking app
- Enquiries that never became appointments: usually not
- Ask your vendor: a due-for-check-up list, the source of each new patient, a follow-up date on an enquiry
02When a CRM earns its place
A CRM earns its place in three situations. Enquiries arrive through several doors (a form, a message, an email, an ad) and nobody owns the answer, so some wait for days. Treatment plans are presented and not accepted, and there is no polite next step with a date on it. Patients overdue for a check-up exist in the app, but nobody works the list. In each case the pain is a follow-up that depends on someone remembering. A CRM turns that into a stage and a date: new enquiry, contacted, consultation booked, plan presented, accepted, scheduled, each with a next-action day. If you cannot say which of the three hurts, you do not need one yet.
- Enquiries through several doors and no owner for the answer
- Treatment plans presented and left without a dated next step
- Overdue patients in the app and nobody working the list
- Stages with a next-action day: new, contacted, consultation booked, plan presented, accepted, scheduled
03Patient data: keep health details out of the CRM
Article 9(1) of the GDPR prohibits processing data concerning health unless an exception applies, such as explicit consent for specified purposes (Article 9(2)(a)). Treatment records are the obvious example. Even a note like interested in implants next to a named person may reveal something about health, and whether it does is a question for your data protection adviser. The safe default is a CRM that holds only what it needs to follow up: name, contact details, where the person came from, the stage and the next-action date. Clinical detail stays in the clinic's own record system. Where the CRM is hosted, who can open it and how you export and delete one person's data are things to ask before you buy. This is not legal advice.
- CRM fields: name, contact, source, stage, next-action date
- Clinical detail stays in the clinic's own record system
- Ask the vendor: where it is hosted, who can open it, how one person's data is exported and deleted
- Your data protection adviser decides what counts as health data in your case
04The cheap test before you buy anything
For four weeks, keep one shared sheet with a line for every enquiry that does not become an appointment on the spot: date, name, contact, where it came from, what happens next and on which day. One person opens it every morning. At the end, count how many lines moved to a booked visit, how many were forgotten and how many came from one source. If the sheet worked, you may not need software, or you now know exactly what the software must do. If nobody kept the sheet up, a CRM will not be updated either, which is why a CRM only helps when bookings and replies feed it automatically. We have not measured how many dental enquiries go unanswered, and we will not guess.
- Four weeks, one shared sheet, one person who opens it each morning
- Per line: date, name, contact, source, next step, day of the next step
- Count what became a visit, what was forgotten and which source it came from
- A sheet nobody maintains predicts a CRM nobody updates
05Where PROOF48 is the wrong choice for a dental practice
None of our eight builds written up at /work is a dental practice. AUTOMATE, at 2,997 EUR a month, lists an AI website chatbot that qualifies and books, AI DM and email auto-responders, booking automation with a CRM, and everything in GROWTH. We do not claim it reads your clinic software, holds clinical records or connects to your booking app. Two custom automations a month are included, and any connection would be scoped first. It does not cover WhatsApp or phone calls, which matters if your patients mostly call. It is the wrong purchase for a one-dentist practice that lives on referrals. A patient system built around your own workflow is a web app, from 5,000 EUR, and larger or custom projects may need a deposit, as our terms say.
- None of our eight written-up builds is a dental practice
- We do not claim AUTOMATE reads clinic software, holds clinical records or connects to your booking app
- No WhatsApp or phone calls in AUTOMATE
- A one-dentist practice that lives on referrals does not need it
One calendar, not two
None of our eight written-up builds is a dental practice. The closest pattern is SCP Shine & Style, a salon whose booking flow points at the salon's live booking platform. That is the rule we would hold a dental CRM to: one calendar owned by the practice, with anything else reading from it rather than competing with it. We do not publish the salon's booking counts, because we do not measure them.
See the build: SCP Shine & StyleQuestions, answered
Is a dental booking app a CRM?
Not usually. A booking app holds appointments and often records. A CRM follows people before they book and between visits. Some booking apps cover part of that, so ask your vendor before you add another tool.
Should patient treatment details go into a CRM?
The safe default is no. Article 9(1) of the GDPR prohibits processing data concerning health unless an exception applies. Keep clinical detail in the clinic's own record system and ask your data protection adviser what else counts.
Can PROOF48's CRM connect to my clinic software?
We do not claim that. AUTOMATE lists booking automation with a CRM, a website chatbot and DM and email auto-responders. A connection to your software would be scoped first, and we would tell you in the first reply whether it fits.
Does a small practice need one?
Often not. If patients come by referral and the app lists who is due, a shared sheet for new enquiries is enough. A tool earns its cost when several people share the same enquiries and some go unanswered.
Where PROOF48 fits
A dental practice needs a CRM when enquiries and unaccepted plans fall between the booking app and the front desk, and when something automatic feeds it. Health details stay out of it, and one calendar stays the practice's own. PROOF48's AUTOMATE plan, at 2,997 EUR a month, includes a CRM with booking automation. None of our written-up builds is a dental practice, and a referral-led practice does not need it.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.