Agent #005 · Outbound
Prospect List Builder: governance & failure modes
What this agent is built not to do, and the specific ways it can fail if misconfigured.
Governance notes
- The agent never creates a CRM contact without explicit human approval in the review list — sourcing and CRM creation are two separate steps by design.
- Suppressed and unsubscribed individuals are never sourced or surfaced, full stop, regardless of how good a persona match they might otherwise be.
- Every candidate stores its source (Clay, Apollo, Sales Navigator) and relevance score, so a reviewer can see why a name showed up.
- Batch size matters for adoption, not just cost — small batches keep the human review step from becoming a backlog nobody clears.
Failure modes
- Contacts created without review: the workflow deliberately has no contact-create node — creation only happens through a separate, manually-triggered approved-list flow.
- Suppressed contact sourced anyway: the suppression check is the first node in the pipeline, not the last, specifically to prevent this.
- Low-relevance candidates flooding the list: a QA test asserts nothing below the configured relevance floor ever appears in the output.
- Rubber-stamp approvals: if SDRs start approving without reading, that’s a signal the relevance scoring needs to be tighter — not a reason to skip the review step.