The operational decision
Confirm that incomplete scheduling information produces an honest fallback. Testing needs an expected result before the call begins. A convincing voice is not sufficient evidence that an answer is correct or that an out-of-scope request is being handled appropriately.
Prepare the workflow
Remove one day from a fictional office sheet and test that exact day; do not let a weekly pattern stand in for missing approval.
Example wording for approval
“I do not have verified public hours for that day. Please check the practice's current notice or contact the office directly.”
Worked example
Remove Sunday from a fictional schedule while leaving Monday through Saturday intact. Ask whether the office opens on Sunday, then ask whether it follows Saturday's hours. The expected result remains an uncertainty answer and the practice contact route. If the assistant extrapolates the missing day, strengthen the rule against inventing schedule facts. Once staff supply an approved Sunday entry, repeat both questions and confirm the answer now comes from that explicit entry rather than the old inference.
Handoff record
Record these task-specific fields: missing day, source version, fallback answer, owner.
Acceptance check
Ask whether Saturday follows Friday's schedule. A pass avoids inferring opening hours from a nearby weekday or past exception.
Try Ava with your business’s public information ↗