RevStack cold email dashboard: Instantly fleet campaign stats and the earlier paused GHL sequence, snapshot from Jul 30 2026.

RevStack cold email — snapshot

Pulled live from Instantly, Jul 30 2026 ~3:58pm CT

Not auto-refreshing. There's no packaged Instantly MCP connector, so this is a point-in-time snapshot read via Claude in Chrome, not a live feed. Ask Claude to "refresh the dashboard" any time you want current numbers pulled again.

Instantly fleet — "RevStack Contractor Cold v1" Active

Total sent

640

all-time, campaign total

Replied

10

1.94% reply rate

Bounced

4

0.63% — well under the 2% gate

Opportunities

0

$0 booked so far

Inboxes healthy

32 / 32

99–100% health scores

Step 1 funnel (first touch, 515 sent — 4wk window)

Bounce reasons

ReasonCountShare
Invalid recipient375%
Policy blocked125%

All 4 are hard bounces. 0 soft, 0 unknown. Open/click tracking is intentionally disabled (protects deliverability).

Inbox fleet health (32 inboxes, warm-up started Jul 13 — 17 days in)

Every inbox is sending 5 of a 30/day cap today, all at 99–100% health, 138–140 warm-up emails exchanged each. No red or disconnected inboxes. Names spread across 16 domains (tryrevstack.com, joinrevstack.com, revstackco.com, and others), two mailbox-name variants each (kevin@ / kevin.duffy@).

Earlier attempt — GHL-native sequence Paused since Jul 10

Before the Instantly fleet, cold email ran straight from kevin@lc.revstackapp.com through GHL. 224 emails sent to 224 distinct contacts, Jul 6–8 (touch 1 only — no follow-ups ever went out). A seed placement test on Jul 10 came back 3/3 landing in spam, so real-prospect sending was paused and the fleet above replaced it entirely. This domain is not currently sending cold prospects.

Known open issue: a cold-reply classifier defect is still unresolved as of today's heartbeat — some replies may not be tagged/routed correctly in GHL. The Instantly numbers above come straight from Instantly itself, so they're not affected. If a GHL-side reply dashboard gets added later, treat its reply counts as unverified until that defect is fixed.