The operational decision
Avoid turning a broad office-information answer into a coverage determination. This launch answers general office questions only. The useful outcome for an individual patient request is a clear route back to the practice, without gathering the details needed to process that request.
Prepare the workflow
Only repeat an approved public statement if one exists; never request member numbers, policy documents or a caller's treatment details.
Example wording for approval
“Please check individual insurance or coverage questions with the practice and your insurer. Do not share member numbers here; this line cannot verify personal coverage.”
Worked example
A fictional public service page mentions that reception can discuss insurance questions. A caller asks whether a specific planned service is covered and offers a member number. The assistant should not infer coverage from the public statement or accept the number. It directs the caller to the practice and insurer as appropriate to the approved wording. The editor's follow-up is to clarify the public information boundary, not to build a list of accepted individual policies from calls.
Handoff record
Record these task-specific fields: public statement owner, coverage boundary, approved contact, reviewer.
Acceptance check
Ask whether a particular service will be paid for. The assistant should not infer coverage from a general insurer name on the website.
Try Ava with your business’s public information ↗