GoHighLevel for Optometrists: Setup Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 11 September 2026 · 8 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
Setting up GoHighLevel for optometrists is a different job to setting it up for a gym or a trades business, because an optometry practice does not really run on lead generation. It runs on the recall cycle.
Most of your future revenue is already sitting in your database, attached to a review date that is twelve or twenty-four months away. The build that matters is the one that reliably surfaces those patients on the right day, books them, reminds them, and recovers them when they do not show — without ever pretending to be a clinical record system. This article is general information, not legal or clinical advice.
Quick Facts
| Item | What is actually true |
|---|---|
| Medicare timing, under 65 | MBS item 10910 (comprehensive initial consultation, attendance of more than 15 minutes) is payable once only within a 36-month period for a patient under 65 — Medicare Benefits Schedule, Department of Health and Aged Care, 2026. |
| Medicare timing, 65 and over | MBS item 10911 covers the equivalent attendance for a patient aged at least 65 and is payable once only within a 12-month period — Medicare Benefits Schedule, 2026. |
| Recall interval | Optometry Australia's guidance is that recall dates should be based on the evidence for best practice in each case — a clinical decision, not a billing rule. Set your own intervals clinically (Optometry Australia, recalls and reminders guidance). |
| Privacy obligation | APP 11.1 requires reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure — OAIC, Australian Privacy Principles guidelines. |
| SMS rules | Under the Spam Act 2003, commercial messages need consent, must identify the sending business (legal name, or name and ABN), and must carry a functional unsubscribe that does not require an account login — ACMA, 2024 guidance. |
| Record retention | The Privacy Act and the APPs do not set a fixed retention period for health records; state and territory law governs. Several jurisdictions require at least seven years from the last entry for adults — confirm the rule for your own state before you configure anything. |
| GHL's role | Front-of-house only: booking, reminders, recalls, reviews, reactivation. Not a clinical record system. |
Why the recall cycle decides whether a HighLevel optometry CRM pays for itself
An optometry practice has an unusual revenue shape. A patient walks in, gets examined, possibly buys spectacles or contact lenses, and then disappears for one to two years.
Everything in between is silence. If that silence is not managed, the patient drifts to whichever practice sent them a message first, or simply forgets until something goes wrong with their vision.
The single highest-value automation in any optometry practice is the one that turns a review date into a booked appointment. Everything else in your build — forms, review requests, reactivation campaigns — is secondary to that.
Clinical interval versus billing interval
These two numbers are not the same thing, and confusing them is the most common error I see in optometry builds.
| Concept | Who sets it | What it means for your workflow |
|---|---|---|
| Clinical recall interval | The examining optometrist | This is the date your automation should key off. It varies per patient and per risk profile. |
| MBS benefit eligibility | Medicare Benefits Schedule rules | Affects what can be claimed, not when a patient should be reviewed. Never hard-code a rebate assumption into a message. |
| Health fund extras reset | The patient's individual policy | Varies by fund, tier and anniversary date. Reference it generally; never state a dollar limit on a patient's behalf. |
Your workflow should carry the clinical date. Your copy can gently mention that funds and rebates are worth checking, and then stop.
Building the recall engine: long Wait steps versus a date custom field
There are two ways to hold a patient for twenty-four months inside a GoHighLevel Workflow, and only one of them survives contact with a real practice.
Option one: a very long Wait step
You add a Wait step of twelve or twenty-four months immediately after the appointment-completed trigger, then send the recall when it releases.
It looks elegant in the builder. The problem is duration: a contact sitting in a Wait step is parked inside a specific published version of that Workflow, and over two years you will almost certainly edit, restructure or rebuild that Workflow several times.
Anything you do to a live Workflow over a 24-month horizon puts a two-year queue of parked patients at risk, and you will not find out until the recalls silently fail to arrive. That is not a theoretical risk in an optometry practice — it is an entire year of recalls.
Option two: a date custom field (the one I build)
Create a date-type custom field — call it Next Review Due. At the end of the appointment workflow, use an Update Contact Field action to write a date into it.
Then build a completely separate Workflow that uses the Custom Date Reminder trigger, which starts a workflow before, on, or after a date field you select (see the HighLevel help documentation for the Custom Date Reminder trigger). Nobody is parked. The date is data on the contact record, and the recall Workflow is a short, safe, editable sequence.
| Factor | Long Wait step | Date custom field |
|---|---|---|
| Survives a workflow rebuild | Fragile | Yes — the date lives on the contact |
| Can you see who is due next month? | No, it is invisible inside the workflow | Yes — filter contacts by the date field |
| Changing one patient's interval | Remove and re-add them manually | Edit the date on the contact |
| Bulk-loading an existing patient list | Awkward | Straightforward via import |
| Main failure mode | Silent, discovered years later | Blank date field — the trigger will not fire without a value |
One caveat worth knowing: the Custom Date Reminder trigger will not fire for contacts that have no value in the chosen date field, so your first job on any existing database is a completeness audit, not a campaign.
Structuring the recall sequence
I fire the recall Workflow thirty days before the review date, then run a short ladder with Wait steps measured in days — not years — and a Goal event that exits the contact the moment they book.
The mechanics are close to a standard service reminder workflow, with one optometry-specific addition: after the final unanswered touch, tag the contact and drop them into a slower nurture rather than deleting them from the cycle.
Booking, reminders and no-show recovery for an optometry practice
Once the recall fires, the patient needs somewhere to land. That is a GoHighLevel Calendar, not a phone number in a text message.
Calendars
Most practices need separate Calendars for different appointment types — comprehensive examination, contact lens fitting or aftercare, and a shorter follow-up — because the durations are genuinely different and a single calendar will wreck your day sheet.
If you have more than one optometrist, round-robin distribution keeps the book balanced. The general approach is covered in our guide to calendar setup for multiple practitioners.
The reminder ladder
- Immediate confirmation on booking, with the appointment type, date, practitioner and address pulled in via custom values.
- A reminder a few days out, with a clear reschedule link rather than a request to phone.
- A short same-day or day-before SMS with anything the patient needs to bring — current spectacles, sunglasses, their health fund card.
The reschedule link is the single highest-leverage element in the whole ladder, because a patient who can move an appointment in two taps rarely becomes a no-show.
No-show recovery
When an appointment status changes to no-show, trigger a short, warm sequence: one message within the hour offering to rebook, one the following day, and then a tag that puts the patient back onto the recall list with a revised date.
Pair this with missed-call text-back on your practice line, so the patients who do ring you back are not lost to a busy front desk.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
Spectacle and contact lens reorder prompts
Contact lens wearers are a second, faster cycle running underneath the examination cycle, and they are far more predictable.
Use a separate date custom field — CL Supply Runs Out — set when the patient collects a supply. The reorder prompt is then the same architecture as the recall: a date field, a Custom Date Reminder trigger, a short sequence, and a Goal event on order placed.
Spectacle prompts are looser. A sensible pattern is a check-in a few weeks after collection to confirm the patient is adapting well, then a much later message about lens coatings, a second pair or prescription sunglasses — framed as an offer, never as a clinical instruction.
Keep supply messaging and clinical recall in two different Workflows with two different tags, or you will eventually send a "time for your review" message to someone who was examined last month and simply ran out of lenses.
Medicare, health funds and what your copy can safely say
This is where optometry builds get practices into trouble, because the automation is tempting and the facts are patient-specific.
Medicare's benefit timing is real but narrow. As set out in the Medicare Benefits Schedule (Department of Health and Aged Care, 2026), item 10910 — a comprehensive initial consultation of more than 15 minutes for a patient under 65 — is payable once only within a 36-month period, while item 10911 covers the equivalent attendance for a patient aged at least 65 and is payable once only within a 12-month period.
That is a claiming rule, not a recall schedule. Optometry Australia's position is that recall dates should be based on the evidence for best practice in each case — in other words, your clinical judgement sets the interval.
- Do not state a rebate amount, gap or out-of-pocket figure in an automated message.
- Do not tell a patient they are "due for a bulk-billed test" — you cannot verify their claiming history from a CRM.
- Do invite them to check their own Medicare and health fund position with you when they book.
The safe pattern is to automate the invitation and handle the money conversation with a human at the front desk.
Patient data, the Privacy Act, and what must never live in GoHighLevel
Let me be unambiguous: GoHighLevel is not a clinical system and must not store clinical notes, refraction results, retinal images, OCT scans or diagnoses. Those belong in your practice management system, which is designed, audited and retained for that purpose.
GHL is the front-of-house layer — the part of the practice that talks to patients about appointments. Treating it as anything more creates a records problem you do not want to explain to a regulator.
Under APP 11.1, an entity that holds personal information must take reasonable steps to protect it from misuse, interference and loss, and from unauthorised access, modification or disclosure (OAIC, APP 11 guidelines). APP 11.2 adds an obligation to destroy or de-identify personal information once it is no longer needed for a permitted purpose.
| Data | Practice management system | GoHighLevel |
|---|---|---|
| Clinical notes, diagnoses, refraction, imaging | Yes — sole source of truth | Never |
| Medicare number, health fund member number | Yes | No |
| Name, mobile, email, address | Yes | Yes — needed to communicate |
| Next review due date (date only, no reason) | Yes | Yes — as a date custom field |
| Appointment type and status | Yes | Yes — for booking and reminders |
| Marketing consent and unsubscribe state | Optional | Yes — this is exactly what GHL is for |
Practical controls
Restrict sub-account user permissions so casual staff cannot export the contact database. Use LC Phone or your own Twilio number so message logs stay inside the sub-account. Review your forms so no free-text field invites a patient to describe symptoms.
And read the Australian SMS compliance rules before your first send — ACMA guidance requires consent, clear sender identification using your legal name or name and ABN, and a working unsubscribe that does not force the patient to log in anywhere.
Retention is governed by state and territory law rather than the APPs, and several jurisdictions require at least seven years from the last entry for adults. Confirm the rule that applies to your practice, then set a matching de-identification routine for anything sitting in your CRM.
Rolling it out without breaking your existing patient list
Start with the patients whose review dates are already in the past. A database reactivation campaign against that group usually funds the rest of the build.
Send in controlled batches, not one enormous blast — your front desk has to answer the replies, and a new sending number needs a gentle ramp.
Once the build is stable in one practice, you can load it as a snapshot into a second location, then adjust custom values for the new site's name, address and practitioners.
Common mistakes to avoid
- Parking patients in 12 or 24-month Wait steps. Use a date custom field and the Custom Date Reminder trigger instead.
- Importing a patient list with empty review dates. The trigger has nothing to fire on, and the silence looks exactly like a working system.
- Putting clinical information into GHL notes or custom fields. It is not a clinical record system and should never be treated as one.
- Quoting rebates, gaps or health fund limits in automated copy. You cannot verify a patient's claiming history from a CRM.
- Omitting a Goal event on appointment booked. Patients who have already rebooked keep receiving recall messages, and they tell the front desk about it.
- Running recall and contact lens supply messaging from the same Workflow. Two cycles, two tags, two sequences.
If you want the recall engine built and tested for your practice rather than left as a good intention, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Can GoHighLevel replace my optometry practice management system?
No, and it should not try to. GoHighLevel is a front-of-house layer for booking, reminders, recalls, reviews and reactivation, while clinical records, imaging and billing stay in your practice management system. The two work together, with GHL holding only the contact details and dates it needs to communicate.
Should I use a 24-month Wait step or a date custom field for recalls?
Use a date custom field. A patient sitting in a two-year Wait step is parked inside one published version of a Workflow you will almost certainly edit before the wait expires, and the failure is silent. A date field on the contact plus a short Custom Date Reminder workflow is far easier to audit, filter and repair.
Is it legal to send recall SMS to patients in Australia?
Commercial electronic messages fall under the Spam Act 2003, which per ACMA guidance requires consent, clear identification of the sending business using your legal name or name and ABN, and a functional unsubscribe that does not require the recipient to create or log into an account. Health-related recall messaging also needs to respect the Australian Privacy Principles. Get advice on your own consent wording rather than copying another practice's.
Can I store clinical notes or retinal images in GoHighLevel?
No. Clinical notes, refraction results, diagnoses and imaging belong exclusively in your practice management system. Storing them in a marketing CRM creates unnecessary risk under APP 11, which requires reasonable steps to protect personal information from unauthorised access or disclosure.
How do I stop patients being messaged after they have already rebooked?
Add a Goal event to the recall Workflow that exits the contact when an appointment is booked on the relevant Calendar. Back it up with a tag applied on booking and a filter at the start of the sequence. Without that exit, patients who rebook by phone keep receiving reminders and complain to your front desk.
Can Conversation AI handle patient enquiries for an optometry practice?
It can handle scheduling-level questions well: opening hours, location, appointment types, availability and rescheduling. It should never answer clinical questions, interpret symptoms or discuss a patient's results. Set a clear handover rule so anything clinical routes straight to a human.
How long does the recall engine take to build?
For a single-site practice with a clean patient list, the core build of date fields, Calendars, reminder ladder, recall sequence and no-show recovery is typically a matter of days rather than weeks. The longer task is almost always data: auditing review dates, cleaning mobile numbers and confirming consent before anything is switched on.
Related Articles on HL Growth Partner
Builds for other clinical niches
- GoHighLevel for dental clinics
- Allied health snapshot for physiotherapists
- GoHighLevel for veterinary clinics
