Concepts
Enrichment and email verification
How SignalDock fills in company and contact data from several providers, and how it checks emails before anything is sent.
Waterfall enrichment
An organization can connect several enrichment integrations (for example KvK and
Apollo). SignalDock tries them in order of config.priority (lower first,
default 100), then by connection date. Each provider:
- records its own
enrichment_runsrow, so costs and failures are visible per provider; - only fills fields that are still empty, so an earlier, more trusted source is never overwritten;
- stops the waterfall once every target persona from the industry profile has a contact.
Email verification
After enrichment, every new or stale contact email is verified. Results are cached for 30 days.
| Status | Meaning |
|---|---|
valid | Syntax is valid and the domain accepts mail (MX or A record). |
risky | Role address (info@, sales@) or the check was inconclusive. |
invalid | Invalid syntax, disposable domain, or no mail server. |
unknown | Not checked yet. |
The built-in emailcheck verifier needs no API key and uses DNS only. Connect
a verification integration to use a paid verifier instead. Email sequences
skip invalid contacts, and every email to a risky or unknown address
waits for a human review, even on autopilot.
Last updated on