Workflows
Email Discovery And Verification
Understand how GrowthEngene finds, verifies, scores, and uses emails for outreach workflows.
Quick Answer
How Email Discovery Works
Email discovery can combine contact evidence, provider results, pattern learning, verification checks, and confidence scoring to determine whether an email can be used.
The system is evidence-first. It should prefer known direct evidence, then provider or pattern evidence, then verification signals. A discovered email should not become send-ready just because one weak signal exists.
- Find candidate email addresses.
- Verify address quality where possible.
- Track confidence and evidence.
- Promote reliable contact data.
- Respect monthly caps, provider limits, and workspace policies.
Verification Layers
GrowthEngene email verification can use layered evidence such as syntax checks, domain and MX checks, provider intelligence, historical patterns, SMTP handshake signals, catch-all detection, and cross-reference providers.
SMTP and catch-all results are useful but should not be treated as absolute truth on their own. Ambiguous or catch-all domains should remain reviewable unless other evidence is strong.
- Format and syntax validation.
- Domain, MX, and provider-family intelligence.
- Pattern learning from known company formats.
- Provider cross-reference where configured.
- SMTP handshake and catch-all probing with throttles.
- Confidence scoring and promotion policy.
When Email Discovery Runs
Email discovery usually runs after a workflow has enough person and company evidence. For example, a LinkedIn job can resolve a company and hiring manager, or a LinkedIn post can provide poster name and company domain.
- Run discovery for contacts with name plus company/domain evidence.
- Use direct emails from posts before external discovery.
- Use Search Intelligence when person or company evidence is incomplete.
- Promote discovered emails only when confidence and policy requirements pass.
- Keep low-confidence, risky, unknown, or catch-all results in review.
Safety And Pacing
Email verification can create external traffic, so GrowthEngene uses pacing, quotas, cooldowns, worker keys, and monthly caps to avoid noisy or unsafe verification behavior.
- Respect workspace verification queue limits.
- Respect provider caps and monthly caps.
- Use same-recipient-domain pacing for verification probes.
- Throttle SMTP probing and verification source IP usage where configured.
- Keep sending SMTP separate from verification SMTP.
How Results Are Used
A verified or likely email can be promoted into contact evidence, shown in review queues, used by pipelines, or made available for campaign enrollment. Sending still depends on sender, suppression, pacing, resume, and send-mode checks.
- Store evidence and confidence with the contact.
- Expose verification state in review surfaces.
- Use best-email promotion only when policy allows.
- Do not send automatically from discovery alone unless guarded send rules also pass.
Frequently Asked Questions
Does every discovered email become send-ready?
No. Emails should meet confidence, verification, and policy requirements before being used for outreach.
Why can an email be found but not used for sending?
It may be low confidence, risky, catch-all, suppressed, unverified, below policy threshold, or blocked by sender and domain pacing checks.
Does GrowthEngene verify every email with SMTP?
No. GrowthEngene can use layered verification. SMTP is one signal and should be throttled, interpreted with catch-all awareness, and combined with other evidence.