New in ReplyOS · Pro and Scale
An AI assistant front desk for your practice
An AI assistant front desk publishes a practice's services, guide prices, opening hours and booking link for AI assistants to read and quote, and lets assistants connected to it pass on a patient's enquiry when the patient asks them to. In ReplyOS the enquiry lands in the practice inbox for the team to answer; nothing is sent to the patient automatically.
Why this matters now
Patients are starting to ask AI assistants such as ChatGPT or Gemini to find a dentist, compare prices and get them in. An assistant can only recommend a practice accurately using what it can read. Most practice websites give it nothing structured, so it guesses, or points the patient somewhere else.
What ReplyOS publishes for assistants to read
- Your services, with the guide or "from" prices you have set
- Opening hours, phone number and WhatsApp
- Your online booking link, where you have one
- A connection (an MCP server) that assistants linked to ReplyOS can use to pass on an enquiry for a patient
It comes from what you already keep in ReplyOS, so it stays current as you change services, prices or hours.
What works today, and what depends on the assistant
- Works today, with any assistant that reads the web. When ChatGPT, Gemini, Perplexity or Claude look your practice up, they can read your real services, guide prices, hours and booking link instead of guessing.
- Works today: you see what AI sent you. When a patient clicks through from an assistant and messages you on web chat, the enquiry is marked with where they came from, such as Via ChatGPT, and the Revenue page shows how many booked and what they were worth.
- Depends on the assistant: sending an enquiry for the patient. An assistant can only pass on an enquiry once it is connected to ReplyOS. Mainstream assistants do not yet connect to a practice on their own; a user has to add the connection, or the assistant has to list it in its app directory. Until that changes, most patients who find you through an assistant will reach you through your website, web chat or phone, and ReplyOS still shows you they came from AI.
When a connected assistant passes on an enquiry
The assistant sends the patient's name, contact details and what they need. It arrives in your inbox marked AI assistant, alongside your web chat, SMS, email and social messages, and your team picks it up from there. The assistant is told straight away that the practice will be in touch, and to send anyone in severe pain to your phone line or NHS 111.
What it never does
- Reply to the patient automatically. Your team answers every enquiry.
- Accept medical history. Only name, contact details and a short message.
- Act without the patient asking. The assistant must confirm the patient asked it to get in touch.
- Publish anything you have not already chosen to show patients in your web chat.
How it fits ReplyOS
ReplyOS works on pre-booking leakage: the value lost between a patient's first enquiry and a booked appointment. AI assistants are a new way that first enquiry arrives. Because they come in as their own channel, you can see how many patients reached you this way and what happened next, instead of losing them to a practice that was easier for the assistant to read. Payments, clinical records and your diary stay in your own systems.
Which AI assistants can use it?
Any AI assistant that reads the web can read the profile, which ReplyOS publishes in the standard schema.org format and as plain text. Sending an enquiry for a patient is different: the assistant has to be connected to ReplyOS's MCP server, and mainstream assistants such as ChatGPT, Gemini and Claude do not connect to a practice on their own yet. A user can add the connection, or an assistant can list it in its app directory. Whether a particular assistant uses any of it is that assistant's decision; ReplyOS has no partnership with any AI company.
Can I see which patients came from an AI assistant?
Yes, and this works today without any connection. When a patient clicks through from ChatGPT, Perplexity, Gemini, Copilot or Claude and messages you on web chat, the enquiry is marked with where they came from, and the Revenue page shows enquiries from AI, how many booked and the booked value.
Does ReplyOS reply to the patient automatically?
No. An enquiry from an AI assistant lands in your inbox marked AI assistant, and your team contacts the patient: by SMS or WhatsApp from the enquiry, or by phone. Nothing is sent to the details an assistant supplies until a person at the practice decides to reply.
What information can an AI assistant send?
Only the patient's name, a phone number or email address, a short message about what they need, and a preferred contact time. The assistant must confirm the patient asked it to contact the practice. Medical history is not accepted, and the assistant is told not to send it.
What happens with urgent cases?
Every response tells the assistant to direct anyone with severe pain, swelling, bleeding or trauma to phone the practice or NHS 111, rather than wait for a reply.
Is it UK GDPR compliant?
The practice stays the data controller and ReplyOS the processor, as with web chat, under the same data processing agreement. The practice chooses to switch it on. Data is minimal, contact is at the patient's own request, and there is no marketing or automatic messaging. Practices should mention enquiries made through AI assistants in their patient privacy notice.
Security and trust →Which plans include it, and how is it switched on?
The AI assistant front desk is included on Pro and Scale. A practice switches it on in the ReplyOS console, on the Webchat page, under AI assistants. It needs the practice web chat widget to be live. The page then gives a link tag to add to the practice website and a line for its llms.txt, so assistants can find the profile.
Explore the platform or view pricing.