Portfolio audit + fix

Multi-channel intake clarity

The site offered several ways to reach the practice, but did not clearly assign ownership, response time, or purpose to each intake route.

Front-desk handoffPatient-path auditFix 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

Multi-channel intake clarity

1Phone2Form3Message route4No visible owner or response time

Friction point: Several intake channels are available, but the patient cannot tell which team monitors each route or how quickly it will be handled.

Steward Snapshot

Annotated finding

Source reviewed
Website contact options, form route, location/hours surface, service links
Patient impact
Patient sends care, billing, scheduling, or urgent questions into the easiest-looking channel, not the right one.
Front-desk consequence
Requests require internal triage before scheduling, billing, or clinical routing can begin.
Cleanup direction
Name the purpose and owner for each route: appointments, existing-patient questions, billing/insurance, urgent issue, and general question.
Fixed path

Cleaned-up route

1Appointment request2Existing patient question3Billing / insurance4Urgent: phone-first

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
  • Multiple contact routes were available but not clearly differentiated.
  • Service intent and intake ownership were disconnected.
  • Location and logistics were not close enough to the request moment.
After
  • Every intake path gets a visible purpose and owner.
  • Top services point into the matching request path.
  • Hours, location, and parking support the form instead of living separately.

Recommended fixes

  • Assign every intake route a visible purpose: appointment, existing patient, billing, urgent issue, general question.

  • Add expected response time and who monitors the form.

  • Connect top services to the matching intake path.

  • Place location/hours/parking beside the request path to reduce logistical callbacks.

Audit matrix

Full path, not CTA theater.

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

AreaEvidence checkedFindingPatient impactFront-desk consequence
ConversionWebsite, form/message route, contact optionsMultiple routes are available without a clear owner for each.Patients may submit through the easiest-looking path, not the right path.Requests require internal handoff and interpretation.
TrustTeam/review/comfort proofTrust cues can be moved closer to the contact decision.Patients may need reassurance before leaving details.Front desk answers more “is this right for me?” questions.
ServicesService categories and intake mappingServices need clearer paths into the correct request type.Specific treatment patients may choose general contact.Staff has to identify the service before scheduling.
AccessibilityForms, labels, link clarityForm controls and links should make the action unambiguous.Patients may misunderstand field purpose or next step.Incomplete/vague submissions need callbacks.
Local detailsHours, location, parking, directionsLocation and timing details should support the intake route.Patients may ask logistical questions after submitting.Staff spends time resolving basics before care questions.

Want one of these for your practice?

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