# Clinic Answerworthiness Playbook

## Why this exists
Patients use search, maps, and AI tools to decide whether a clinic feels clear, current, and safe before they ever call. This playbook helps a clinic publish answers that reduce anxiety instead of forcing the front desk to repeat the same explanations all day.

## Patient Question Families
- Fit: "Do you actually treat this problem, or am I in the wrong place?"
- Timing: "How quickly can I be seen, and what happens first?"
- Cost: "Is this covered, financed, or likely to turn into a surprise bill?"
- Comfort: "Will this hurt, embarrass me, or require recovery time?"
- Trust: "Why should I believe this clinic is better prepared than the next one?"
- Logistics: "What do I bring, how long will I wait, and what happens when I arrive?"

## Answer Architecture
Build every clinic answer surface with the same sequence:
1. State who the clinic is for.
2. Clarify when the clinic is and is not the right fit.
3. Explain the next step in plain language.
4. Add proof that the clinic handles the problem routinely.
5. Remove one fear about timing, comfort, cost, or confusion.

Use that structure on:
- service pages
- location pages
- FAQ blocks
- after-hours routing language
- appointment-confirmation and pre-visit email copy

## Trust and Triage Blocks
Every clinic should maintain a reusable library of trust and triage blocks:
- "When to call us vs. when to seek emergency care"
- "What to expect at the first visit"
- "How wait times and scheduling work here"
- "Provider credibility and training"
- "Review-backed patient confidence cues"
- "Financing, insurance, or consult-fee clarity"

The goal is not to publish more words. The goal is to make repeated patient uncertainty easier to resolve consistently across the public journey.

## Review Cadence
Use a monthly review loop:
- Pull the top 20 repeated questions from calls, chat, forms, and reviews.
- Mark which questions still lack a strong public answer.
- Refresh one service page, one FAQ block, and one local trust section every month.
- Check whether the new answers reduced front-desk repetition or improved booking confidence.

## Operating Notes
- Avoid fake certainty. Clear boundaries build more trust than overpromising.
- Keep answer blocks reusable so the same logic can feed pages, scripts, and AI-ready surfaces.
- Treat every unclear answer as a leak in the front door, not just a content issue.