Account Engagement Monitor: QA checklist

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

Deployment checklist

• ☐ At least one signal source connected and verified
• ☐ Four HubSpot company properties created
• ☐ Signal weighting and decay config written and versioned
• ☐ n8n workflow imported, marked nodes configured
• ☐ Demo-data run matches `demo-data/sample-output.json`
• ☐ Anonymous-identity governance test passes
• ☐ Slack alert routing verified for owned and unowned accounts
• ☐ QA checklist completed by a non-builder
• ☐ Rollback tested

Failure-mode verification

• ☐ Verified: Alert fatigue from too many Hot flags does not occur (mitigation: QA checks weekly Hot-flag volume against a sane ceiling; threshold tuned if exceeded)
• ☐ Verified: Anonymous visitor treated as a named contact does not occur (mitigation: Schema enforces account-level-only signal records; QA test asserts no person field is populated from reverse-IP data)
• ☐ Verified: Stale spike keeps account Hot for weeks does not occur (mitigation: Rolling 14-day decay window is a required config field, not optional)
• ☐ Verified: Alert goes to no one does not occur (mitigation: Alerts route to a shared queue Slack channel when `hubspot_owner_id` is empty)

Governance verification

• ☐ Agent writes only to its agent-owned fields: `account_engagement_signal_score`, `account_temperature`, `account_top_signal`, `account_last_signal_date` (company)
• ☐ 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)