Woodpecker handles sequence-based outreach. You decide what gets sequenced.
Woodpecker is built for cold email outreach — automated sequences, follow-up management, inbox warm-up, and multi-inbox support for SMBs and agencies. It handles the operational side of outbound: scheduling, timing, deliverability signals, and campaign management for teams that run ongoing prospecting.
What Woodpecker does not do is screen the contact records before they enter a sequence. It receives whatever is imported and executes the sequence against it. A bad record gets the full treatment — all follow-up steps, all delays, all inbox capacity — until a bounce or a manual intervention stops it.
For agencies using Woodpecker's team workspace, this risk multiplies. One client's unverified list, imported without a quality check, affects the shared sending infrastructure that serves every other client. Protecting the workspace means establishing a consistent verification standard before any list is imported, regardless of the client or the source.
Cold Email Verification Framework
This page covers one sender or workflow. The full framework explains the complete path from list source through verification, segmentation, and import into your sender.
What to check before Woodpecker import.
Woodpecker users in agency and SMB settings typically import from CSV exports, Apollo, LinkedIn, or data collected through lead generation tools. The quality of each source varies. These are the fields that matter before any record enters a Woodpecker sequence.
| Field | Why it matters |
|---|---|
| The address that receives each sequence step — the primary delivery target | |
| Domain | Determines catch-all behavior, MX validity, and whether the target company is still active |
| Source | Client-provided CSV, Apollo, LinkedIn, lead gen tool — each carries different error rates |
| Suppression status | Previously bounced or unsubscribed contacts must be excluded from new sequences |
| List age | Records older than 90 days should be re-verified — contact data decays steadily over time |
The risk each signal type creates.
Woodpecker sequences can run for days or weeks with multiple follow-up steps. An invalid or risky record is not caught immediately — it receives all configured touches before a bounce surface in campaign analytics.
| Signal | Delivery behavior | Risk to Woodpecker campaigns |
|---|---|---|
| Invalid | Permanently rejected by receiving server | Hard bounce — direct damage to the sending inbox and connected domain |
| Catch-all | Domain accepts all addresses, mailbox status uncertain | May deliver or bounce — introduces measurement noise across the sequence |
| Role-based | Shared inbox (info@, sales@, hr@) | Deliverable but weak for personalized sequence outreach targeting individuals |
| Disposable | Temporary or low-trust address | No real contact — wastes all follow-up capacity in the sequence |
| Unknown | Verification result inconclusive | Should not enter any active sequence without a deliberate review |
| Duplicate | Same address across multiple sequences or client lists | Contact receives multiple simultaneous sequences — complaint and unsubscribe risk |
Verify before import — not after bounce.
The practical moment to verify is before any record enters a Woodpecker sequence. Once contacts are inside an active sequence, removing them requires manual intervention and breaks the continuity of the campaign schedule. Identifying bad records before import is simpler and protects the sending infrastructure from the start.
Collect list from source
→ Normalize and deduplicate
→ Verify with BillionVerify
→ Apply routing decisions by signal
→ Import approved records into Woodpecker
→ Launch warmup or campaign sequence
Import is a commitment point. In Woodpecker, especially in agency workspaces, that commitment extends to the shared inbox infrastructure serving the campaign. Verifying before import means the sequence starts clean and the inboxes behind it are not absorbing bounces from records that were never deliverable.
Route each result into the right bucket.
| BillionVerify result | Action before Woodpecker import |
|---|---|
| Valid | Import into target sequence for full scheduled execution |
| Invalid | Do not import — add to client-level suppression list |
| Catch-all | Separate sequence with reduced follow-up frequency and close monitoring |
| Role-based | Separate sequence with messaging adjusted for shared inbox routing |
| Unknown | Hold for review — do not enter any active sequence without a decision |
| Risky or disposable | Do not import |
For agency workspaces, maintain suppression lists at the client level as well as the campaign level. A bounced address from one client's campaign should not be importable again under a different campaign name if the same workspace infrastructure is shared.
After the list is verified.
Once approved records are imported into Woodpecker:
- Valid addresses enter the target sequence and proceed through all scheduled follow-up steps
- Catch-all addresses run in a separate, lower-frequency sequence with limited follow-up touches
- Role-based addresses get a sequence with copy that accounts for shared inbox routing
- Invalid and disposable records are suppressed at the client level and excluded from all imports
- Unknown addresses remain in a review state until an explicit import decision is made
Instantly Email Verification
Verify before importing lists into Instantly campaigns and warmup sequences.
GMass Email Verification
Clean Google Sheets lists before GMass sends them through Gmail.
Smartlead Email Verification
Set a pre-import quality gate for high-volume Smartlead campaigns.
Lemlist Email Verification
Verify lists before multi-channel Lemlist campaigns — before enrichment becomes a liability.
Salesloft Email Verification
Apply a pre-import quality gate before records enter Salesloft sequences.
Outreach Email Verification
Verify emails before Outreach sequence enrollment to protect enterprise sender reputation.
Mailshake Email Verification
Clean lists before Mailshake campaigns — keep bounce rate low for small outbound teams.
Reply.io Email Verification
Verify emails before Reply.io sequences to prevent invalid records from entering automated workflows.
Mailmeteor Email Verification
Check Google Sheets contacts before Mailmeteor sends Gmail merge campaigns.
QuickMail Email Verification
Apply a pre-import quality gate before contacts enter QuickMail inboxes.
Saleshandy Email Verification
Verify lists before Saleshandy campaigns to protect deliverability at lower send budgets.
Klenty Email Verification
Verify emails before Klenty cadences to keep CRM-sourced contacts clean.
Close CRM Email Verification
Clean email records in Close before sequences run — protect CRM contact quality.
Yesware Email Verification
Verify lists before Gmail-based Yesware campaigns to reduce bounce exposure.
Overloop Email Verification
Apply a pre-send quality gate before contacts enter Overloop sequences.
Mixmax Email Verification
Verify emails before Mixmax Gmail sequences to prevent bounce damage.
Lavender + BillionVerify Workflow
Verify the list before Lavender helps write messages — clean data improves AI targeting.
PersistIQ Email Verification
Check lists before PersistIQ campaigns to keep SDR workflows free of invalid contacts.
Autoklose Email Verification
Verify emails before Autoklose sequences — protect automated sending from list risk.
SendBuzz Email Verification
Apply a pre-import gate before SendBuzz campaigns to keep bounce rate low at scale.
Woodpecker email verification common questions.
1. Does Woodpecker have built-in email verification?
Woodpecker provides some deliverability features and sending controls within the platform. A dedicated pre-import verification pass with BillionVerify applies a consistent quality threshold before any record enters a sequence — independent of what the sender itself provides. For agency teams handling multiple client lists with different origins, an external verification standard ensures quality decisions are made before any list reaches the shared sending environment.
2. Should I verify before or after warmup in Woodpecker?
Before. Warmup builds the sending reputation of connected inboxes. It does not validate whether specific contact records are deliverable. Running sequences with unverified records during warmup introduces bounce signals that work against the reputation improvement warmup is designed to build. In agency workspaces where multiple clients share infrastructure, one bad list during warmup can affect the warmup trajectory for all connected accounts.
3. What should I do with catch-all contacts in Woodpecker?
Assign them to a separate sequence with reduced follow-up frequency and do not escalate them to the same volume as confirmed valid contacts. Catch-all domains accept all mail at the server level, but individual addresses within them may not route to active inboxes. Monitoring catch-all delivery in isolation prevents them from distorting the performance data for your main campaign sequence.
4. How should agencies handle client lists before importing into Woodpecker?
Treat every client-provided list as unverified by default. Clients frequently deliver exports from CRM tools, Apollo, or databases without applying any quality check. Establishing a standard verification step before import protects the agency workspace and gives clients accurate performance data. Any exceptions should require an explicit sign-off rather than a last-minute workaround before launch.
5. Can verification prevent all bounces in Woodpecker sequences?
No. Verification removes bounces from permanently invalid addresses and reduces risk from disposable and risky record types. Temporary delivery failures, server-side quota limits, and catch-all addresses that become inactive after verification cannot be predicted or prevented by any verification service. The goal is to eliminate the controllable bounce risk before sequences run — not to guarantee zero bounces across all follow-up steps.