Portfolio audit + fix

Booking route consistency

The site could get a patient to a booking/request action, but the patient could not always tell whether they were booking a confirmed visit, sending a request, or waiting for a callback.

Booking flow→Patient-path audit→Fix plan

Public-path proof

Before friction, the finding, and the cleaned-up path.

Source basis: public website, listing, mobile route, and contact path

Built from visible website/listing route patterns: visual enough to inspect quickly, specific enough for the front desk to act on.

Before path

Booking route consistency

1Google appointment action2Website request button3Scheduler / callback language shifts4Patient unsure what is confirmed

Friction point: The public path moves between book, request, and callback language without saying what is immediate versus staff-confirmed.

Steward Snapshot

Annotated finding

Source reviewed: Google appointment action, website CTA, request page, mobile booking route
Patient impact: Patient may not know whether they booked a visit, sent a request, or should wait for the office to call.
Front-desk consequence: Staff starts follow-up by resetting expectations instead of scheduling cleanly.
Cleanup direction: Use one booking vocabulary across listing, header, request page, and form confirmation; add visit-type and response-time labels before form fields.

Fixed path

Cleaned-up route

1Choose visit type2Request appointment3Staff confirms timing4Insurance note before form

Outcome: The public path tells the patient what to do next and gives the front desk cleaner intent before follow-up.

Representative public-path artifact. Built from visible route patterns only — no PHI, no private analytics, no unsupported growth or revenue claims.

Before → after

What would change for the patient and the front desk.

Before

Google action and website request language set different expectations.
Treatment intent was not connected to the booking route.
Insurance and response-time questions appeared too late.

After

Booking, request, call, and callback are named separately.
Visit type appears before long intake fields.
Insurance/financing and response-time notes move beside the action.

Recommended fixes

✓
Rename CTAs so each one tells the patient exactly what happens next: book, request, call, or callback.
✓
Add visit-type selection before detailed intake.
✓
Place insurance/financing and response-time notes beside the request action.
✓
Route emergency and existing-patient needs away from the generic appointment request.

Audit matrix

Full path, not CTA theater.

Each row connects public evidence to patient hesitation and front-desk recovery work.

Area	Evidence checked	Finding	Patient impact	Front-desk consequence
Conversion	Google appointment action and website booking route	Booking/request language is not framed with the same expectation.	Patients may not know whether they are booking, requesting, or waiting for a callback.	Staff must reset expectations after submission.
Trust	Reviews, team credibility, service promise	Trust proof is useful but should appear before deeper intake asks.	Patients may hesitate before form completion.	More pre-booking questions reach the phone.
Services	Appointment routes tied to services	Specific treatment intent is not always attached to the booking path.	Patients with implants/aligners/emergency needs may start in a generic route.	Requests need manual service triage.
Mobile UX	Scheduler/request view on mobile	Mobile path should reduce choices, not multiply them.	Small-screen users may abandon or call with vague context.	Staff receives less structured inquiries.
Content/new patient	Insurance, first-visit, response expectations	Response timing and new-patient expectations need to be scannable near the booking action.	Patients wonder what happens next.	Follow-up calls start with expectation-setting instead of scheduling.

Want one of these for your practice?

Steward reviews one public patient path first, then turns it into a focused cleanup plan.

Request a Steward Snapshot View portfolio