Send campaigns and protect your domain
Runner coordinates campaigns, journeys, sending windows, pacing and each mailbox's daily cap while handling opt-outs and bounces in the background.
Built into Runner
- One teammate gives the go-ahead before anything goes out
- Sending windows, pacing and a daily cap on each mailbox
- Opt-outs and bounces handled for you
- Timed multi-step follow-up, in the journey engine
Worth knowing
Live sending ships off for your organization and for each product, and an admin turns each one on, so your team chooses when automation begins. A platform switch sits above both, and while any of the three is off no campaign email leaves.
Your team sets the sending limits once, and every send is held to them
Most damage to a sending domain is a volume decision nobody meant to make. Runner turns those decisions into settings a product keeps: the days and hours it may send, read in the timezone you choose, a minimum gap between sends from the same mailbox, and a ceiling on how many new people it contacts in a day.
Each mailbox in the product's sending pool has its own daily cap. The next send leaves from the mailbox with the most room left, so volume spreads across the pool, and when no mailbox has room the send is refused with the reason named rather than switching to an address nobody added.
One campaign can follow the product's schedule or set its own days and hours. Whatever it leaves blank keeps the product's value, so tightening one limit never quietly drops another.
A go-ahead covers the exact email it approved
Sending a campaign waits for an approval. The request an approver sees carries the subject, the body and the audience size, and deliberately no list of addresses, so approving a send never copies your contacts into the approval record.
Edit the subject, change the body or grow the audience afterwards, and the send becomes a new request with no approvals on it. An approval is spent once, so a second click on send finds it already used.
Follow-up keeps its promises for as long as a journey runs
Timed multi-step follow-up lives in the journey engine, and every email it sends goes through the same campaign checks, one contact at a time. A journey step only ever mails the contact that step is acting on. It never widens to the rest of the campaign's audience.
Each contact stays on the version of the journey they enrolled on, so publishing an edit never moves someone already partway through. Pausing a journey freezes everyone in it. A journey that loops back to a step with no wait in between stops, rather than mailing in circles. And a step interrupted by a crash is never retried, because a missed email is a better failure than a duplicate one.
Picture this
Northwind rewrites step three of its onboarding journey on a Wednesday. Everyone who enrolled on Monday finishes the version they started, whatever step three says now.
Questions buyers ask
Can a cold campaign go out outside our sending hours?
No. Outside a product's schedule, only mail with a transactional purpose may send, such as support, security and legal messages, and only when the product or that campaign is set to allow it. A marketing, sales or research campaign stays inside the window whatever the setting says, because the answer is worked out from the campaign's purpose at send time.
Does Runner warm up a new mailbox?
Runner enforces the warm-up your team sets. Each mailbox in a product's sending pool has a daily cap that every send counts against, and your team raises that cap as the mailbox builds a history, so however large the audience, a new mailbox sends no more than its number.
What happens when an address hard-bounces or someone marks us as spam?
The address goes on your organization's opt-out list, and no product in the organization mails it again, transactional messages included. A soft bounce, such as a full inbox, leaves the address alone.
Who can approve a campaign send?
An owner or an admin, of the product or of the organization. Those are the only roles the approval accepts, and the approval is recorded against the person who gave it.
What pauses sending if deliveries start failing?
The product pauses itself. When its recent sends fail at a high rate, sending for that product stops and each attempt says why, and a single bounce never trips it. Your team can also pause one campaign, one product or the whole organization by hand.
Is live sending on from the start?
No. Live sending ships off, so your team chooses when automation begins. An admin turns it on, and switching it off again holds every later send, with no release and no redeploy.
Use what already works
Runner runs the campaign and records the outcome. A campaign goes out from a sending identity Runner's team configures, and your DNS stays with whoever runs it today.
How teams often buy this job
Usually bought as Outreach or Smartlead.
OutreachSmartlead
Trademarks of their owners. No affiliation or endorsement.