What becomes an exception
- Provider connection, permission, timeout, delivery, webhook, or synchronization failure.
- Scheduling overlap, blocker, external change, inactive professional, removed capability, callout, or time-zone conflict.
- Payment failure, abandonment, mismatch, refund, dispute, reconciliation, or subscription problem.
- Unanswered transfer, exhausted route, unavailable department, queue failure, or voicemail processing problem.
- Invalid, incomplete, unauthorized, contradictory, or overdue business data/action.
Recovery
Each exception should state what failed, which business record is affected, the recommended recovery, severity, owner, due time, retry state, and audit history. A user can review, retry, resolve, ignore with a reason when allowed, or override only within their permission.
No disappearing failures
A failed automated action must not vanish because the system retried or the customer left the page. Retries remain idempotent and linked to the original command so they do not create duplicate bookings, payments, messages, or jobs.
✓
Source-of-truth policy
This article is part of the same maintained knowledge corpus used by NevoGuide. Live provider evidence and saved workspace configuration remain authoritative for your account’s current operational state.