Voila Norbert finds email addresses and scores them. Finder confidence reflects discovery accuracy, not inbox status.
Voila Norbert is an email finder that helps outbound teams locate professional email addresses for specific people at specific companies. It takes a name and domain as inputs, discovers the most likely email address for that contact, and assigns a confidence score based on how well the result matches expected patterns and available signals.
Voila Norbert's confidence score measures how reliable the discovery was — how consistently that address appears in the data available to the finder at the time of the query. A high score means the finder is confident in the pattern it used. It does not confirm that the mailbox is currently active, that the employee is still at the company, or that the domain will accept email to that address today. Address validity changes over time; confidence scores do not update to reflect those changes.
BillionVerify provides what confidence scoring cannot: a real-time SMTP check that confirms whether the specific mailbox will accept a message today, along with catch-all domain detection and role-based inbox identification. Voila Norbert answers "is this the right email address for this person?" — BillionVerify answers "will this email deliver right now?"
B2B Leads Verification Framework
This page covers one database or workflow. The full framework explains the complete path from B2B data source through verification, segmentation, and routing into your CRM or sender.
What Voila Norbert's confidence score actually means.
| Voila Norbert confidence level | What it means | What it does not mean |
|---|---|---|
| High (90%+) | Pattern matches the most common format for this domain | Mailbox is currently active and accepting email |
| Medium (70–89%) | Pattern likely matches, some uncertainty in the data | Address has not changed since Voila Norbert found it |
| Low (below 70%) | Pattern match is less reliable or signals are weaker | Mailbox exists at all |
| Catch-all domain | Domain accepts all incoming email at server level | Individual mailbox is active or monitored |
The confidence score is a proxy for discovery quality, not a substitute for deliverability testing. Teams that treat a high confidence score as send-ready skip the step that actually confirms whether the mailbox will accept a message. Even a confidence score of 97% can include addresses pointing to employees who left, mailboxes that were deprovisioned, or catch-all domains where individual delivery is unconfirmed.
The specific risks in a Voila Norbert export.
| Risk | Source | Impact |
|---|---|---|
| High-confidence stale addresses | Employee left company after Voila Norbert's last data point | Hard bounce despite high score |
| Pattern-correct invalid mailboxes | Format matches domain convention, but mailbox was removed or never existed | Hard bounce on an address that looks valid |
| Catch-all false positives | Domain accepts everything, individual inbox may be unmanned or filtered | No bounce signal, email silently discarded |
| Role-based inboxes | info@, hello@, contact@ matching common domain patterns | Shared inbox, no named individual |
| Outdated employer associations | Company name and domain do not reflect a recent rebrand or acquisition | Bounce or delivery to a defunct domain |
| Duplicate finds | Same address discovered across multiple finder queries | Repeat sends to the same contact |
Verify Voila Norbert exports before import.
Verification should happen after every Voila Norbert export and before any record enters a CRM, sender, or sequence. A plausible address with a high confidence score is a good starting point — it is not a send-ready record. Run BillionVerify on the full export first, route results by category, then import only the records that pass.
The verification step does not negate the value of Voila Norbert's confidence score — it builds on it. A high confidence score combined with a BillionVerify valid result gives you the strongest signal available before sending. A high confidence score without verification still leaves the deliverability question unanswered.
Export from Voila Norbert
→ Normalize and deduplicate
→ Remove previously suppressed addresses
→ Verify with BillionVerify
→ Valid → import into CRM or sender
→ Catch-all → separate segment, lower volume
→ Role-based → separate campaign, shared-inbox messaging
→ Invalid, disposable → suppression file
→ Unknown → review queue
Route each result.
| BillionVerify result | Action for Voila Norbert exports |
|---|---|
| Valid | Import into CRM or outbound sequence |
| Invalid | Do not import — add to suppression file |
| Catch-all | Separate lower-volume segment, monitor deliverability closely |
| Role-based | Separate campaign written for shared-inbox context |
| Unknown | Review queue — exclude from high-volume sequences |
| Risky or disposable | Do not import |
After verification — where records go.
- Valid: import into CRM or sender, standard outbound sequence
- Catch-all: lower-volume segment, separate from main campaign rotation
- Role-based: separate campaign, messaging written for shared-inbox audiences — avoid personal-name opening lines
- Invalid and disposable: suppression file, do not re-import even if the address reappears in a future Voila Norbert search
- Unknown: review queue, decision required before any send — exclude from automated sequences
What verification adds to a Voila Norbert workflow.
Voila Norbert's interface is straightforward: input a name and company, get back an email address with a confidence score. That simplicity is part of its appeal for lean outbound teams. The verification step extends that workflow with a quality gate that the finder itself cannot provide.
The practical value of verifying Voila Norbert results is that it separates addresses where deliverability is confirmed from addresses where it is merely probable. For small lists where each record carries significant personalization investment, this distinction matters. Spending copywriting time and outreach effort on an address that will bounce is not just wasted cost — it also means the right person never receives the message.
For larger Voila Norbert exports, the aggregate effect of unverified addresses is visible in campaign metrics. A list with an average confidence score of 85% might still contain 10–15% invalid or catch-all addresses. Those addresses drag down reply rates, inflate bounce rates, and make it harder to evaluate whether the campaign's targeting and messaging are working.
Common data quality issues across Voila Norbert exports.
Name-and-domain inputs that rely on LinkedIn profile data to determine the correct person's name carry a secondary staleness risk: if the name or employer in the input is outdated, the resulting email address may be correct in format but wrong in target. Verify the list but also review whether the input data used to generate it is current.
Rebranded or acquired companies are a specific failure mode for Voila Norbert exports. If a company was acquired and its domain merged or deprecated, addresses from the old domain may return high confidence scores based on historical pattern data while the domain itself is no longer active. Check for recent acquisitions in your target account list before treating Voila Norbert results as final.
Bulk Voila Norbert runs across large prospect lists tend to surface more catch-all results than single-contact searches. Larger companies and mid-market accounts often use catch-all configurations. The routing guidance in the table above handles this — catch-all addresses go to a separate segment rather than being treated as invalid.
Lists from previous campaigns in Voila Norbert's saved results do not update automatically when the underlying email addresses become invalid. Re-verify any Voila Norbert export older than 90 days before reusing it.
When to run verification relative to a Voila Norbert export.
- Run Voila Norbert searches — input names and domains, export results
- Optional: filter by confidence threshold — remove very low confidence results if needed to reduce list size before verification
- Deduplicate — remove duplicate email addresses and contacts already in your CRM
- Remove suppressed addresses — apply your global suppression file
- Verify with BillionVerify — run the cleaned export through bulk verification
- Route results — valid to CRM, catch-all to separate segment, invalid to suppression
- Import verified records — only confirmed deliverable addresses enter the sender
- Update suppression file — add invalid and disposable results from the verification run
Voila Norbert in a complete email finder workflow.
Voila Norbert handles name-and-domain based email discovery with confidence scoring. BillionVerify handles the final deliverability gate before discovered addresses enter a sender or CRM. Voila Norbert answers the discovery question; BillionVerify answers the deliverability question. Both answers are needed before any outreach makes sense.
For lean outbound teams using Voila Norbert as their primary finder, the verification step completes the workflow at the point where it matters most: immediately before a contact record becomes active in outreach. Confidence scoring is useful for prioritizing or filtering the list. Verification is what determines whether the addresses on that list will actually deliver.
For a broader comparison of finder-based sourcing approaches and their verification requirements, see email finder workflow.
Apollo Email Verification
Verify Apollo exports before they enter your CRM or sender — remove invalid and catch-all addresses.
Hunter Email Verification
Understand what Hunter verification covers and when to run an independent check.
ZoomInfo Email Verification
Verify ZoomInfo contacts before import — confidence scores are not the same as deliverability.
RocketReach Email Verification
Verify RocketReach exports before sending — catch-all and stale records need a final check.
Lusha Email Verification
Verify Lusha contacts before import — especially for EMEA and LinkedIn-sourced records.
Seamless.AI Email Verification
AI-discovered addresses still need verification — confirm deliverability before import.
Snov.io Email Verification
Verify Snov.io finder output before sending — pattern-based discovery produces mixed-quality results.
UpLead Email Verification
Verify UpLead contacts before import — small team exports need the same verification gate.
Cognism Email Verification
Verify Cognism exports before sending — enterprise EMEA data still requires a deliverability check.
GetProspect Email Verification
Verify GetProspect output before import — LinkedIn-sourced contacts need a final deliverability gate.
Adapt.io Email Verification
Verify Adapt.io contacts before sending — database exports require an independent verification pass.
Lead411 Email Verification
Verify Lead411 contacts before import — intent signals do not guarantee email deliverability.
ContactOut Email Verification
Verify ContactOut exports — LinkedIn-sourced emails need a final deliverability check before outreach.
SalesQL Email Verification
Verify SalesQL output before sending — LinkedIn finder results need a final verification gate.
Wiza Email Verification
Verify Wiza exports — LinkedIn Sales Navigator workflow output requires a deliverability check.
Findymail Email Verification
Verify Findymail output before import — confidence scores are not the same as deliverability.
Kaspr Email Verification
Verify Kaspr contacts before sending — LinkedIn-sourced emails require a final quality check.
Skrapp Email Verification
Verify Skrapp output before import — pattern-based email discovery requires a verification pass.
AeroLeads Email Verification
Verify AeroLeads exports before import — mixed-source data requires a final deliverability gate.
Datanyze Email Verification
Verify Datanyze contacts before sending — technographic signals do not guarantee deliverability.
Dropcontact Email Verification
Verify Dropcontact enriched data — enrichment accuracy is separate from current deliverability.
SignalHire Email Verification
Verify SignalHire contacts before sending — sourced data needs a final deliverability check.
Prospect.io Email Verification
Verify Prospect.io contacts before import — automation platform data needs a separate verification pass.
Saleshandy Leads Verification
Verify Saleshandy lead data before sending — platform-sourced contacts need a final quality check.
Clearbit Enrichment Verification
Verify Clearbit enriched emails before sending — enrichment signals are not SMTP deliverability.
Voila Norbert email verification common questions.
1. Does Voila Norbert's confidence score replace independent verification?
No. Voila Norbert's confidence score measures how well the address pattern matches expected signals at the time of discovery — it is a discovery quality signal, not a deliverability signal. A 90% confidence score means the pattern is very consistent; it does not mean the mailbox is active today. Run BillionVerify to get a current SMTP-level answer.
2. Should I filter by confidence score before verifying?
You can use the confidence score to prioritize or reduce list size before running verification. However, even high-confidence addresses can include stale records, catch-all domains, and role-based inboxes. Use the confidence score as a pre-filter if needed, then verify the resulting list before any send.
3. How should I handle catch-all addresses from a Voila Norbert export?
Route them to a separate, lower-volume segment. Catch-all domains accept all email at the server level, which means individual mailbox status cannot be confirmed for those addresses. Some catch-all addresses will deliver; many will not. Keeping them separate from confirmed valid addresses protects your sender reputation.
4. Should I re-verify a Voila Norbert list from a previous campaign?
Yes. Voila Norbert exports older than 90 days should go through another verification pass before reuse. Confidence scores do not update when employees leave, when companies change their email format, or when domains reconfigure their mail servers. An address that was deliverable previously may not be now.
5. What export format from Voila Norbert works best with BillionVerify?
Export as CSV from Voila Norbert with the email column included. BillionVerify accepts standard CSV files without special formatting. A standard Voila Norbert finder export with the email field is ready to verify immediately.
6. How does Voila Norbert compare to other email finders for verification purposes?
Voila Norbert uses the same fundamental approach as most email finders: pattern matching against employer domain data. The verification requirement is the same regardless of which finder you use. The confidence score labels differ between tools, but the underlying limitation is identical: pattern confidence is not deliverability confirmation. See B2B database vs email finder for a comparison of how finder-based and database-based contact sourcing differ in their verification needs.
7. What should I do if a large portion of my Voila Norbert results come back as catch-all?
A high proportion of catch-all results usually means your target accounts use catch-all mail server configurations — this is common in certain industries and company sizes. Route all catch-all addresses to a separate, lower-volume segment and test that segment at small scale before committing it to a full campaign. If reply rates and bounce rates are acceptable from the test send, you can scale the catch-all segment carefully. If they are not, treat the catch-all segment like an invalid segment for campaign purposes.
8. Does Voila Norbert's Verify feature eliminate the need for BillionVerify?
Voila Norbert offers a separate verification product alongside its finder. That product checks addresses against SMTP and availability signals. If you are already running addresses through Voila Norbert's own verification layer, you have already performed a check similar to what BillionVerify provides. The key question is how recently that check was performed and whether the results are current. If the verification was done at discovery time rather than immediately before sending, a fresh BillionVerify pass before import confirms that nothing has changed in the intervening period.
9. How does Voila Norbert perform for niche industries with uncommon email formats?
In industries where companies use non-standard email formats — hyphenated names, department-prefix formats, or custom conventions — Voila Norbert's pattern matching may produce lower confidence scores and a higher proportion of incorrect addresses. For niche industry exports, expect a higher invalid rate in your BillionVerify results and verify accordingly. The catch-all routing step is particularly important for these exports, since some niche-industry domains use catch-all configurations as a workaround for complex email structures.
10. What is the relationship between Voila Norbert's enrichment API and verification?
Voila Norbert's API allows teams to look up email addresses programmatically. When the API is used in an automated enrichment workflow, the resulting addresses should still go through a verification pass before they are used in outreach. API-sourced results carry the same pattern-matching limitations as UI-sourced results. The automation that makes the API valuable also makes it easy to accumulate large numbers of unverified addresses quickly — which is exactly when a pre-send verification gate is most important. See email finder workflow for guidance on integrating verification into automated enrichment workflows.