Branch Logic
Four questions a cadence can ask before it decides what to send next. Every answer is something the person on the other end actually did, rather than something anybody on your floor guessed about them.
Four questions, and the row that answers each
port not_clicked- 1Every link is rewritten to a signed redirect
- 2Following one is verified, then forwarded on
- 3A clicked row and an opened row are written together
- clicked
- not_clickedtaken
Product figures from the platform’s own defaults - not customer averages
How it works.
Opened and clicked come from the message itself
Each send carries a one-pixel image and has its links rewritten to a signed redirect on our side. Fetching the image records an open. Following a rewritten link records a click and an open together, because clicking implies one. Each is written once per message, so a preview pane firing twice is still one.
Replied is matched on the person, not the thread
Mail arriving through the Gmail, Outlook or IMAP sync counts as a reply when it comes from somebody with a live run and a send behind them inside a month. It is a contact-level match rather than header threading, which is exactly why that window exists.
Call outcome routes on the word the rep chose
A call step raises a task. Closing that task with an outcome writes the outcome back against the run, and the outcome box downstream takes the port carrying that name. You type the port names yourself, separated by commas, and anything unmatched falls to the catch-all.
You can trace why somebody ended up where they did
Every question records which way it went and what it read, stamped with the box and the run. So a person sitting on an arm you did not expect can be traced back to the answer that put them there instead of argued about.
One moment in every run.
Every run passes through the same seven. Branch Logic 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- Questions
- Opened, clicked, replied, and the outcome logged on the last call
- What they look at
- Only the most recent message this sequence sent that person, never their wider history
- Reply window
- Thirty days from the send. Older mail from the same person is not counted
- Reply matching
- Contact level. Incoming mail is not tied to the outgoing message by its headers
- Outcomes a call step reports
- Answered, no answer, voicemail, busy, wrong number. Your port names have to match those words
- Placement
- A question only knows what has happened by the time it is reached, so a pause usually belongs in front of one
- Not the same as
- This asks about behavior. Dividing an audience by weight is A/B Split Testing
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.
Enroll a lead once and the cadence carries them at their own pace. Nobody loses their place when the platform updates, and nobody is sent one message twice.
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.
Nobody gets a message at ten past three in the morning. A pause coming due outside the hours you set is pushed forward before the time is ever written down.
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 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 branch logic on your own floor.
Thirty minutes, your numbers and your data. We will set branch logic up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included