Instantly handles sending. You decide what enters it.
Instantly is built for multi-inbox campaigns, mailbox rotation, warmup sequences, and scaled outbound operations. It does all of that well.
What it does not do is make final decisions about record quality before import. That decision belongs to you β before the list reaches the sender, while you still have the discipline to remove or segment risky addresses.
What to check before Instantly import.
Every list entering Instantly should pass a field-level check before it is imported. These are the fields that matter most.
| Field | Why it matters |
|---|---|
| The verification target β the address that enters the mailbox rotation | |
| Domain | Determines catch-all status, MX validity, and company matching |
| Source | Apollo, LinkedIn export, scraper, enrichment, manual list β each has different risk |
| Duplicate status | Instantly handles rotation, but duplicate addresses inflate your bounce exposure |
| Suppression status | Addresses that bounced or unsubscribed from previous campaigns should not re-enter |
The risk each signal type creates.
Not all records are equally risky. Understanding what each signal type does to your campaign helps you apply the right rule before import.
| Signal | Delivery behavior | Risk to Instantly campaigns |
|---|---|---|
| Invalid | Permanently rejected | Hard bounce β direct reputation damage |
| Catch-all | Domain accepts all addresses, mailbox uncertain | May deliver or bounce β inflates uncertainty |
| Role-based | Shared inbox (info@, sales@, hr@) | Technically valid, but weak as a named outreach target |
| Disposable | Temporary or low-trust address | Not a real business contact |
| Unknown | Verification result inconclusive | Should not enter high-volume rotation without review |
| Duplicate | Same address imported multiple times | Repeat sends, complaint risk |
Verify before import β not after bounce.
The right point to verify is before you import the list into Instantly. Not after the first campaign wave. Not when bounce rate starts climbing.
Import is a commitment point. Once a list is inside Instantly, campaign pressure makes it much harder to stop and remove weak records. A pre-import pass creates the right kind of friction β before the bad data becomes a running campaign.