Suppression Lists
One list per workspace of addresses nothing may go to. It is read when somebody is added to a cadence and read again inside the send itself, so an address that lands on it mid-cadence still stops the next message.
One roll, read at the door and again at the step
not on the roll- manualfrom the screen
- manualfrom the screen
- manualfrom the screen
- manualfrom the screen
- At the doorbefore a run existsNot on the roll. A run is created.
- At the stepafter the claim is takenClaim taken, roll read, nothing found. The message renders and the walk carries on.
Product figures from the platform’s own defaults - not customer averages
How it works.
A block follows the address, not the person
The address is the unique key, so it cannot appear twice and somebody who moves to a new address is no longer covered by the old row. A reason and a source travel alongside, which is how you tell a hand-entered block from an automatic one.
Checked at the door, and again at the step
Adding somebody to a cadence looks up their address first and refuses quietly if it is on the roll. The send path looks a second time after taking its claim, marks that claim failed, and halts the walk with the reason recorded. Anyone holding no address at all is admitted without complaint and then stopped at the first message.
Two ways on, and one of them needs nobody
The screen takes an address and files it as manual. A hard failure notice coming back is parsed as it arrives, the address is filed as bounced, and everyone currently on it is closed out. So the roll grows from what the receiving servers tell you as well as from what you type.
It stops the cadence; it does not edit the person
The run closes marked suppressed. The record itself is left alone: no flag is set on it, no tag written, and the do-not-call marks the phone side works from are an entirely separate thing.
Two moments in every run.
Every run passes through the same seven. Suppression Lists 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- Key
- The address. One row per address across the entire workspace
- Reasons the column describes
- Bounced, manual, replied, complained. That list is a comment beside the column rather than anything the database enforces
- Reasons written in practice
- Manual from the screen, and bounced from a hard failure notice the moment one comes back
- Consulted at
- The moment somebody is added, and again inside the send after the claim is taken
- Capitalization
- Compared exactly as stored. The same address filed differently cased is a second row
- The screen
- Newest five hundred rows. No search field and no paging beyond them
- Removing one
- Delete the row and that address can be written to again. Runs already closed stay closed
- Not the same as
- This is email only. Do-not-call on a record is a separate roll the dialer reads
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.
Park a lead for minutes or days between steps. The delay you type is a floor rather than an appointment, so the sending hours can push it later, not earlier.
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 suppression lists on your own floor.
Thirty minutes, your numbers and your data. We will set suppression lists up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included