If you ask most UK independent optician practice owners what their practice management software actually does for them all day, the honest answer is: it talks to patients. Confirmations, reminders, “your glasses are ready”, recall texts, a birthday voucher, a follow-up email after a contact lens fit. Patient communication is the module your PMS runs through more times in a week than EMR, stock or reporting combined.
And yet, when practices compare optician software, the comms module is almost always the least scrutinised. Demos focus on the diary, the records, the eGOS workflow. The comms tab gets a 30-second whip-through: “yes, we send SMS reminders, here’s the template editor.” Three months in, the practice realises the reminders go out at the wrong time, the replies disappear into a black hole, and the recall sequence stops at one text instead of three.
This guide is for UK independent optician practice owners and managers who want to compare patient communication and messaging modules properly before they sign a PMS contract. It covers the four jobs your comms module has to do, the dimensions you should actually compare vendors on, ten demo questions, the red flags, and what good looks like in 2026.
Why patient communication is the most under-compared PMS module
Three reasons it gets skipped in demos.
First, it looks the same on the surface across every vendor. Every modern UK optician PMS will tell you it sends SMS appointment reminders. So practices tick the box and move on. The differences only show up once you’re using it daily — and at that point you’re locked in.
Second, the people choosing the PMS often aren’t the people who’ll be sending and answering the messages. Owners pick the software; receptionists, dispensing opticians and recall coordinators live inside the comms inbox. If the buyer doesn’t put the comms module in front of front-of-house staff during the demo, the awkward bits never surface.
Third, comms is where automation actually saves you hours per week. A weak module costs you in a hundred small ways — slightly more no-shows, slightly slower glasses collection, slightly fewer recalls coming back, slightly more time on the phone — and none of those losses ever shows up as a line item you can complain about. You just feel busy.
Patient communication is a quiet leverage point. The right module gives you a measurable lift in attendance, dispense rates, recall return and Google reviews. The wrong one slowly bleeds you.
What “patient communication” actually means in a 2026 PMS
It’s worth pinning down the scope, because vendors use the word loosely.
A modern UK optician PMS comms module should cover, at minimum:
- Outbound SMS and email — confirmations, reminders, “ready for collection”, recalls, follow-ups, marketing-permitted sends.
- Inbound replies — patients can reply to a text, and the reply lands somewhere a human can act on it.
- Automation rules — messages triggered by events in the diary, the dispense workflow, the recall list, the CL register.
- Templates and personalisation — practice-branded copy, patient name, appointment time, branch, optometrist, link to confirm or reschedule.
- An audit trail — what was sent, when, to whom, and what was received.
- Compliance — consent capture, opt-outs, GDPR/PECR alignment.
If a vendor only ticks one of these (outbound SMS) and calls itself a “patient communication platform”, you’re looking at a glorified text gateway. That’s a starting point, not a finished product.
The four jobs your comms module has to do
Forget the feature list for a minute. The module has four jobs.
Job one: get the patient through the door for the right appointment
Confirmations that go out within seconds of booking. Conditional reminder cadences — a different sequence for an eye test booked six weeks out versus one booked tomorrow. A 48-hour confirmation request with a YES/NO reply that updates the diary automatically. A morning-of nudge for early slots so people who set their alarm wrong don’t simply not turn up.
If your module can’t do conditional cadences — if every patient gets the same single text 24 hours before — you’re carrying a higher DNA rate than you need to. We covered the full no-shows playbook in a recent piece on reducing patient no-shows, but the headline is: the comms module is where most of the DNA leak lives.
Job two: shorten the dispense cycle
The “your glasses are ready” message is one of the highest-value automated sends in the practice. It needs to fire within minutes of the dispense being marked ready, not at 5pm in a daily batch. It needs to include the practice’s collection hours and a one-tap call-back option for patients who want to ring to confirm a collection time. And it needs to escalate — a second text three days later, then a personal call workflow surfaced to the front desk if a high-value pair is still uncollected at day seven.
This is the single comms behaviour we hear most often from independents who’ve switched PMS: the new system actually tells patients their glasses are ready on the same day, and uncollected glasses drop by half within a quarter.
Job three: bring the patient back when they should come back
Recall is patient communication’s other gravitational mass. Twelve-month recall for routine, six-month for diabetic, three-month for certain glaucoma watch-list patients, four-week for new contact lens wearers, twelve-week for orthokeratology fits. A good comms module lets you set differentiated recall cadences per clinical category, not one generic “your eye test is due” text for everybody.
It also needs to handle stepped recall — a first SMS, then an email a fortnight later, then a phone-list export at the four-week mark if the patient still hasn’t booked. Single-touch recall converts a fraction of what a three-touch sequence does.
Job four: be a record, not a ghost
Every message sent and received has to be attached to the patient record, time-stamped, viewable in the EMR, and exportable for GDPR access requests or clinical record audits. If a patient says “I didn’t get a reminder”, you should be able to pull the delivery log in 20 seconds. If a clinician says “did we follow up after the abnormal pressure?”, the answer should be visible inside the record, not in a separate marketing inbox no clinician ever opens.
A comms module that doesn’t write back to the patient record is doing half a job.
The six dimensions to compare PMS comms modules on
Once you accept the four jobs above, comparing vendors gets sharper. There are six dimensions where modules genuinely differ.
One: channel coverage
SMS is table stakes. Email is table stakes. After that, the real questions are: does the module support two-way SMS (replies that land back in your system, not on some random mobile phone)? Does it support WhatsApp Business — a growing patient preference, especially for under-40s and family members managing parents’ appointments? Does it support voice broadcasts for storm-day cancellations or surgery closures? Does it integrate with the practice phone line so missed calls surface as a follow-up task?
You don’t need every channel on day one. You do need a vendor whose roadmap matches where patient behaviour is going, not where it was in 2018.
Two: automation depth
This is where most modules quietly fall over. Ask a vendor to show you, live, how they’d build a contact lens aftercare sequence for a new wearer: SMS day 1 (“how are the lenses settling?”), email day 7 (“solution reminders and care tips”), SMS day 14 (“ready to book your fit check?”), task on the receptionist’s dashboard day 21 if the fit check hasn’t been booked.
If the demo turns into “you can set up SMS reminders 24 hours before”, you’ve got a single-trigger system, not an automation engine. Independents trying to build a real CL business need real sequences — we walked through the full pattern in our guide to contact lens services for UK independents, and the comms module is the spine.
Three: two-way replies and inbox workflow
The single biggest difference between a good and a bad comms module is how it handles replies.
Bad: the patient replies to the reminder text, the reply hits a mobile number no-one watches, or worse, hits an “unmonitored inbox” and is bounced. The patient gets a system message back saying “do not reply to this number.” You’ve just told a paying patient they’re talking to a machine.
Good: every reply lands in a unified inbox visible to reception, threaded by patient, with the patient record one click away, with reply matching that updates the diary when a patient texts “yes” or “no”. Reception can reply from the same inbox. Replies that look like clinical questions (symptoms, problems with vision) flag for an optometrist’s attention rather than a busy front desk.
Ask to see the inbox during the demo. Insist on it.
Four: templates, personalisation and brand
Patients are getting hundreds of automated messages a week. Yours has to feel like it came from a practice that remembers them, not from a payroll system.
Compare: how many variables can you drop into a template (name, time, branch, optometrist, dispenser, last test date, frame brand collected)? Can you set per-branch templates for multi-site practices? Can you write a different tone for a CL fit reminder versus a children’s appointment? Are templates version-controlled so a typo doesn’t go out 400 times before anyone notices?
Some modules let you bulk-update a template and roll the change forward to every active automation. Others make you edit every sequence manually. Multiply that by 30 templates and 8 sequences and you can see the difference.
Five: deliverability and reliability
If 4% of your texts fail silently because of dropped UK telco routing, you’re losing roughly one in every 25 reminders — and not knowing which ones. Ask the vendor for their average UK SMS delivery rate over the last 90 days, and how delivery failures are surfaced inside the PMS (a red flag on the patient record, a daily failures report, both). Ask whether they use a single SMS gateway or have failover routing. Ask what their email deliverability looks like on common UK consumer domains.
This isn’t a question vendors expect, which is exactly why it’s worth asking. The answers separate the comms-as-feature crowd from the comms-as-product crowd.
Six: compliance and consent
PECR is the law of the land on marketing-permitted patient communication. GDPR governs how you store the underlying data. An optician PMS comms module should make compliance easy: opt-in capture at booking, separate consent flags for service messages (reminders, recall) and marketing messages (offers, events), one-click opt-out from any send, an automatic suppression list that the practice can’t accidentally bypass.
If a vendor can’t show you the consent fields on the patient record and tell you precisely which message types respect which flag, treat that as a serious risk, not a paperwork detail.
Ten demo questions to score every vendor on
Print this list. Use it on every demo. Score each vendor 0-2 on each question.
- Show me, live, building a four-touch recall sequence for a glaucoma watch-list patient, including a final task that lands on a reception dashboard if no booking is made.
- Send a test SMS from the demo system to my phone — including a YES/NO confirmation reply — and show me where the reply lands and how it updates the diary.
- Show me the inbox a receptionist sees on a Monday morning. How many clicks to read a thread, view the patient record, and reply?
- How does a “your glasses are ready” message get triggered? On which event? With what delay? Can I escalate to a second message and a call task?
- Show me a per-branch template with three personalisation variables, and roll a change forward to every active sequence using it.
- Pull a report showing SMS delivery rate, email open rate, and reply rate for the last 30 days. What’s the breakdown of delivery failures by reason?
- A patient asks via SMS reply “is my appointment still on?” — walk me through how reception sees that, responds, and updates the diary in under a minute.
- Show me the consent fields on a patient record. Which message types respect which consent flag? How does an opt-out propagate?
- Pull the comms history for a single patient over the last 12 months — every send, every reply, every delivery status — and tell me how I’d export it for a GDPR access request.
- Show me what happens if my SMS gateway goes down for an hour. Do messages queue and retry, or fail silently?
A vendor scoring 18+ is genuinely competitive. 12-17 is workable with caveats. Under 12, the module is a marketing line, not a working system.
Five red flags to walk away from
One: “we send through your own mobile phone.” Sometimes dressed up as “personal touch”, this is just a hobbyist setup. No delivery reporting, no thread history, no failover, and a compliance nightmare the day a member of staff leaves with the SIM.
Two: the comms module is a third-party bolt-on you pay separately for and that doesn’t write back to the patient record. The patient record becomes incomplete the moment you turn it on.
Three: “unmonitored inbox” auto-replies on inbound texts. Tells you the vendor never built a real two-way workflow.
Four: per-message pricing on SMS with no monthly cap. You’re now optimising sends to control cost instead of patient experience, which is the wrong way round.
Five: no per-branch template control for multi-site practices. Either you accept a single template for every location or you fork the database, and both options are a long-term mess.
What good looks like in 2026
A 2026-standard comms module in the UK independent market looks like this: SMS and email outbound with two-way replies threaded by patient, WhatsApp on the roadmap if not live, multi-step sequences with conditional logic, a unified inbox for reception, per-branch templates with variable personalisation, trigger events tied to real PMS state changes (booking, dispense ready, recall due, CL aftercare, abnormal clinical flag), delivery and reply reporting in the same dashboard as appointments, proper consent capture and opt-out suppression, and every message written back as a permanent record on the patient file.
Anything below that bar in 2026 is technical debt you’ll inherit on day one.
Where Raven Vision sits on patient communication
Raven Vision was built inside Shaukat’s three practices before we opened it up to the industry. The comms module reflects that. Confirmations and reminders trigger on diary events, not overnight batches. Replies land in a unified inbox the receptionist actually uses. Dispense-ready messages go out when the dispense is marked ready, not when someone remembers to run a list. Recall cadences are configurable per clinical category. Templates are per-branch, version-controlled, and pull from the live patient record.
The point isn’t that we’ve reinvented patient communication. It’s that we built it inside a practice where the cost of a bad comms module — uncollected glasses, repeat phone calls, missed recalls — was a cost we paid personally. That’s a different design constraint than a feature spec written in a meeting. You can see how the rest of the system fits together on our features page, and we covered the broader comparison framework in our guide to switching practice management software.
A short pre-signing checklist
Before you sign any PMS contract — Raven Vision included — do four things on the comms module. Run the ten demo questions above and score every vendor honestly. Get a test account for 48 hours and send 20 messages to your own phone, reading every one as a patient would. Put a receptionist in front of the inbox for 30 minutes and watch their face — if it tightens, the workflow is wrong. And ask for written delivery rate numbers plus a sample monthly comms report. If the vendor won’t share, that’s the answer.
Patient communication is the part of your PMS that runs every single day, on every appointment, with every patient. It’s not a feature — it’s the operating layer of your practice. Compare it accordingly.
If you want to see how the Raven Vision comms module handles your specific recall, dispense and CL workflows on a real demo, book a demo and we’ll walk through it with your sequences, not ours. No slide-deck demo, no generic flow — your practice’s actual patient journey.
