When a CRM ownership rule fails in Concierge, the log currently shows a generic "Account Ownership: Not Matched" message with no further context. Admins diagnosing a routing failure have no way to determine whether the rule failed because no account was found in the CRM, an account was found but the owner is not a Chili Piper user, the account and owner were both found but the routing rule conditions weren't met, or some other reason. The tooltip indicator that appears on failures rarely provides actionable detail.

Chili Piper should surface structured failure reasons in Concierge ownership matching logs, distinguishing at minimum between: no matching CRM account found, account found but owner not provisioned in Chili Piper, and account and owner found but rule conditions not met.

Ownership matching failures are among the most common and hardest-to-diagnose routing issues. Without granular failure reasons, every investigation requires either guesswork or a support ticket. Structured failure states give admins the context to self-serve diagnosis and make targeted fixes to their routing configuration without needing to escalate.