Product / Campaigns

Sequences with variants. A loser is paused for you, never rewritten.

Multi-step sequences, each step with variants. Once a week the variants are compared and the one that is losing is paused so a person can look at it. That is the single scheduled job in the product permitted to write anything, and pausing is all it can do.

Step 1, two variants — example data
VARIANT AActive
Lead times on the taller panels
Dana — you are specifying for two builds in Q1. Is the constraint the schedule or the spec? That changes which option I’d point you at.
Sent
412
Replied
19
Reply rate
4.6%
VARIANT BPaused for review
Quick question about your Q1 builds
Hi Dana, hope you’re well. I wanted to reach out about your upcoming projects and see if there might be a fit…
Sent
408
Replied
6
Reply rate
1.5%

What the optimizer did: paused B and left a note. What it did not do: edit B, write a C, or move A’s budget. You decide what happens next.

Settings

The controls that keep a campaign inside the lines.

Sending window
Mon–Fri 9:00–17:00, in the client’s zone
Windows are set in whole hours, and the console says so rather than implying minutes.
Stop on reply
On by default
A reply ends the sequence for that person. The next message is yours, from the queue.
Company limit
People per company per campaign
So five people at one firm do not get the same message in the same week.
Risky addresses
Excluded unless you allow them
Catch-all and unverifiable addresses are held out of the send by default.
Do-not-contact list
Yours, plus every unsubscribe
Unsubscribes are honoured even if you never uploaded a list.
CC / BCC
Per campaign
Copy a colleague or a CRM address on what goes out.
Results

People, not messages. Genuine, not automated.

A reply rate that counts every inbound message counts every out-of-office and counts one keen person three times. It reads about twice the truth. This product counts one distinct person with at least one genuine reply, and shows the breakdown beside it.

NumberHow it is countedWhen it is a dash
People contactedDistinct leads with at least one send.Never; sends are logged locally.
People repliedDistinct leads with a genuine inbound: not out-of-office, not unsubscribe.When the inbound sync has not run for that campaign.
AutomatedOut-of-office and similar, shown as their own count.Same as above.
Reply ratePeople replied over people contacted, per campaign.When either side is unknown. It is not computed from a partial pair.
Open rateOnly when tracking is on.Absent on purpose when tracking is off. An empty column beats a made-up one.
BouncesNot shown as a message count.Always: a bounce is a delivery report, not an inbound message, so that count would always have been a fabricated zero.
Launch

A person launches every campaign.

Launch, pause and resume are clicks. Lanes derived from a campaign you launched — the resume after an out-of-office, a copy addressed to a referred contact — run inside that launch, and only while five guards hold: the parent is still active, the operation is supported, the lane is one the product itself created and recorded, the per-lead guards are unchanged, and the workspace has not opted out. Read more on the security page.

Run the sequence. Keep the decisions.

Variants, windows, limits and a weekly pause you can overrule.