Three outreach tools, one health grid — so a dead sender can't hide
You connect a sending account. It warms up. Weeks later, the replies dry up.
Here is what usually happened. The warmup paused itself, because the domain kept failing — which is the correct call. But it does not switch itself back on. And from the outside, a paused warmup looks exactly like a working one.
That blind spot is why I built the outreach surface in SpiderMail™.
Connect the tool you already use
SpiderMail holds brand-scoped connections to three cold-email platforms: Smartlead, lemlist and Instantly. You connect an account once. SpiderMail reads the sending accounts behind it and keeps them in sync.
Nothing about your sending moves. Campaigns keep running where they run. What changes is that you get one place to look.
Every sender in one grid
Once a connection is live, you get a health view across every sending account:
which accounts exist, and which local mailbox each one matches
whether warmup is on — per account, not per tool
health score, plus sent, inbox, spam, bounce and reply counts over 24 hours and 7 days
a warmup trend, so you read direction instead of a single day
Three tools, one grid. That is the whole point.
Push verified leads into a campaign
The other half joins lead generation to outreach. A SpiderIQ™ campaign's verified leads push straight into a Smartlead campaign you pick.
Three things make that safe to run twice. The push is idempotent, so nobody gets added again. It is quota-aware — if the push would blow past the account's lead cap it stops and says so, and you can pass a limit to trim to the headroom instead. And it is reversible: remove leads and the credits come back.
The number that changed how I run this
You can filter that push. Two filters are opt-in: send only leads carrying a VayaPin™ pin, or only leads carrying an SEO article.
I measured which one actually qualifies leads. Across 52 restaurant lead campaigns — 9,322 verified leads, measured 9 August 2026 — 64.2% carried a pin and 18.8% carried an SEO article. The pin filter qualified more leads in 32 of those 52 campaigns.
So for pin-centric outreach, use the pin filter. The SEO filter is far narrower than it looks. Measure your own campaigns before you assume the same split — you can always optimize once you have a number.
What this does not do
Be clear about this part. It saves you a bad afternoon.
Deliverability failures usually are not a SpiderMail problem, and this surface reports them rather than fixing them. Two failures look alike and have different owners. A domain_does_not_exist bounce is DNS — fix the zone. A 553 Relaying disallowed while DNS is healthy is your mail host blocking the domain, and the fix is re-verifying ownership there. Inbound mail keeps working through that one, which is exactly why it hides.
One more, learned the hard way: an SMTP probe that stops before the DATA stage returns a clean 250 even when the domain is send-blocked. If you want to know whether a sender can really send, send a real message.
Nothing here is a deliverability promise. It is designed to show you what your providers already know, in one place, early enough to act on.
For your agents
The whole surface is in the mail skill — twelve methods, reachable from the CLI and over MCP. Your agent can list connections, sync a provider, read health for one sender or the whole brand, and run or reverse a push.
Start here
Connect a provider, then read the manual page: Outreach & Warmup.