A Saturday on an optician's website produces a familiar list of questions. Can I get an eye test this week? Do you stock a particular designer brand? How much are varifocals? Do you do contact lens trials? Is my eye test free if I am over 60? And then, among them, something different: my left eye has gone blurry since this morning and I keep seeing flashes, should I be worried?
The first five are retail and scheduling. The last one is clinical, possibly urgent, and must not be treated like the others.
That split is the whole design problem. An AI receptionist for opticians can take a real load off the front desk, but only if it is built from the start to recognise the difference and hand clinical concerns to people who are qualified to judge them.
Sorting optician enquiries before anything else
It helps to lay out, question by question, what the assistant is and is not allowed to do. Here is a starting matrix. Adjust it with your own team.
| Visitor asks about | Assistant answers from content? | Then |
|---|---|---|
| Opening hours, parking, accessibility | Yes | Nothing further needed |
| Eye test prices and eligibility for free tests | Yes, as published | Offers to capture an appointment request |
| Frame brands, price ranges, offers | Yes | Suggests visiting for a fitting |
| Lens types: single vision, varifocal, blue light filters | Yes, in general terms | Notes that the optometrist recommends what suits them |
| Contact lens trials and aftercare appointments | Yes | Captures a request |
| Repairs, adjustments, collecting glasses | Yes | Captures details if staff need to check an order |
| Whether their prescription has changed | No | Suggests an eye test |
| Any symptom: pain, redness, sudden blur, flashes, floaters, loss of vision | No | Fixed urgent response, see below |
| Children's eyesight concerns | Only process and eligibility | Symptoms go to staff |
Notice how much sits in the "yes" rows. Most optician enquiries are the retail and scheduling kind, and those are exactly the questions that clog phones on busy mornings.
The symptom rule
The most important configuration is also the simplest. Any message that describes a symptom gets the same kind of response: no opinion, no reassurance, no guess at the cause, and a clear instruction on what to do.
Your optometrists should write this, not whoever set up the website. They know which symptoms your practice treats as same-day and which need hospital eye services or emergency care, and they know how that guidance is phrased locally. Here is a process for putting it in place:
- Ask your lead optometrist to write the list of symptoms that should never wait, in plain words a patient would type.
- Have them write the exact response for those cases, including your phone number and what to do out of hours.
- Write a second, gentler response for non-urgent symptoms, such as tired eyes or mild dryness, that still avoids advice and suggests an appointment.
- Put both into the assistant's instructions and a Q&A pair, stating that it gives information, not clinical advice.
- Test with at least ten symptom messages, including vague ones like "my eye feels weird" and ones mixed into a retail question.
- Review every conversation mentioning a symptom for the first month.
Step five matters because real patients do not write neatly. "Do you sell sunglasses, also I've had a shadow in my vision since yesterday" must trigger the symptom response, not a list of sunglasses.
A tested version might read like this:
Visitor: Do you do eye tests on Sundays? My right eye has been painful and red since last night. Assistant: A painful red eye should be checked promptly, and I can't advise on symptoms here. Please call the practice now on the number at the top of this page. If we are closed, the guidance on our urgent eye care page explains where to go, and if your sight has suddenly changed or the pain is severe, seek urgent medical help. We are not open on Sundays for routine tests, but I can take a request for a routine appointment separately if you would like.
More on building boundaries like this is in guardrails for regulated industries and questions your assistant should refuse.
Frames and lenses: where the assistant shines
Retail questions are where a website assistant earns its place. A visitor comparing practices at 9pm wants to know whether you carry a brand, what a pair of varifocals costs roughly, and whether there is an offer on second pairs.
Give it your frame ranges, lens price lists and current offers as documents or Q&A pairs. Explain lens options in the plain terms your dispensing staff use. Keep offers in one place that someone updates, because an assistant quoting last season's two-for-one is worse than one that says nothing.
It should always leave the final recommendation to your team. "Our dispensing opticians will help you choose the right lens after your eye test" is honest and it brings people through the door.
Eye test requests that staff can confirm
For eye test booking questions, the assistant captures the request rather than confirming a slot. Useful fields: routine test or contact lens check, new or existing patient, preferred days and times, whether they think they qualify for a free test, and contact details. Staff then confirm in the practice system.
Tell visitors plainly that someone will confirm the time. Nobody should leave the conversation believing they have an appointment they do not have. There is a sector overview on the opticians page, and the actions and settings are listed on features.
Keeping it current
Optical practices change more content than people expect. Offers rotate, frame ranges are refreshed, clinic days move when an optometrist goes part time. Give one person the job of updating the assistant whenever any of these change, and check the unanswered questions list every fortnight. It will show you which retail questions visitors ask that your website never answered in the first place.
Where to begin
Book thirty minutes with your lead optometrist this week, with one agenda item: the symptom list and the two responses. Everything else, from frame ranges to parking, can be gathered by front desk staff over a few days.
Do the clinical part first, test it until it never fails, and only then add the retail content. That order keeps the one conversation that really matters safe from day one.