Contact Enrichment

How enrichment is doing across the scored cohort — and where you configure and run it (Set-up & run). Emails come from three places: on-file HubSpot seeds (already in NAVIRA's CRM), Apollo (decision-maker discovery + reveal), and BetterContact's verified-email waterfall (the paid fallback we only spend on Apollo's misses). Per-row and top-N enrichment also live in the Review Queue.
Apollo reveal attempts (all-time)
BetterContact credits left
Enriched
Deliverable (verified)

Apollo is the primary lookup — 1 reveal ≈ 1 Apollo credit (it's a subscription, so $ is fixed monthly; see Apollo billing). BetterContact is the pay-per-verified fallback on Apollo's misses, drawn from the balance above. Reveals are counted going forward — enrichments from before this counter was added (e.g. contacts already in the queue) aren't included; Apollo's API exposes no credit total, so this is our own tally.

Deliverability breakdown

Of the contacts enriched so far, how many returned a send-safe email. BetterContact SMTP-verifies each address — verified (deliverable) means the mailbox itself accepts mail (not just that the domain exists), and is safe to approve by default; catch-all-safe is a domain that accepts everything so the exact mailbox can't be confirmed (usable when "require verified" is off); risky is never sent.

Loading…
Where the emails came from

Each saved email traces to one origin: a HubSpot on-file seed (warm, but never SMTP-verified), a direct Apollo reveal, or BetterContact — which cascades ~20 data providers and stops at the first SMTP-verified hit (the row shows the underlying provider it landed on). Because BetterContact is the paid fallback we only run on Apollo's misses, its share grows as the cohort moves past the seeded and Apollo-covered brands.

Loading…
Recently enriched

The latest contacts written back to the review queue.

BrandContactEmailStatusSourceWhen
Loading…
→ Go to the Review Queue to enrich brands and approve leads.