All builds Talk to me
Eye care · front desk

Front desk knowledge base

Livesince Aug 2026

Anyone at the front desk finds the right answer in one search, without pulling a manager away.

About 200 hrs/yr

of front-desk time returned

About 4 questions a day at 10 minutes each, now one search.

35 pages

plus a 41-price grid, kept current by the managers

The front desk knowledge base answering a question during a live call
A caller's question, answered in seconds.

How it works

  1. A caller asks

    A caller asks something unusual, and whoever is at the desk can answer it during the call instead of putting them on hold.

    The front desk knowledge base answering a question during a live call
  2. Search one box

    One search box across every page and price. It's plain search, not a chat box, so it can never invent a rule.

  3. Answer on screen

    Decision guides answer the tricky ones on screen: which doctor can see this patient, the right price, and whether to collect or bill.

  4. Managers keep it current

    Two managers keep it current right in the browser, with revision history and one-click restore. No developer needed for a content change.

What I built

Answers in one search

35 pages of front desk protocol in 7 sections and a live 41-price grid, on every front desk device and searchable from one box, with no AI to invent a rule.

Decision guides

Guides that bring the buried exceptions to the surface: which doctors a patient can see, the right price with prompt-pay, whether to collect or bill a refraction, and how urgent a symptom is.

Managers edit it themselves

Two managers edit any page in the browser, with revision history in plain English and one-click restore. No developer is needed for a content change.

Locked to the clinic

Only clinic Google logins get in, and only the two managers can edit. Pages are sanitized as they render, and a monthly export keeps a full backup.

BeforeAfter An unusual questionInterrupt a managerOne search, answered on the callWhen someone leavesTheir know-how leaves tooIt stays in the app
In their words

“This is highly valuable, both in the short term and long term. It's already saving a lot of time.”

Jill Romines, Front Office Manager, Wichita Family Vision

Engineering

Row-level security, not app checks: only the two editors can write, whatever the browser sends.

How it fits together
A static PWA reading from Supabase. Row-level security lets everyone read and two named editors write.
Tested
A no-dependency test suite gates every deploy. Pages sanitized at render.
Runs on
The front desk tablet and PCs.

My role. I built it, from the content model to in-app editing.