Five founding places open
ALPHA startup · Web Summit Lisbon 2026Patients enquire. Then they go quiet.
ReplyOS replies in seconds and keeps the conversation going until they book.
WhatsApp · Sunday 21:02 · sample enquiry
“Hi, do you do Invisalign? Roughly how much is it?”
Replied 21:03Approved by reception Mon 08:31Booked Thu 16:30 · consultation
Every channel your patients use, in one inbox: WhatsApp, Instagram, Facebook, website chat, SMS and email. Your reception team approves each reply with one tap and books the patient exactly as they do now. Quiet enquiries are followed up politely on Pro and Scale, and handed to a person the moment one is needed.
See what your receptionist sees ↓
No commitment during setup. Billing only starts once your system is live.

The ReplyOS console as it ships. Northgate Dental Group is a sample workspace with generated data — not a customer, and not a customer result.
- First reply on connected channels
- Seconds
- Evenings and weekends captured
- 24/7
- WhatsApp, SMS, email, webchat, calls
- One inbox
- Until your system is live
- £0
Straight answers
What ReplyOS does, and what it doesn’t
It does
- Replies to patient messages within seconds, 24 hours a day, using your practice’s own answers: treatments, fees, opening hours, who does what.
- Puts WhatsApp, Instagram, Facebook, website chat, SMS and email into one inbox, one thread per patient.
- Texts back anyone whose call to your ReplyOS practice number goes unanswered, so they don’t ring the practice down the road.
- Follows up politely when a patient goes quiet, then stops the moment they answer, book, or a team member takes over.
- Hands anything clinical or awkward to a named person on your team, with the whole conversation attached.
- New on Pro and Scale: publishes your services, guide prices and hours in a form AI assistants can read, and lets them pass on a patient’s enquiry when the patient asks. It lands in your inbox; your team replies.
It doesn’t
- Replace your reception team. Every reply can be approved by a person before it goes out, until you choose otherwise.
- Give clinical advice. It reassures, offers an appointment and passes the question to a clinician.
- Touch your diary or your practice software. Booking stays exactly as it is now.
- Need your team to learn new software. They read a suggested reply, tap Approve, and book as usual.
Channel availability is set by plan. See what each plan includes.
New on Pro and Scale
A front desk for AI assistants
Patients are starting to ask AI assistants to find a practice. ReplyOS publishes your services, guide prices and hours for them to read and quote, and marks the enquiries that came from ChatGPT and other assistants so you can see what they booked. Nothing is sent to the patient automatically.
Try it as a patient
Ask about implants. Then see what your team sees.
This is the real ReplyOS chat, running for Northgate Dental, a sample practice with sample fees. Type as a patient would. The panel on the right is the same conversation from the reception side, in the ReplyOS inbox.
You, as a patient
Northgate Dental · sample practice
Sample fees, sample clinicians. Messages you send here go to the demo practice’s inbox, not to a real dentist, and are used only to run this demo.
What your team sees
The ReplyOS inbox row for this conversation. Sample data.
Want the missed-call version too? Ring the sample practice on a demo call and watch the text-back land as an enquiry.
Revenue infrastructure
See leakage, inbox, and revenue in one command centre
Every enquiry tracked from first message to booked outcome — with £ at risk, recovery queues, and channel performance your team can act on today.

See what is leaking — and how much of it is still recoverable.
Real ReplyOS console · demo practice data, not customer results
A normal week
Sound familiar?
Day 1
Sunday, 9pm
Someone on the sofa messages your Instagram: “Do you do composite bonding? How much?” They have messaged two other practices as well. The one that answers first gets the consultation.
Instagram, Facebook and WhatsApp are included on Pro and Scale.
Day 2
Tuesday, 12:50
Three calls ring out while your receptionist checks in a patient and takes a payment. Two of the callers were new patients. Neither leaves a voicemail.
Missed-call text-back runs on your ReplyOS practice number. We set up the call routing with you.
Day 3
Thursday, sometime
An email about an emergency appointment has been sitting in the shared inbox since Monday. Nobody quite owns it.
More on missed calls: missed-call recovery for dental practices.
What patients actually ask
The eight messages every practice gets, answered properly
During setup we ask your team how you answer each of these. ReplyOS then answers the same way, every time, at any hour, and hands the thread to a person the moment it should.
01 / 08
“Are you taking on new NHS patients?”
Answers with your current NHS position and, if you are full, offers the private new-patient exam or the waiting list, whichever you have chosen.
02 / 08
“How much is a check-up?”
Answers with your NHS band or private fee, what it includes, and invites them to book.
03 / 08
“Do you do Invisalign? How much?”
Answers with the clinician, the from-price, finance if you offer it, and offers a consultation.
04 / 08
“I’ve chipped a tooth, can I be seen today?”
Reassures, explains how you handle emergencies, and flags the thread to a person straight away.
05 / 08
“Can I book a hygienist appointment?”
Answers with the fee and appointment length, and hands the booking to your team.
06 / 08
“Do you offer 0% finance?”
Answers with your finance arrangement and terms, in the words your team gave us.
07 / 08
“Are you open Saturdays?”
Answers with your hours, and invites them to book if you have weekend slots.
08 / 08
“Is my tooth infected? It’s throbbing.”
Does not diagnose. Offers an urgent appointment and passes the message to a clinician with everything the patient said.
Quiet enquiry follow-up
When a patient goes quiet,
ReplyOS follows up. Then it knows when to stop.
Most lost treatment is not a “no”. It is an enquiry that got a good first reply and then silence — on both sides. ReplyOS watches every open thread, and when one goes quiet it sends a follow-up in your practice’s voice with the treatment context intact, on the channel the patient already used.
Automatic sending is switched on per practice. Until then, follow-ups are drafted for your team to approve. WhatsApp follow-ups are included on Pro and Scale.
Rule 1
Stops the moment the patient replies
A new inbound message cancels the pending follow-up. Nobody gets chased after they have answered.
Rule 2
Stays out of booked, closed and handed-off threads
Converted enquiries, closed ones, and anything a team member has taken over are never touched.
Rule 3
A capped number of attempts, with a cooldown between them
Each practice sets its own limit. Follow-ups are spaced out, not stacked, and every attempt is logged on the thread.
Rule 4
Written from the conversation, not a template
The follow-up references the treatment the patient asked about and the practitioner they were offered, in your tone of voice.
For your practice manager
The compliance bit, in plain English
01
Your practice stays in charge of the data
Under UK GDPR you are the controller and ReplyOS is your processor. A data processing agreement is signed before anything goes live.
02
Registered with the ICO
Reply Intelligence Group Ltd, registration ZC192287. You can check it on the ICO register.
03
Only the right people see patient messages
Every user has their own login and role. Every reply, edit and hand-off is logged, so you can show who did what.
04
Encrypted, and never sold
Connections are encrypted with TLS and stored data sits on encrypted disks at our hosting provider. We do not sell patient or practice data.
Full security overview, sub-processor list and DPA available before you sign anything. Security & trust centre.
Trust centre
Security & data protection
Built for practices where patient enquiries are sensitive. ReplyOS acts as your data processor — you stay in control, with clear access boundaries and no data resale.
Encrypted connections to ReplyOS
Your practice stays the controller
Reply Intelligence Group Ltd
Role-based permissions and audit trail
Cloud provider disk encryption
Data Processing Addendum available for founding practices. Read DPA
Guides for dental practices
The questions practices ask before they buy anything
- How do dental practices recover missed calls?
Log every unanswered call as an enquiry, text the caller back within seconds, and order the callback queue by treatment value and time waiting.
- What is revenue leakage in a dental practice?
Treatment value lost between a patient's first enquiry and a booked appointment: calls that ring out, slow replies, quiet threads and unchased treatment plans.
- How much are missed dental enquiries costing you?
A calculator from three numbers you set: enquiries per day, the share missed or late, and average treatment value. Every assumption labelled illustrative.
- What is dental lead management software?
Software that tracks prospective patients from first enquiry to booked treatment, sitting before the practice management system.
- When does an AI receptionist fit a dental practice?
When messages and calls go unanswered at busy or closed times. Not when the problem is clinical judgement, diary management or an unhappy patient.
- All guides, each with a one-line answer
Questions practices ask us
Frequently asked questions
Direct answers about ReplyOS for dental and aesthetics practices. More on how dental practices manage patient enquiries.
01What is ReplyOS?
ReplyOS is an AI-native revenue infrastructure platform that helps UK dental and aesthetics practices stop revenue leakage: capturing patient enquiries, replying in seconds across connected channels, and including Reputation Shield to protect reviews after treatment.
02How much revenue do dental practices lose from slow responses?
Many practices lose thousands per month when high-value enquiries are missed or answered slowly. An illustrative model using a few missed enquiries per day can show £30,000 or more per year at risk; estimate with your own assumptions on the ROI page.
Estimate it with the ROI calculator →03Does ReplyOS follow up enquiries that go quiet?
Yes. When an open enquiry gets no reply, ReplyOS sends a follow-up in your practice’s voice with the treatment context intact, on the channel the patient used. It stops as soon as the patient replies, the enquiry is booked or closed, or a team member takes over, and each practice sets a maximum number of attempts with a cooldown between them. Automatic sending is switched on per practice; otherwise follow-ups are drafted for your team to approve.
04Does ReplyOS replace my reception team?
No. ReplyOS assists your reception team; it does not replace them. It helps capture enquiries, respond quickly, qualify patients, and hand off to your team with full context when a human is needed.
05What channels does ReplyOS support?
ReplyOS unifies WhatsApp, SMS, email, web chat, Instagram, and Facebook in one inbox. Core plans launch with webchat, SMS, and email; Pro and Scale add social messaging channels.
06What is revenue leakage in a dental practice?
Revenue leakage is treatment value lost when enquiries are missed, answered too slowly, or never guided to a booking. ReplyOS helps practices capture, respond, and convert demand that would otherwise go to a competitor.
What is revenue leakage? →Founding practices
See it on your own enquiries
Bring last week’s messages to the demo. We’ll walk through what ReplyOS would have replied, and where it would have handed off to your team.
- One of five founding places, with onboarding run by the founder
- Founding price locked as the platform expands
- Reduced set-up fee
- First month free once your system is live
- No commitment during setup; billing starts at go-live
- Priority support during rollout
Who you’d be working with

Paul Redman, founder. Reply Intelligence Group Ltd, Watford. Company no. 17040048.
I built ReplyOS after watching practices spend real money getting patients to enquire, then lose a good share of those enquiries to a slow or missing first reply. Nobody at the desk was doing anything wrong; the message just arrived at the wrong time on the wrong channel.
I run onboarding for every founding practice myself. In return I ask for honest feedback and, if it works, a sentence I can quote.