Verdict: An AI receptionist is usually a service layer on top of clinic telephony, not a synonym for PBX, PSTN, VoIP or IVR. Most UK clinics should keep a sound phone system and add AI for conversational answering, overflow and booking actions. A full telephony replacement is a separate decision—often driven by analogue-line risk, routing limits or the UK move away from the Public Switched Telephone Network (PSTN).
This comparison is for buyers evaluating “AI phone system vs traditional clinic phone system” without mixing up the layers. For the landline retirement itself, see the PSTN switch-off guide. For conversational delay and provider-lock-in questions, see the latency and phone-migration article.
Clarify the categories first
These terms are related but not interchangeable:
| Term | What it is | What it is not |
|---|---|---|
| PSTN | The legacy analogue public telephone network carrying traditional landlines | A modern clinic phone product or an AI agent |
| PBX | The clinic’s private call-switching system (on-premise or hosted) that rings extensions and applies basic rules | A booking brain or natural-language agent |
| VoIP | Voice delivered over IP/internet-based telephony | Automatically an AI receptionist |
| IVR | Interactive voice response: menus, keypad options or fixed prompt trees | Conversational understanding or diary write-back by itself |
| AI receptionist | Software that interprets spoken intent and can complete configured administrative actions | A complete substitute for every telephony, compliance and safety control |
Practical model: telephony delivers the call; the AI layer decides how to converse and act; practice management software (PMS) holds the diary of record when booking is connected.
Clero fits the AI-receptionist layer. Depending on the clinic, calls may be routed from an existing business VoIP platform, forwarded from the published number, or moved onto a VoIP setup—including partner telephony—when a migration is required. That is integration and routing, not proof that every deployment replaces the phone system end to end.
Answer-first comparison
| Factor | Traditional clinic telephony (PBX / VoIP / IVR) | AI receptionist layer |
|---|---|---|
| Purpose | Deliver, ring, queue and route calls to people or menus | Interpret intent and complete approved admin workflows |
| Caller experience | Rings, hold music, extensions, button menus | Conversational handling for supported request types |
| Natural language | Limited unless a separate AI layer is added | Core capability, with accuracy depending on audio quality and workflow design |
| Concurrency | Limited by trunks, licences and staff answering | Can handle multiple supported conversations subject to platform and telephony limits |
| Routing | Time-of-day, hunt groups, overflow to voicemail or another extension | Can sit in overflow, out-of-hours or selected queues, then escalate to humans |
| Booking actions | Usually none beyond connecting a person | Can check availability and book when a supported PMS is connected |
| Reporting | Call logs, queues, missed-call reports | Intent, outcomes, escalations and booking results, depending on configuration |
| Resilience | Depends on lines, internet, PBX and cover rota | Adds overflow capacity but still needs telephony and human fallbacks |
| Implementation | Provider install, number routing, handsets or softphones | Workflow discovery, routing design, PMS mapping and testing |
| Human fallback | The default destination for most clinics today | Required for complaints, clinical language, exceptions and failed bookings |
| Cost model | Lines, licences, handsets, support | Platform or usage fees plus telephony, implementation and oversight |
Traditional systems remain necessary plumbing. AI changes what happens after the call is answered.
When to keep your phones and add AI
Retain existing telephony and add an AI layer when:
- the clinic already has stable business VoIP
- the published number can be routed or forwarded into AI for overflow, out-of-hours or selected queues
- desk phones still need to ring for transfers and walk-in coordination
- the main gap is unanswered routine calls, not a failing line platform
In that model, patients keep dialling the same number. The architecture question is routing design, not a forced provider swap.
When a VoIP migration may be needed
Consider migrating telephony when:
- the clinic is still on analogue / PSTN-reliant lines approaching industry retirement
- current hardware cannot support reliable overflow, recording controls or multi-site routing
- the clinic wants a single cloud telephony layer before adding automation
- payment terminals, alarms or other devices on the old line also need a planned digital path
The UK telecommunications industry is retiring the PSTN, with landline and other PSTN-reliant services expected to complete the move to digital technologies such as VoIP by January 2027, according to GOV.UK guidance on moving landlines to digital technologies. Clinics should confirm their exact date and options with their communications provider; do not rely on outdated “2025” or other stale deadlines.
A VoIP migration and an AI receptionist project can run together, but they solve different problems. Migration replaces the transport layer. AI changes call handling and booking outcomes.
Decision tree: current setup → suitable approach
- What delivers your calls today?
- Analogue / PSTN landline or ageing ISDN → plan a digital/VoIP migration, then decide where AI sits in the call flow.
- Business VoIP or hosted PBX → usually keep telephony and evaluate AI as a routed service layer.
- What fails today?
- Missed overflow, out-of-hours voicemail, no booking on the call → prioritize an AI receptionist on top of sound telephony.
- Unreliable lines, poor multi-site routing, unsupported hardware → prioritize telephony redesign, with or without AI in phase one.
- Can you route selected calls without changing the public number?
- Yes → design overflow / out-of-hours / queue injection into AI.
- No → ask whether forwarding, internal VoIP rules or number porting during migration is required.
- Do you need live diary write-back?
- Yes → confirm PMS connectivity before promising booking automation.
- No → AI may still answer FAQs and take structured messages, but that is not full booking automation.
- What is the outage plan?
- If unanswered, document desk divert, alternative site, monitored messaging or provider fallback before go-live.
Architecture questions that decide the design
Ask vendors and your telecom provider:
- Will AI answer all calls, overflow only, out-of-hours only, or selected queues?
- Do we keep, forward or port the published number—and who owns that process?
- How do warm transfers reach desk handsets or mobiles if nobody answers?
- Which practice systems can be read and written during the call?
- What happens if internet, VoIP, AI or the PMS path fails?
- If calls are recorded or transcribed, what is the lawful basis, notice to callers, retention period and access control?
Number porting and forwarding
Patients usually keep the same practice number. Clinics either:
- forward or re-route the number into AI / VoIP rules, or
- port the number as part of a telephony migration so the public identity stays stable
Do not assume every AI deployment requires porting, and do not assume every clinic can avoid all telephony change—especially on analogue lines.
Out-of-hours routing
Out-of-hours behaviour is a routing rule, not an automatic property of “having AI.” Define which requests may book, which become messages, and which follow urgent-language scripts after closing time.
Call recording and caller notice
If audio, transcripts or call metadata are retained, treat them as personal data. Clinics need a lawful basis under UK GDPR and should make callers aware that recording or monitoring may occur. Consent is one possible basis, not the only one; purpose, transparency and retention still matter. Review current ICO guidance for organisations and your privacy notice before enabling recording. Deeper retention and security questions are covered in the healthcare call automation security guide.
PMS connectivity
Telephony can exist without booking. Booking automation needs a connected, supported practice system and clear appointment rules. Message-taking alone is not the same as live diary write-back.
Outage fallback
AI does not remove the need for a human or alternative route when systems fail. Build fallback into the telephony plan, then rehearse it. Implementation sequencing is covered in the AI receptionist implementation guide.
Claims to treat carefully
- “No migration required” — sometimes true for clinics already on suitable VoIP with flexible routing; not true for every analogue or locked-down setup.
- “Zero delay” / “perfect understanding” — conversational quality varies with network path, audio conditions and workflow design. Ask for measured behaviour under realistic clinic conditions rather than absolute promises.
- “AI phone system replaces traditional phones” — often marketing shorthand. In practice, clinics still need a telephony layer to deliver and recover calls.
Where Clero is deployed, it is designed to answer inbound practice calls, handle routine administrative requests, book into supported systems when connected, and escalate complex calls. Exact routing—existing VoIP, forwarding or porting onto a VoIP platform—depends on the clinic’s starting point.
Frequently asked questions
Is an AI receptionist a replacement for a clinic phone system?
Not necessarily. An AI receptionist is usually a service layer that answers and acts on calls after they are delivered by PSTN, PBX or VoIP. Many clinics keep their telephony and route selected calls into AI.
Do clinics need to change phone provider to add AI?
Often no, if they already have workable business VoIP and can route or forward calls. Clinics still on analogue lines, or needing a fuller cloud telephony rebuild, may need a VoIP migration—especially ahead of the UK PSTN switch-off.
What is the difference between IVR and an AI receptionist?
IVR routes callers through button menus or fixed prompts. An AI receptionist uses conversational language to interpret intent and can complete administrative actions such as booking, subject to clinic rules and connected systems.
Will patients keep the same practice phone number?
Usually yes. Clinics commonly keep the published number and either forward it, re-route it inside their VoIP platform or port it during a telephony migration so patients continue dialling the same number.
When should a clinic migrate to VoIP instead of only adding AI?
Migrate when the current line is analogue or otherwise ending with the PSTN retirement, when routing and recording controls are too limited, or when the clinic wants unified multi-site telephony before layering automation.
What happens if telephony or the AI path fails?
A resilient design needs a documented fallback: divert to the desk, another site, monitored messaging or an alternative route. Do not rely on AI alone as the only continuity plan.
Next step
If you know whether your lines are analogue or VoIP, how overflow works today and whether you need live booking, you can map the architecture before choosing products. Bring a call-flow diagram or provider bill details if you want a concrete keep-versus-migrate recommendation.