Sending Windows
Nobody gets a message at ten past three in the morning. A pause that would come due outside the hours you set is pushed forward before the time is written down, so the gap ends when the window opens.
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.
The hours belong to the cadence, not the workspace
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.
Hitting the daily ceiling delays somebody, never skips them
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 enrollled 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 outside triggers that act without being asked.
What you draw is the thing that runs, not a picture somebody then has to build. Thirteen kinds of step, and publishing never moves a lead off their own place.
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.
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 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