Getting in
A cadence tool is judged on the day it goes wrong.
Somebody replies and gets three more emails. Somebody edits a live sequence and fifty people in flight silently skip a step. A rep opens their queue on a Monday and finds Saturday's work was hidden from them until nine.
Each of those is a decision taken once, in the right direction or the wrong one.
The day
The queue is a list of things to do, not a record of things that happened.
Five kinds of step — a call to make, an email, a task, a wait, and a branch. The default for an email step is that the rep sends it, with the draft prepared. Automatic sending is available and is the exception, not the default.
Which means the queue is a working surface: the rows are actions, each with the person, the step they are on, and the thing to press.
- Marguerite OkaforCall · Step 2 of 6Dial
- Tobias LindqvistEmail · Step 1 of 4 · you send itOpen draft
- Vestra FreightTask · Step 4 of 6 · check the tender portalMark done
- It stops when somebody replies —
And when a meeting gets booked, and when the deal is won or lost — each switchable per sequence. Nobody has to notice; nobody sends a fourth email to somebody who already said yes.
- Quiet hours do not apply to your own to-do list —
Waits and automatic steps respect the working window. Manual steps do not, and the reason is written into the code: deferring them once hid fresh enrollments from reps until Monday morning. Somebody working a Saturday can see their queue.
- A failed send leaves the row where it is —
Visible, to be fixed by hand — rather than being skipped past and quietly lost.
- One live enrollment per person per sequence —
A second is refused with a readable message. A completed or cancelled one does not block re-enrolling them later.
- Enrolling a batch tells you who was skipped, and why —
Per person, not a count.
Editing
A published sequence cannot have its steps rearranged, and that is the feature.
Add, remove or reorder a step on a live sequence and it is refused.
Because an enrollment in flight holds a position. Move a step underneath fifty people mid-cadence and you have silently changed what happens next for every one of them — some skip a step, some repeat one, and nobody finds out.
So structural changes happen on a draft. Content changes to a step are a different matter and are not blocked.
- Publishing an empty sequence is refused —
Which sounds obvious and is the sort of thing that otherwise ships.
- Archiving cancels every live enrollment first —
So it cannot strand people part-way through a cadence that no longer exists.
- Each kind of step is validated for its own shape —
A wait needs a duration. An email needs a subject and a body. A task needs a title. Each refusal names the specific thing that is missing.
- Every step taken is written down permanently —
Executed, snoozed, skipped, branched, paused automatically, completed, cancelled — keyed to the position rather than the step, so the history survives a step being deleted afterwards.
›Is this marketing email?
No, and the distinction is deliberate. These are rep-owned, one-to-one cadences. There is no unsubscribe header, no open or click tracking, no bounce handling and no delivery tracking past the handoff. For anything resembling a campaign, use the marketing side of the platform, which has suppression and consent enforcement built for it.
›Do branch steps evaluate a condition?
Not today. A branch is accepted, validated and stored, and the sweep advances past it. Build cadences that do not depend on branching.
›Do task steps create real tasks?
Not today. A task step appears in the sequence queue as a line of text; it does not appear in your task list or generate a reminder. Treat the sequence queue as the place that work lives.
›Can I test two subject lines?
Variants can be stored and are not yet rotated between. Write one subject per email step.
›What happens if a lead in a cadence converts?
The enrollment stays with the lead rather than following them to the new contact. Cancel it and re-enrol on the contact if the cadence should continue.