- Call / request / contact actions sat together without patient-intent guidance.
- New-patient, urgent, existing-patient, and callback needs collapsed into one decision.
- Trust and contact information were present, but not sequenced around the booking moment.
Portfolio audit + fix
Contact route friction
The path had the right ingredients — Google profile, phone, request form, mobile contact links — but it asked patients to choose before the route explained which action fit their need.
Public-path proof
Before friction, the finding, and the cleaned-up path.
Source basis: public website, listing, mobile route, and contact pathBuilt from visible website/listing route patterns: visual enough to inspect quickly, specific enough for the front desk to act on.
Contact route friction
Friction point: Call, request, and generic contact are visible, but the page does not explain which path fits new patient, urgent, existing patient, or callback intent.
Annotated finding
- Source reviewed
- Google profile, mobile header, contact page, request route
- Patient impact
- Patient pauses to decide whether to call, request, or keep browsing because the next step is not mapped to intent.
- Front-desk consequence
- Front desk has to clarify urgency, patient status, and appointment type after the message arrives.
- Cleanup direction
- Split routine new-patient request, urgent phone-first, existing-patient callback, and general question routes with expectation-setting microcopy.
Cleaned-up route
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.
- Primary path becomes “new patient appointment.”
- Urgent issues become phone-first with clear language.
- Existing-patient callbacks get their own expectation-setting route.
Recommended fixes
- ✓
Make “new patient appointment” the primary routine path and keep urgent issues as phone-first.
- ✓
Add microcopy under contact actions: new patient, existing patient, emergency, callback.
- ✓
Mirror the same routing language on Google profile, mobile header, contact page, and request form.
- ✓
Add one tracking note for staff: which contact reason needed manual clarification.
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 profile, mobile header, contact page, appointment/request route | Multiple actions compete without enough patient-intent guidance. | Patients may choose a path that does not match their need. | Staff must clarify urgency, patient status, and next step after contact. |
| Trust | Homepage proof and practice identity cues | Trust exists, but it is not connected tightly to the moment of booking. | A patient may keep browsing instead of acting. | More calls arrive as exploratory questions instead of ready requests. |
| Services | Navigation and service discovery | Services are discoverable, but high-intent paths need clearer routing into the right appointment type. | Patients with urgent or specific needs may hunt. | Front desk gets broader, less qualified requests. |
| Mobile UX | First screen and tap path | The mobile route gives several possible next actions without priority. | Decision friction increases on small screens. | More manual interpretation after the request arrives. |
| Local SEO/schema | Public listing and site identity | NAP/identity surfaces should reinforce the same preferred contact route. | Search-to-site expectations may feel inconsistent. | Staff fields requests created by mismatched entry points. |
Want one of these for your practice?
Steward reviews one public patient path first, then turns it into a focused cleanup plan.