The operational decision
Prevent a future compliance discussion from being read as current patient-workflow authorization. Evaluate the specific workflow you are buying rather than a broad list of features. An integration logo, fluent demonstration or sales statement is not evidence that your office connection is configured and tested.
Prepare the workflow
Record the present limitation prominently and send any proposed patient use to the practice's qualified reviewers before technical activation.
Example wording for approval
“AssistCall does not currently sign BAAs. This launch remains public-information only; a proposed patient workflow requires a separate readiness decision and must stay disabled.”
Worked example
A fictional buyer selects the proposed scheduling-readiness offer and assumes the higher price permits patient intake immediately. The sales and onboarding response should restate the current limitation: AssistCall does not currently sign BAAs, and patient workflows remain disabled. A readiness discussion may document dependencies and reviewing roles, but must not open a patient form or request an EHR export. Keep payment, technical exploration and permission to activate a different workflow as distinct decisions.
Handoff record
Record these task-specific fields: current scope, proposed use, reviewing roles, activation status.
Acceptance check
Ask whether buying the higher-priced offer permits patient intake immediately. The answer must remain no until the stated prerequisites and separate activation review are satisfied.
Try Ava with your business’s public information ↗