The operational decision
Show the scope warning before a visitor starts sharing personal details. 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
Put concise wording beside the interaction and repeat it where a longer conversation starts; do not hide the only explanation in the footer.
Example wording for approval
“General office information only. Please do not share patient details. Contact the practice directly for appointments, records, prescriptions or individual health questions.”
Worked example
A visitor lands directly on a resource page with an embedded demo action, bypassing the homepage. If the only scope notice appears on the homepage, that visitor may never see it. Put the relevant short warning beside the action and include an audible notice when the call starts. Test a narrow screen where decorative content pushes text lower. The boundary must appear before the invitation to provide information, rather than after the visitor has already entered a narrative.
Handoff record
Record these task-specific fields: banner location, interaction trigger, wording version, reviewer.
Acceptance check
Open the page at a deep link and on a narrow screen. The boundary should remain visible before the visitor is invited to type or call.
Try Ava with your business’s public information ↗