Build a sequence, point it at a pool of mailboxes, and let it run. NuMail rotates every send across your inboxes, schedules each touch for the lead's local morning, and runs the A/B test for you, promoting the winning variant the moment it crosses significance.
A sequence is an ordered list of steps. Each step has a delay, a subject, a body, and, if you want, competing variants. Personalize with merge fields; the engine handles the rest.
Drag steps into order, set the gap between each, and write your copy with {{first_name}}-style merge fields. Follow-ups thread onto the original send, so they land as Re: in the same conversation.
Every campaign ties the same primitives into one running system, so you set it up once and it keeps optimizing itself.
Order multi-step touches, set delays in hours or days, thread follow-ups onto the original send, and auto-stop a lead the moment they reply.
up to 12 stepsAssign a pool, not a single inbox. Sends rotate across every healthy mailbox, respecting each one's daily cap, warmup tier, and sending window.
volume without burnoutRun variants on subject or body. NuMail tracks reply lift, computes significance, and promotes the winner automatically once the threshold is reached.
no manual callEach touch fires in the lead's own local morning, not yours. Set send windows and working days per campaign; weekends and holidays are skipped.
their timezoneImport a CSV with column-mapping suggestions, de-duplicated against the leads you already have. Webhooks push every send, open, click and classified reply to whatever you keep your pipeline in.
CSV + webhooksReal-time funnel from enrolled → sent → opened → replied → booked, broken out per step, per variant, and per mailbox. Export or pull it from the API.
per step · per mailboxSending a million emails a month from one inbox gets you blocked. NuMail spreads the load across a pool, and never asks a mailbox to do more than it safely can.
Point a campaign at a pool of mailboxes and the engine round-robins every send across them. It reads each mailbox's daily cap, current warmup tier, and sending window, and routes around any inbox that's paused, throttled, or showing a reputation dip.
Add a per-campaign throttle on top to pace overall volume, and a suppression list so a domain you've already contacted (or unsubscribed) is never touched again, across every campaign in the workspace.
Most tools split traffic and leave you eyeballing two numbers. NuMail runs the test properly, and acts on the result automatically.
Add variants to any step. The engine splits enrollment evenly, measures reply rate as the primary metric, and runs a continuous significance test as data lands.
ab_winner.declared webhook so your stack knowssubject_aThe difference isn't features on a list; it's whether the system runs itself once it's live, or quietly waits on you.
We pointed one campaign at a 14-mailbox pool and turned auto-promote on. Two weeks later the engine had already swapped in the better subject line. We'd never have caught the lift that fast by hand.
Build a sequence, assign a pool, turn on auto-promote. NuMail handles rotation, scheduling, throttling, and the A/B while you watch the replies land.