AI in an Optometry Practice: A Week-by-Week First-Month Plan

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI in an Optometry Practice: A Week-by-Week First-Month Plan.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI in an Optometry Practice: A Week-by-Week First-Month Plan.

Start an optometry practice's AI use with the front desk, not the consulting room. Week one covers phone calls, week two recall messages, week three exam-note drafting, and week four marketing and a review of the numbers. Retinal-image diagnosis stays out of the plan, because an error there is clinical, not clerical.

The order matters because the risk rises with each week. A missed call or a clumsy reminder costs a booking. A wrong sentence in a clinical note costs trust, and a wrong finding costs far more. So the plan starts where mistakes are cheap and visible, builds the habit of checking AI output, and only then touches anything clinical, always with the optometrist as the author of record.

Follow me on Instagram@sagnikteaches

What a month can realistically change

A month is enough to get four jobs running, not to transform the practice. It is also enough to find out which of the four is worth keeping. Most practices that try everything at once end up with none of it properly set up, so the plan below gives each week one job, one owner, one measure and one stop rule.

Connect on LinkedInSagnik Bhattacharya

Before week one, do three small things. Pick one person to own the project; in a two-optometrist practice that is usually the practice manager or the owner. Write down the baseline for five numbers over the previous four weeks: calls received, calls missed or sent to voicemail, no-shows, recalls sent against recalls booked, and minutes spent on notes per exam. Rough figures from the booking system and a tally sheet are fine. Without a baseline, in week four you will only have opinions.

Subscribe on YouTube@sagnikteaches

Then settle the data rule that governs everything: patient names, dates of birth, contact details, prescriptions and clinical findings stay inside systems the practice has a proper agreement with. General chat tools see only wording, templates and de-identified examples. The patient data confidentiality checklist goes through the questions to ask a vendor.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Week one: the phone, and what callers actually ask

Phones come first because the cost of a miss is easy to count. Say a practice with two testing rooms receives about 60 calls a day. The front-desk pair are mid-fitting or checking patients in for about 15 of them, so 8 to 12 go to voicemail, and some callers never leave a message. Even if only a third of those callers wanted an eye test and a third of those never ring back, that is a booking lost every couple of days. These numbers are illustrative; yours will differ, and the baseline tally will tell you.

The week-one job is not to install an AI receptionist on day one. It is to find out what callers ask. For the first three days, the front desk ticks a sheet for every call: new booking, rebook, repair or adjustment, collecting glasses, contact lens reorder, price question, insurance question, other. Then you decide.

If more than half the calls are bookings, rebooks and "are my glasses ready", an AI phone agent that books into your diary and sends a text is a good fit. AI receptionists for eye test bookings covers how these tools connect to the diary and what they cannot do. If most calls are price and insurance questions, a better first move is a better website page and an automated text reply. Cost varies a lot; as one reference point, Smith.ai lists a free AI receptionist plan for 25 calls a month, then $3 a call, which is enough to test with real calls before committing to anything larger.

Whichever tool you try, write the escalation rules before switching it on. Here is a filled-in set for an optometry practice.

Hand to a human immediately if the caller:
- says "pain", "sudden", "flashes", "floaters", "curtain", "lost vision" or "chemical"
- is a child under 8 asking for an urgent appointment
- mentions a recent eye operation or injury
- is angry, or asks twice to speak to a person
- asks about test results or a clinical finding
Script for urgent symptoms: "I'm going to put you through to a member of the
team now. If you cannot reach us, please contact an emergency eye service."
Never: give clinical advice, quote a prescription, or confirm a diagnosis.

Run ten test calls yourself, including awkward ones: a caller with a heavy accent, someone who changes their mind mid-sentence, someone asking for the optometrist by first name, and someone reporting sudden flashes of light. Listen to every recording. The test you are looking for is whether the urgent-symptom call reaches a person within seconds, every time. If it does not, the tool does not go live, however good the booking rate looks.

Measure for week one

Count calls answered by a person or the tool, bookings made by the tool, and calls handed over. Also note complaints. A sensible week-one target is simply "no urgent call mishandled and fewer voicemails than the baseline". Do not chase a percentage yet.

Week two: recalls that people actually answer

Recalls are the second job because the practice already knows who is due, and the wording is the only thing that needs help. Many practices send one generic reminder and stop. The messages below show the difference an AI draft can make when you give it the right instructions.

Give a general chat tool the wording brief, not the patient list. A usable prompt looks like this.

Write three recall messages for an independent optometry practice. Patients are
due for an eye examination at the interval our optometrists set: [adult interval]
for most adults, more often for children and some medical conditions, as advised.
Message 1: friendly SMS, under 300 characters, with a booking link placeholder
[link] and the placeholder [first name]. Message 2: email, 90 words, sent 3
weeks later, mentions that the practice has evening slots on [day]. Message 3:
a final SMS 6 weeks later that makes it easy to say "not now" with a reply word.
Do not give medical advice, do not claim the patient is at risk, do not use
urgency language. British English.

A typical output, illustrative only, will read well but needs fixing in predictable ways. It may say "your eyes could be at risk", which you delete. It may promise "evening slots" you do not have. It may be 340 characters when the SMS limit you set was 300. It may invent a clinical interval ("every 12 months") that differs from what your optometrists actually advise. Read every message against the practice's own recall policy and let the clinician approve the interval wording once, then reuse it.

The patient-specific parts, name, date of the last test and booking link, are filled by your practice software or messaging tool, not by the AI. ChatGPT for optometrists: recall letters, reviews and front-desk replies has more prompts.

Also use week two to add one contact lens job: an aftercare or reorder reminder. These are the messages patients most appreciate, and the timing is rule-based. A sample reorder text, illustrative: "Hi [first name], your contact lens supply should run out in about two weeks. Reply YES and we will have your next box ready to collect, or tap [link] to order." The trigger is the supply length on the last order, which your practice system holds; the AI only drafts the wording once.

One more guard for week two: set a send window. Reminders that land at 6 a.m. or on a Sunday evening feel intrusive, and the AI will not know your patients' habits. Fix the window in the messaging tool (say 10 a.m. to 6 p.m. on weekdays), cap contact at three messages per recall cycle, and suppress anyone who already has an appointment booked. These three rules cost nothing, and they prevent the complaints that make teams distrust automation.

A before and after

Before: one email, "It's time for your eye test. Call us to book." Sent once to everyone due that month. After: a three-step sequence with a one-tap booking link, a text that arrives at a sensible hour, and a polite opt-out. Illustrative sum: if a practice sends 300 recalls a month and 18% book under the old single email, that is 54 bookings. If the sequence lifts that to 24%, it is 72, so 18 extra. At an average first-visit value of, say, $110, that is about $1,980 a month. The lift is hypothetical, and the point of the baseline is to find the real number.

Measure for week two

Recalls sent, recalls booked within 21 days, unsubscribes or "stop" replies, and any complaint about tone. If stops rise above what you saw before, the messages are too frequent or too pushy. Cut the third message first.

Week three: exam notes, with the optometrist as the author

Notes are the first clinical-adjacent job, so the rules tighten. The AI drafts; the optometrist writes the record. In practice, that means an ambient scribe or dictation tool produces a draft in your record template, and the optometrist edits and signs it before it enters the patient record.

Start with one optometrist, one session a week, and a clear test plan. The detailed version is in AI scribe for optometrists: exam notes, templates and a test plan. The short version follows.

  1. Get consent. Tell patients at booking and at the start of the exam that a tool will draft the notes, and let them say no. Put a sign at reception and a line in the booking confirmation.
  2. Use a tool with a signed data agreement. Ask where audio goes, whether it is kept, who can access transcripts and whether recordings train the vendor's models. SimplePractice's Note Taker, for example, began keeping de-identified transcripts by default for clinicians who switched it on from June 2026 (earlier users stay opted out), which shows why you check the current settings rather than assume them.
  3. Map the template. Presenting complaint, history, medications, acuity, refraction, binocular vision, ocular health findings, plan, advice, recall interval. The tool should fill headings, not invent content.
  4. Check every draft. The optometrist compares the draft against their own memory and the instrument printouts. Numbers deserve most attention: sphere, cylinder, axis, add, intraocular pressure, cup-to-disc ratio.
  5. Log errors. A one-line tally sheet: wrong number, missing finding, invented finding, wrong side (left or right), wrong tone.

Here is a realistic mistake and how it showed up. In a test, a scribe heard "plus one point two five" and recorded +1.75 in the right eye, because the patient's earlier reading was +1.75 and the model leaned on it. The optometrist caught it only because they checked numbers against the phoropter printout. After that the practice added a rule: refraction values are typed or imported from the instrument, never taken from the transcript. The scribe handles narrative, the instruments handle numbers. (An illustration of the kind of slip to expect, not a report of a real case.)

Time matters too. Time two matched sessions: four exams without the tool and four with it, from the first word to the signed note. If the saving is under two minutes a patient after editing, the tool is not yet paying its way, though template tuning often improves this by the second week.

Measure for week three

Minutes per signed note, number of corrections per note, any patient who declined, and any clinical error caught. A single clinical error that reached the record unnoticed is a stop signal: pause, find out why, and fix the process before continuing.

Week four: marketing copy and the review of the month

The last week splits in two. Early in the week, use AI for the marketing jobs that have little downside: a draft of a Google Business Profile post, a page on children's eye tests, a plain-language explainer on varifocals, a reply template for reviews. Later in the week, review the numbers and decide what stays.

A realistic marketing task: a page answering "How long does an eye test take?" Give the AI the real facts, such as 30 minutes for a standard test, 45 if a retinal photograph is included, what to bring, and what happens afterwards. Ask for a 250-word draft in plain English. Then remove any claim you cannot stand behind, such as "detects early signs of every eye disease", and any outcome promise. Marketing about health carries claims rules, so keep the language factual: what happens, how long, what it costs.

For reviews, give the tool a template, not the review. Example reply wording for a positive review: "Thank you, [first name]. We're glad the visit went well and look forward to seeing you at your next test." For a negative review about waiting times, the reply states a fact, apologises briefly, and moves the conversation offline. Never put a patient's clinical details in a public reply, even if they posted them first, and never paste the review text, which may contain a name, into an unapproved tool.

For frame and lens talk, an explainer for the front desk helps: what blue-light coatings do and do not do, why progressive lenses take adjustment, how to choose between single vision and varifocals. Explaining lens options and eye test results with AI help shows a safe way to do it, with the optometrist checking any explanation of results.

The month-end review: keep, change or stop

On the last afternoon, put the four weeks side by side with a simple table.

JobBaselineAfterDecision
Phones10 calls a day to voicemail3 a day, 0 urgent mishandledKeep, extend hours
Recalls18% booked22% bookedKeep, test wording
Notes9 minutes a note6 minutes, 1.2 correctionsKeep for one clinician
MarketingNo posts4 posts, 2 pagesKeep, monthly slot

All figures above are illustrative. The decisions follow a simple rule: keep a job if it saved time or won bookings and caused no incident; change it if the benefit is real but the process leaked; stop it if you spent more effort checking than you saved. Stopping is a fine outcome. A month that rules out one tool cheaply is a good month.

The next month's plan then follows from the results. If phones worked, add the website chatbot from an AI chatbot for opticians. If notes worked, roll out to the second optometrist and add referral letters. Keep the same tally sheets running into month two, so the next review compares eight weeks of data with the baseline rather than four.

What stays out of the first month

Retinal-image analysis and any tool that suggests a diagnosis or referral urgency from an image are out of scope. They are clinical devices, and the evidence, approvals and liability sit with the manufacturer and the clinician, not with a prompt. If you are curious, ask vendors for their evidence and their regulatory status in writing, and decide separately, with the practice's insurer, whether to use them.

Also out: asking a general chatbot "what could this finding mean?" about a real patient, drafting a patient's results explanation without the optometrist reading it, and letting any tool message patients about clinical matters on its own. The firm line is that anything a patient might act on clinically passes through the optometrist first.

Two softer exclusions deserve a mention. Do not bolt on a second tool while the first is bedding in, because you will not know which one caused a problem. And do not promise the team that AI will "save hours" before you have measured it; promise only that you will test and keep what helps. That framing earns far more trust than a sales line.

Who does what, and the weekly rhythm

A small practice cannot afford a project office, so keep the routine light. Fifteen minutes at the start of each week: what are we trying, who is watching it, what is the stop rule? Fifteen minutes at the end: what did we count, what went wrong, what do we change? Put both on the calendar before the month begins, and keep a single shared page with the tallies, the prompt wording and the escalation rules, so the knowledge does not live in one person's head.

Roles are simple. The owner decides what stays and what goes. The practice manager runs the weekly check and keeps the tallies. One optometrist owns the clinical wording: recall intervals, advice sentences and the notes template. A dispenser or front-desk lead owns the phone script, because they know what callers say. If you are a solo optometrist, you hold all four roles, which is exactly why the plan allows one new job a week and no more.

If you would rather work through the sequencing with someone who has seen how these rollouts go wrong, that is what my AI implementation consultation is for.

Questions optometry owners ask before week one

Should an optometry practice use AI to read retinal images?

Not as part of this first-month plan. Image analysis that supports a diagnosis is a regulated clinical tool with its own evidence and approval questions. Keep the first month to phones, recalls, notes and marketing, where an error is a missed booking or a clumsy sentence, not a missed condition.

Can we paste patient names into ChatGPT to draft recall letters?

Use a mail-merge field or the practice software to insert names after the AI has written the template. The AI only needs the wording, the recall interval and the tone. Names, dates of birth and prescriptions stay in your practice system.

How many hours should the first month take?

Plan for roughly two to three hours a week from one owner or practice manager, plus short staff briefings. If the plan needs more than that, you are trying to do too much at once.

What if the team resists?

Start with the job they dislike most, usually repeat phone queries or recall chasing. When the first week removes an irritation rather than adding a task, resistance mostly fades. Never announce it as a way to cut hours.

Further reads

Sources: Smith.ai AI receptionist pricing page and SimplePractice's transcript retention FAQ, both checked 4 November 2026; the plan itself is general practice-management guidance, and no figures here come from a study.

Want your first month planned around your own practice?

On a 1:1 call we'll go through your phone volume, recall process and exam notes, pick the one job worth automating first and decide which tools you already own can do it.

Book a 1:1 call with me