TL;DR
A missed consultation records an outcome, not its cause. Compare the original offer, booking action, confirmation and practical appointment details. Repair documented contradictions and delivery problems. Preserve unknown reasons rather than assuming every no-show reflects poor lead quality or a need for a stronger sales sequence.
Start with the appointment that was actually promised
Ask the scheduling owner to define the relevant status. Was the person confirmed for a consultation, waiting for confirmation, rescheduled or canceled? Keep administrative errors and duplicate records separate from missed confirmed appointments. A dashboard label is not a reliable explanation until the underlying states are clear.
Then preserve the version of the offer that was live when the request was made. A current landing page may no longer show what the person encountered. Use approved public creative and change records, without placing identifiable patient details in a marketing audit.
For a medspa, distinguish a consultation about a service from delivery of the service itself. Also check named-provider language, office, fee conditions and any package-credit wording. A consultation confirmation should not silently transform into a promise of treatment or a different provider.
Use a promise-to-appointment audit
This is an original operational review, not a model for predicting attendance. Use the same public journey and appointment type under review.
| Surface or state | Evidence to compare | Question to resolve |
|---|---|---|
| Ad or social post | Archived approved creative and destination | What action and commercial conditions did the invitation describe? |
| Landing page | Service, provider, office and action language | Did the destination preserve those conditions? |
| Booking interface | Actual request or reservation behavior | Was a slot confirmed or merely requested? |
| Submission feedback | Screen and approved automated message | Did the visitor receive an accurate statement of the result? |
| Appointment confirmation | Actual appointment type, office and provider route | Does it match what the practice recorded? |
| Practical instructions | Approved location, arrival, fee and change process | Are the necessary administrative details usable? |
| Attendance status | Scheduling record under the defined rule | What outcome is verified, and what remains unknown? |
Record each mismatch as a specific defect: affected surface ___; earlier promise ___; later message ___; approved correction ___; owner ___. The audit is complete when the actual displays and workflow have been rechecked, not merely when someone has agreed to rewrite them.
Test delivery as well as wording
A clear confirmation cannot help if the configured destination fails. Coordinate a labeled practice-controlled test with operations so it does not create real outreach or an unwanted booking. Check the public result, the practice's receipt and the approved confirmation behavior.
World Wide Web Consortium's forms tutorial recommends clear feedback after submission, including understandable errors and success feedback. Use that as an interface check, while verifying operational receipt separately. World Wide Web Consortium form notification guidance. Its guidance does not establish that a confirmation will prevent a missed appointment.
Use the appointment-state wording guide when the button or acknowledgement promises the wrong state. If the technical path breaks, capture the failure point before making unrelated creative changes.
Keep reasons separate from hypotheses
If a person supplies a reason through an approved process, preserve the appropriate operational category. Do not expand a short explanation into a narrative about intent, finances or treatment preferences. If no reason is available, record unknown.
A mismatch in the journey is a defect worth correcting. It does not prove that the defect caused every missed appointment. Likewise, a campaign's association with missed consultations does not by itself establish that its audience is unsuitable. Check definitions, service mix, appointment availability and the observed promise before assigning blame.
Avoid pressure-based follow-up as a substitute for understanding the process. The practice's responsible personnel should approve contact purpose, content, timing and restrictions. This audit does not propose deposit rules, medical reminders or a clinical follow-up protocol.
Evaluate the repair using comparable states
Choose the specific question the change should answer. If the button mislabeled a request, verify corrected wording and system behavior. If arrival information conflicted across messages, confirm that the approved office details now match. Then observe subsequent records under the same event definitions and disclose relevant changes.
Keep cancellations, reschedules, unconfirmed requests and missed confirmed consultations separate. Note changes in the promoted service or provider availability rather than treating every period as comparable. A cleaner workflow is a verified improvement; a causal attendance claim needs further evidence.
GetPatients has a commercial interest in healthcare visibility services. Ask any proposed partner which defect it will own, how completion will be checked and which outcomes remain outside the evidence. Use the claim-display review to keep approved conditions intact across the revised creative.
Frequently asked questions
Does a high volume of forms explain our missed consultations?
It does not identify the cause. Define the actual request and appointment states, then inspect the offer and handling path. Avoid inferring individual motives from a dashboard total.
Should we add a deposit to solve the problem?
That is a separate commercial, operational and jurisdiction-specific decision. This audit first identifies what was promised, confirmed and delivered. It does not claim a fee policy will change attendance.
Can an agency be responsible for attendance?
Ask what it actually controls and what the agreement requires. Creative accuracy, notification behavior and handoff completion can be defined deliverables; attendance should remain a separately verified outcome.