SMS in Sequences
A text step on the same canvas as the email and the call. It lands in the same thread the SMS inbox reads from, so the cadence and whoever picks up the reply are looking at one conversation.
A text step, from three phone columns to a receipt
sent- phone_e164+447700900142
- mobile_phone07700 900142
- phone01865 240110
- attemptsfive, then it stops
- backoffexponential, from a second
- at a timetwenty off the queue
- queuedwritten
- senthanded over
- deliveredreceipt back
- failedcarrier refused
- receivedtheir reply
Product figures from the platform’s own defaults - not customer averages
How it works.
It finds a number without anybody typing one
The first of the standardized number, the mobile and the plain phone field that has anything in it, cut back to digits and a leading plus. No number, or an empty body, and the step notes the reason and moves along.
The cadence and the SMS inbox share one thread
A number belonging to the workspace stands as the sender, the thread with that recipient is found or created, and a row goes in marked outbound. This is the same table the messaging screens read from, so the cadence and the inbox are looking at one conversation.
The queue is what carries it out
The row enters at queued and the messaging worker lifts it onto the carrier that holds the sending number, moving it to sent and then to delivered as the receipt comes back. It runs on the same job runner as the rest of the platform's background work.
A text can never block the cadence behind it
Sent or not sent, an entry is written against the run carrying the body, the recipient and the outcome. The walk always proceeds, so a text can never block a cadence behind it.
One moment in every run.
Every run passes through the same seven. SMS in Sequences 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.
8 facts- What the step holds
- One message body. No merge tokens are substituted into it before it is stored
- Number chosen
- Standardized field, then mobile, then plain phone. The first with a value wins
- Sender
- Whichever number the workspace hands back first, with no ordering asked for. The step cannot choose
- States
- Queued on the way in, then sent, delivered or failed as the carrier answers back
- Delivery
- Through the messaging queue onto the carrier holding the sending number, with the receipt written onto the row
- Inbound
- A reply lands on the same thread, and the SMS inbox is the screen it is read on
- Blocking
- Never. The walk carries on the moment the row is written, whatever the carrier does afterward
- Not the same as
- This sends a text from inside a cadence. Reading the conversation it starts is the SMS inbox
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.
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.
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.
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 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 sms in sequences on your own floor.
Thirty minutes, your numbers and your data. We will set sms in sequences up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included