Sending Windows
The hours a cadence is allowed to act inside. A pause that would come due outside them is pushed forward before the time is written down, so an overnight gap ends at nine and not at ten past three.
Nine to five, and what happens to a moment outside it
moved laterProduct figures from the platform’s own defaults - not customer averages
How it works.
Five settings, held on the sequence itself
A switch, an opening hour, a closing hour, whether weekends count, and the offset. They live on the cadence rather than the workspace, so one aimed at a single market can keep hours the one beside it does not.
A fixed offset, not a named zone
The window is expressed as minutes away from universal time, typed into the settings box as a number. There is no zone list and nothing consults where the recipient lives, so selling into several countries means a cadence per country.
Forwards only, and never onto a shut day
Too early moves to that day's opening hour. At or past closing rolls to the next day's opening. With weekends excluded, Saturday and Sunday roll on as well. Closing is read as the first hour outside, so a window ending at five includes four fifty-nine and not five.
A volume ceiling defers rather than drops
How many messages a workspace may send in a day is read from the deployment environment. A step meeting the ceiling re-parks about an hour out without taking its claim, so nobody is skipped. They are only later.
Two moments in every run.
Every run passes through the same seven. Sending Windows is the lit ones, 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.
8 facts- Settings
- On or off, an opening hour, a closing hour, weekends excluded, and an offset in minutes from universal time
- Out of the box
- Nine to seventeen, weekends included, offset of zero, and the whole thing switched off until you turn it on
- Timezone
- One offset per cadence, entered as a number. Not a zone name, and never read from the recipient
- Direction
- Later only, and only on a pause. The moment somebody is enrolled is stamped as now and never clamped, so a first send can land outside the hours you set
- Search limit
- Ten passes, each moving the moment at most one day. Give it hours that can never be met and it stops after the tenth and hands back the date it had reached, not the one you started with
- Daily volume ceiling
- Set through a deployment setting and counted per workspace per day. It is not a field on the settings box
- Not covered
- Public holidays, and quiet hours belonging to an individual recipient
- Not the same as
- This is when a step may land. How long to hold before it is Wait and Timing
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.
Thirteen node kinds on a canvas: send, wait, branch on behaviour, split, call task, tag, goal. Publish a version and in-flight leads keep their own place.
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.
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 sending windows on your own floor.
Thirty minutes, your numbers and your data. We will set sending windows up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included