Today
—
Warmup ramp
—
Reputation
The nightly gate pauses the warmup on any breach and only steps the cap up on a clean day.
Lifetime
Engagement
Opens/clicks are split real vs bot (corporate scanners & prefetch). Tracking is OFF during warmup — turn it on in Config only to A/B the placement cost. Never uses awstrack.me.
Controls
With autopilot OFF, enabling sending does not blast the list — mail leaves only via a manual/API/GHL trigger. Turn autopilot ON to start the paced warmup of the whole queue.
Daily volume
Per-domain today
Provider mix (pending / sent)
Biggest recipient domains
Preview
Subject
Text part
HTML part (rendered)
Warmup configuration
Everything paced or gated lives here: schedule window, ramp steps, per-domain cap, thresholds and the email template. Saved JSON is schema-validated — an unknown key is rejected rather than ignored — and takes effect on the next tick (within 30s).
Preflight
Checks the things that silently ruin a warmup: identity + DKIM, the config set's engagement tracking (an open pixel and awstrack.me link wrapping come back if it is ever enabled), the event queue, GHL write-back, and whether the template renders without holes.
Send a test email
Real SES send through the live config set — use it for seed lists and mail-tester. Uses the default template. Counts toward today's cap.
Send to a contact
The on-demand send GHL and the frontend use — resolves a recipient by email (or paste a recipient/GHL contact id) and sends one real email regardless of autopilot. A previously-unknown contact is auto-registered so bounce/complaint tracking works. If it's a new contact using the default template, paste a body override below (the template needs a name/company, which a new contact may lack).
Validate an address
ZeroBounce single-address check — the validator proven reliable for this list.