Agent #007 · ABM
Account Engagement Monitor: governance & failure modes
What this agent is built not to do, and the specific ways it can fail if misconfigured.
Governance notes
- Never claims an anonymous website visitor is a specific known individual — reverse-IP signals stay account-level only, unless a click is authenticated or an activity is CRM-logged.
- No auto-triggered outreach of any kind — every Hot alert routes to a human for a follow-up decision, never an automated sequence enrollment.
- Only accounts on the active target list are monitored; this agent doesn’t scan the whole web traffic firehose looking for signal.
- A weekly check on Hot-flag volume catches an over-sensitive threshold before it trains reps to start ignoring the alert channel.
Failure modes
- Alert fatigue: if the Hot threshold is set too low, reps learn to ignore the channel fast — caught by a weekly volume check against a sane ceiling.
- Anonymous visitor treated as a named contact: a QA test specifically asserts no person-level field is ever populated from reverse-IP-only data.
- A stale spike keeping an account Hot for weeks: the 14-day rolling decay window is a required config field, not an optional nice-to-have.
- Alert goes to nobody: unowned accounts route to a shared Slack queue rather than silently failing to alert anyone.