Lead Routing Agent: QA checklist

To be completed by a non-builder reviewer before go-live.

Deployment checklist

• ☐ All six routing rule sources connected and current (suppression, customer list, open opps, named accounts, territory, round-robin pool)
• ☐ Four HubSpot lead properties created
• ☐ n8n workflow imported in shadow mode first
• ☐ Shadow-mode accuracy reviewed against real leads (min. two weeks or 100 leads)
• ☐ Ambiguous-lead exception test passes
• ☐ Demo-data run matches `demo-data/sample-output.json`
• ☐ Production go-live explicitly approved by RevOps after shadow-mode review
• ☐ QA checklist completed by a non-builder
• ☐ Rollback tested

Failure-mode verification

• ☐ Verified: Existing customer routed as new logo does not occur (mitigation: Rule #2 runs unconditionally before round-robin; QA test asserts a customer-domain lead never reaches round-robin)
• ☐ Verified: Named account routed to wrong rep does not occur (mitigation: List ownership assigned; QA includes a staleness check on list last-updated date)
• ☐ Verified: Ambiguous lead routed confidently does not occur (mitigation: QA test constructs a deliberately ambiguous lead and asserts it lands in the exception queue, not auto-routed)
• ☐ Verified: Shadow mode skipped, straight to production does not occur (mitigation: Deployment checklist makes shadow-mode sign-off a hard gate before the production toggle is flipped)

Governance verification

• ☐ Agent writes only to its agent-owned fields: `routing_status`, `routing_matched_rule`, `routing_timestamp`, `routing_exception_reason` (lead/contact)
• ☐ No auto-send, auto-close, auto-route, or auto-create action occurs without the human step described in `agent-spec.md`
• ☐ Confidence/model-version is present on every written record where applicable
• ☐ Demo-data run output matches `demo-data/sample-output.json` in structure

Sign-off

Reviewer name: _______________ Date: _______________ Result: Pass / Fail (attach notes)