## TL;DR

Screen every enriched address before it enters a sendable pool: flag free-mail domains and personal-address patterns at the enrichment step, and route flagged leads to human review or skip them. If reputation already dropped, pause sends from the domain, check blocklists, and purge personal addresses from active sequences before resuming.

```text
agent's enrichment step returned a personal Gmail for a CEO and it emailed it  -  the message got flagged and the domain reputation dropped
```

## Steps

1. Add a domain check on the enrichment output: flag addresses on free-mail providers and any address marked personal by the vendor. Expected: a CEO record with a personal Gmail is flagged, not queued for sending.

2. Route flagged leads to manual review or exclude them from automated sends until a work address is confirmed. Expected: zero automated sends go to flagged personal addresses.

3. If the domain reputation already dropped: pause the sending domain, check major blocklists, and only resume with confirmed work addresses after warming. Expected: blocklist checks come back clean before volume resumes.

4. Purge already-collected personal addresses from active sequences and suppression-review the sends that already went out. Expected: no active sequence still targets a flagged personal address.

## Use this when

- enrichment returned a personal email for a B2B prospect
- messages got flagged after emailing non-work addresses
- domain reputation dropped following enrichment-driven sends

## Not for this skill when

- a contact who gave you that address directly and consented to be emailed there
- consumer or B2C outreach where a personal address is the normal channel
- transactional mail the recipient explicitly requested

## Variant phrasings

### enrichment returned a Gmail for a prospect

Same root cause: the agent sent to whatever address field was populated.

### emailed a personal address and got flagged

Same fix: screen enrichment output before it becomes sendable.

### domain reputation hit after personal-email sends

Same fix plus the reputation recovery steps above.

## Why it happens

Enrichment vendors aggregate whatever addresses they can find - work, personal, old - into one record, and the agent reads the first populated email field as the sendable address. Nothing in the pipeline distinguishes a corporate address from a personal one, so the agent emails a CEO's personal Gmail exactly as it would a work address. Recipients flag unexpected B2B mail to personal inboxes, and the flags land on the sending domain's reputation.

## Edge cases

- Founders whose only public address is personal: keep them flagged and require explicit human approval per send.
- Some vendors label address type unreliably - treat unmarked addresses from people-search sources as suspect by default.
- Purging does not undo flags already filed; reputation recovery is measured in weeks, so set expectations before resuming volume.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_e48fKi2TmERmuAw-Fg5YIA