Wait & Timing
The box whose whole job is to do nothing yet. It stamps a time to come back, marks the person as parked, and leaves the noticing to the sweep that runs every minute.
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 recognises itself as the place it parked, and this time the walk passes straight on.
The due time is nudged before it is saved
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.
Resolution belongs to the sweep, not the clock
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 honoured 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 webhooks that act without being asked.
A unique URL per integration with HMAC signing, rate limits, payload caps and idempotency - plus a log of every delivery it ever accepted or refused.
Branch on whether they opened, clicked or replied, and on how the last call was dispositioned - so the next step answers what actually happened.
Weighted splits assigned by a deterministic hash of the enrolment, so a lead always takes the same arm no matter how often that step is run again.
One do-not-contact roll per workspace, checked when a lead is enrolled and again inside the send, straight after that send has taken its own claim.
New leads enrol themselves the moment they are created, and the four guards that can refuse an add are read on every single route into a cadence.
Drop a call step into a sequence and it raises an assigned task on the lead's owner, with the outcome the rep logs coming back as a branchable answer.
Name a linked deal as the outcome that means the sequence worked. Reaching it stamps goal met on the run and takes the branch you wired behind it.
Twenty-six behaviours attach to wrap-up codes, and twenty codes ship already pointing at one, so ending a call the right way books the follow-up.
Six event types a CRM rule fires from: stage change, field update, new record, reassignment, schedule and inactivity, agreed in four places at once.
Send the email, assign the owner, raise the task, set the field, move the stage or call a webhook. Six modules, run in the order you stored them.
Eight comparison operators guarding each action, combined with AND and only AND, so a rule meaning either of two things is built twice, as two rules.
A text is a step on the same canvas as the email and the call task, written into the real thread and carried out by the number it is going out from.
A versioned path, a key minted once and kept as a hash, and the same role and profile model the interface runs on deciding what that key may touch.
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