AI receptionist failure and incident log
Turn a phone-agent failure into a contained, testable correction without spreading a private transcript.
Done when: The impact is contained, the cause is reviewed and the corrected behavior passes a synthetic retest.
Enable JavaScript for on-page entry and smart printing, or print a blank copy from your browser and complete it offline.
Incident category and time window
Record the general failure type and reporting window, not a caller identity, recording or private transcript.
Expected versus actual behavior
Describe the approved behavior and the observed difference using a redacted category or invented reproduction.
Impact and containment
Identify affected workflow scope and the immediate pause, fallback or correction needed. Keep private evidence in the authorized system.
Owner and escalation
Assign an accountable role and the criteria for security, legal, vendor or business-owner review.
Root cause and change
Identify whether the issue was knowledge, routing, permissions, calendar logic, availability or another verified cause.
Retest and closure
Record the synthetic regression test, reviewer, release decision and monitoring check. Do not mark closed from an edit alone.
Reference links and review boundary
Use the current issuer, payer, regulator, platform or qualified professional for your exact activity and location. These links informed the planning questions; they do not make this an official form, full compliance review or permission to operate.
Healthcare businesses are welcome for business education. PublicProof does not receive, store or process patient information. A completed worksheet does not establish HIPAA compliance, transport qualification, professional authority, account approval, a credential, reimbursement or revenue.
Worksheet updated October 20, 2026. Verify changing requirements before relying on them.