Wait & Timing
The step whose whole job is to do nothing yet. It parks somebody until a time you set, and the delay you type is a floor rather than an appointment, because the hours on the cadence can push it later.
The box whose whole job is to do nothing yet
waiting- Visit one
- work out the due moment
- mark the run waiting
- stop here
- In between
- the sweep looks once a minute
- not due yet, so leave it
- nothing is counting down
- Visit two
- waiting, and standing here
- flip back to active
- walk straight on
Product figures from the platform’s own defaults - not customer averages
How it works.
Minutes, and nothing but minutes
One whole number sits on the box and the form asks for it in minutes. A day is fourteen hundred and forty, which is what a new one arrives holding. There is no separate hours or days control, and no calendar date to point at.
Arriving parks; returning walks through
The first time the walk reaches it, a due time is stamped, the run is marked as waiting, and everything stops there. When the sweep brings that run back, the box recognizes itself as the place it parked, and this time the walk passes straight on.
The delay you type is a floor, not an appointment
Where hours are set on the sequence, the computed moment moves forward to the next point that sits inside them, and only then is it stored. So the delay you typed is a floor rather than an appointment.
A short pause is approximate, by about a minute
A due time only gets acted on when the next pass comes round, once a minute. Short pauses are therefore approximate by up to that much, and a pause of zero simply means the following pass will pick it up.
One moment in every run.
Every run passes through the same seven. Wait & Timing is the lit one, and everything either side of it is a different page in this category.
- 01Trigger
the thing that happened first
- 02Enrol
how somebody gets onto it
- 03Wait
the pause, and what governs its length
- 04Branch
the fork, and which side is taken
- 05Act
the mail, the text, the task that goes out
- 06Measure
what counts as it having worked
- 07Exit
how somebody comes off it
The specifics.
7 facts- Unit
- Minutes. One whole number per box, and fourteen hundred and forty on a new one
- Ceiling
- None is enforced. A very long pause is stored and honored the same as a short one
- Precision
- To the nearest sweep, so roughly a minute. This is not scheduling an appointment
- Effect of hours
- The stamped moment is only ever moved later to land inside them, never earlier
- Loops
- A box may point back to an earlier one. Only a box wired straight into itself is rejected at publish; a longer ring with no pause in it is caught later by the hundred-step ceiling
- While parked
- The run counts as waiting. Pausing the sequence leaves it parked, and the due time is not extended to compensate
- Not the same as
- This sets the length of a gap. The hours a gap may end inside are Sending Windows
What starts this, and what it starts.
Automation is only ever a middle. These are the things that set it running and the things that run because of it.
More in Automation & Flows
13 capabilitiesSequences, dispositions and outside triggers that act without being asked.
One address per source, sitting outside the login. The same delivery is never counted twice, every exchange is filed, and a new address cuts that source off.
The next step answers something the person actually did, not something your floor guessed. Opened, clicked, replied, or how the last call was dispositioned.
Two versions of one cadence, side by side. Nobody lands on both and nobody switches halfway, because the side is decided by arithmetic on their own record.
One do-not-contact list per workspace, read on enrollment and read again inside the send, so an address added mid-cadence still stops the next message.
Nobody builds the list by hand. New leads enroll themselves as they are created, and the four checks that can refuse one run on every route into a cadence.
The phone, in the middle of a mail cadence. A rep gets a call task with their name on it, and whatever they log at hang-up decides where that lead goes next.
Stop writing to somebody who already bought. Name the deal state that means the cadence worked, and reaching it stamps the run and takes the branch behind it.
The do-not-call mark, the callback and the task happen because a rep picked the code, not because they remembered. Twenty-six behaviors, twenty codes shipped.
Six things set a CRM rule off: stage change, field update, new record, reassignment, schedule, inactivity. A filter stops it waking for everything that moves.
Send the mail, assign the owner, raise the task, set the field, move the stage, call a webhook. Six actions, none a placeholder, run in the order you set.
The check between a rule firing and an action actually running. Eight comparisons, every one an AND, so a rule covering either of two things gets built twice.
A text step on the same canvas as the mail and the call. It lands in the thread the SMS inbox reads, so the cadence and whoever answers see one conversation.
A key on a versioned path, seen exactly once, held to the same role and profile a person on your floor is, so it never reaches further than they would.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Automation & Flows
See wait & timing on your own floor.
Thirty minutes, your numbers and your data. We will set wait & timing up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included