AI receptionist, CRM chatbot, or a website's built-in patient assistant — what's actually different?
An AI receptionist usually answers calls and messages on your behalf, as a separate subscription service. A CRM chatbot lives inside your practice-management or lead-management software, built mainly to capture enquiries into that system's own follow-up sequences. A website's built-in patient assistant is part of the site itself, trained only on your practice's own facts. All three do a genuinely different job.
Search for “AI receptionist for dental practice” today and the results are a mix of three quite different products, none of which explain how they relate to each other. One is a call-answering service. One is a feature bolted onto practice-management software you may already pay for. One is part of the website itself. They get talked about as if they’re interchangeable. They’re not, and mixing them up is an easy way to think you’ve solved a problem you haven’t.
Three tools, one confusing search
The confusion is real, not a marketing trick. A practice owner searching for help with missed enquiries will land on AI-receptionist services built for phone and message handling, on practice-management platforms that have quietly added a chat widget as a feature, and on agencies (like this one) building an assistant straight into the website. Same search term, three different products, three different jobs. Working out which gap you’re actually trying to close matters more than which one has the flashiest name.
What each one is actually built to do
- An AI receptionist. Typically a subscription service that answers your calls, WhatsApp or social messages, following a script and booking into your calendar. Useful for catching the phone that goes unanswered — but it usually sits outside your website, with its own tone and its own rules.
- A CRM chatbot. A chat feature built into your practice-management or lead-management software. Designed to capture a name, a number and an interest, then push it into that system’s own follow-up sequences. It’s a lead-capture tool wearing a chat window — not necessarily built to answer questions using your website’s own content.
- A website’s built-in patient assistant. Part of the site itself — same design, same tone, one system rather than two or three. Done properly, it’s trained only on your practice’s own confirmed facts and tested against real and awkward questions before it ever speaks to a visitor.
Where they live, and what they're trained on
The clearest way to compare them isn’t the name on the box — it’s where each one lives and what it actually knows:
| AI receptionist | CRM chatbot | Built-in patient assistant | |
|---|---|---|---|
| Where it lives | A separate call/message service | Inside your CRM or practice software | Part of the website itself |
| What it's built for | Catching missed calls and messages | Capturing leads into that system's pipeline | Answering visitors using your own facts |
| What it's trained on | General call-handling scripts | The CRM's own forms and playbook | Only your practice's verified facts |
| A clinical or urgent question | Depends on the supplier | Rarely designed to handle this | Built to hand these to a person |
The “we already have a chatbot” trap
This is the mix-up worth slowing down for. A growing number of practice-management and CRM platforms now bundle a chatbot as a feature, and it’s tempting to assume that box is ticked once you’ve switched it on. But that chatbot was built to serve the CRM, not your website. Its job is to capture a name, a number and an interest, then hand the lead into that system’s own email or SMS sequence — which is a genuinely useful thing for it to do. What it usually can’t do is answer “do you treat nervous patients” or “what are your Saturday hours” using the actual words published on your own site, because it was never trained on your site’s content in the first place.
The question that actually matters isn’t what a tool calls itself. It’s whether its answers come from your practice, or from someone else's playbook.
Does an AI receptionist close the same gap?
Not quite, for a related reason. An AI receptionist is usually built to work across many kinds of business, following a general call-handling script rather than your specific facts — and because it typically lives outside the website entirely, a visitor reading your site and a caller on the phone can get two different answers to the same question. That's a separate risk to the CRM-chatbot trap, but the same root cause: the tool wasn't built with your website, so it doesn't necessarily share its facts. We've gone through this in more depth, including the safety differences, in our guide to AI chatbots, AI receptionists and patient assistants.
Four questions to ask before you buy any of them
Whichever product is in front of you, and whatever it's called, these four questions cut through the branding:
- Where do its answers actually come from — your practice's own facts, or a general script or playbook?
- Where does it live — on your website, inside your CRM, or as a separate call service?
- What does it do the moment it doesn't know something? Says so and hands over, or guesses?
- What happens with a clinical or urgent question? A supplier that answers this clearly, specifically and without hedging has probably built something safe.
None of this means a CRM chatbot or an AI receptionist is a bad tool — both can genuinely earn their keep at what they're built for. It just means neither one is automatically the same thing as a website assistant, and treating them as interchangeable is how a practice ends up with three different answers to the same question, or a gap nothing actually covers. Our guide to what an AI patient assistant should never do is worth reading alongside this one, whichever category you're comparing.
Where Tireless fits
We build the patient assistant into the website itself, not as a bolt-on to a CRM or a separate call service. It's trained only on facts your practice has confirmed, tested against real and awkward questions before it goes live, and built to hand anything clinical or urgent straight to a person. It starts from £1,200 to set up plus from £150 a month — full detail on our pricing page — and is usually built and tested alongside a new site, both live in 7–10 days. If you're weighing the numbers too, our guide to what a dental AI assistant actually costs goes through them in full.
See a built-in assistant, not a bolt-on, in action
Try our live demo and ask it something routine, something awkward, and something urgent. Notice what it does when it isn’t sure — that's the part that actually matters.
See the demo →Frequently asked questions
What's the difference between an AI receptionist, a CRM chatbot, and a website's built-in patient assistant?
An AI receptionist is usually a separate service that answers calls or messages on your behalf. A CRM chatbot lives inside your practice-management or lead-management software, built mainly to capture enquiries into that system's own follow-up sequences. A website's built-in patient assistant is part of the site itself, trained only on your practice's own verified facts.
If my CRM already has a chatbot, do I still need a website assistant?
Often yes. A CRM chatbot is usually built to capture a lead into that system's pipeline, not to answer a visitor's specific question using your website's own content. It can be a genuinely useful tool for follow-up — it's just solving a different problem to an assistant built into your site.
Does an AI receptionist replace a website's built-in assistant?
Not necessarily. An AI receptionist usually handles calls and messages as a standalone service, which can sit apart from your website entirely and may not be trained on the specific facts published on your site. A built-in assistant answers the same visitor, on the same page, using the same facts.
Which one should a dental or aesthetic practice choose first?
There's no universal answer — it depends on where you're actually losing enquiries. If it's unanswered calls, an AI receptionist addresses that directly. If visitors leave your website without an answer, a built-in patient assistant addresses that. Many practices eventually use more than one, for different jobs.