The operational decision
Make the destination clear before a visitor taps a telephone link. The website should let a visitor find public office information without starting an intake conversation. Build each page around a concrete visitor task and keep the route to the practice visible.
Prepare the workflow
Use distinct labels for the demonstration and the practice contact; confirm the number behind the button rather than trusting its visible text.
Example wording for approval
“Call the practice directly for patient questions. The separate Ava demonstration uses fictional office information and does not connect to a clinical team.”
Worked example
On a fictional mobile page, the visible label says Contact the practice but its telephone link opens the demo number. The page may look correct on a desktop screenshot while still sending callers to the wrong destination. Inspect the actual link, test it on a device and label the demonstration separately. The acceptance record should include the visible text and destination together. Neither a correct number with the wrong label nor a correct label with the wrong number is sufficient.
Handoff record
Record these task-specific fields: button label, destination number, page URL, reviewer.
Acceptance check
Compare the displayed number with the actual link on a phone. A demo button must never appear to be the practice's patient line.
Try Ava with your business’s public information ↗