The problem this solves
A campaign is only as safe as its worst address. One in twenty invalid emails is enough to move a sending domain onto the wrong side of a mailbox provider's thresholds, and the damage lands on every campaign that shares the domain, including the ones that were built carefully. The leads were verified when they were found, perhaps, but lists age between building and sending.
The other silent failure is overlap. The same contact loaded into two campaigns receives two sequences, replies to one with irritation, and unsubscribes from both. Deduping against every running campaign before a new one starts is the kind of check nobody does by hand because it means exporting all of them.
A pre-send pass inside Instantly handles both. Every lead is verified fresh, the risky and invalid ones are removed, overlaps with other campaigns are resolved, and the campaign starts with a report of what was taken out and why, so the numbers it produces later can be trusted.
How the mission runs
- Read the campaign's leads. The Lead Verification Agent reads the leads in Instantly campaign <name>, which is still paused, along with their custom fields, so nothing is lost when leads are removed or re-added.
- Verify every address. Verification runs on each lead and labels it deliverable, catch-all, risky or invalid. Invalid and risky leads are marked for removal; catch-all leads are kept or removed according to the rule you set, with the default being to keep them flagged.
- Dedupe against other campaigns. Every lead is checked against the leads in your other active Instantly campaigns. Contacts already in a running sequence are removed from the new campaign, and contacts at the same company are flagged so you can decide whether two people at one account should hear from you at once.
- Apply the removals and report. The removals are applied to the campaign as a reviewed batch, and the report lists every lead removed with the reason - invalid, risky, duplicate, already in campaign X - plus the counts before and after, so the campaign can be started with confidence.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
Instantly campaign <name> cleaned before it starts: invalid and risky leads removed, catch-all leads handled by your rule, contacts already in other running campaigns removed, and a report listing every removal with its reason and the before-and-after counts. The campaign stays paused; you start it once the report reads the way you expect.
Make it yours
- Run the same pass against a Lemlist or Apollo campaign.
- Add a suppression check against your customer list and do-not-contact domains in the same run.
- Schedule the pass to re-verify long-running campaigns monthly and remove addresses that have gone stale.
- Add a bounce-rate threshold so the pass warns you if the remaining list is still riskier than your domain can absorb.
Frequently asked questions
Will it start the campaign?
No. The campaign stays paused after the pass; starting it is yours to do once you have read the report.
What is the right rule for catch-all addresses?
Teams with strong domain reputation often keep them; teams warming a new domain remove them. State the rule in the prompt and the report shows how many leads it affected.
Does dedupe look across sending accounts?
Yes. Every active campaign in the connected Instantly workspace is checked, regardless of which mailbox sends it.
Can it re-add leads that were removed by mistake?
Yes. Removed leads are kept in the report with their fields, and any of them can be restored to the campaign from the thread.