Email, LinkedIn and calls in one cadence
One sequence, several channels, and a single rule underneath: a reply anywhere stops everything else for that person.
- One reply pauses the sequence
- LinkedIn stays human-executed
- SMS steps on the roadmap
The short answer
- The cadence is the spine. Email steps send automatically from the mailbox pool; LinkedIn steps appear in a queue that a person works by hand, because SalesCrew never automates LinkedIn itself.
- A reply on any channel pauses the sequence for that contact. That rule runs in auto by default and it is the one behaviour that keeps a multichannel sequence from becoming harassment.
- Two step kinds are not built. SMS steps and call tasks inside a cadence are on the roadmap, so today a call step is a task you create beside the sequence rather than inside it.
Trigger to logged
One contact's path through a mixed sequence.
- 1
Trigger: an audience is frozen
The segment freezes with suppression applied, and contacts enter the cadence at step one. cadence_enroll does the same from a script.
- 2
Step one sends by email
From the mailbox pool, inside your business-hours window, under per-account daily caps with cooldown stamps and suppression re-checked at send.
- 3
Step two appears in the LinkedIn queue
The contact shows up in the queue with the sending profile assigned. A person opens LinkedIn, does the action and sets the status. Nothing is automated on the platform itself.
- 4
The human works the queue and the tasks
The queue for LinkedIn, a task for a call. Both are visible work rather than invisible automation, which is the honest description of what a multichannel sequence really is.
- 5
A reply pauses everything
Email reply, LinkedIn reply recorded in the ledger, or a call outcome logged. Any of them pauses the cadence for that contact and the thread lands in the shared inbox.
- 6
What gets logged
Each step attempted, each touch recorded, the ledger status per LinkedIn row and the call disposition. cadence_funnel reads the whole thing back as numbers.
What gets configured
Which channel does what, and whether it is built.
| Channel | How the step runs | Status |
|---|---|---|
| Sent automatically through the mailbox pool | Available | |
| Queued for a person; the ledger records what they did | Available | |
| Call | A task created beside the cadence, outcome recorded with call_log | Available as a task |
| Call step inside the cadence | A call_task step kind in the sequence itself | On the roadmap |
| SMS step | An sms step kind with consent and STOP handling | On the roadmap |
| Wait for an event | An await_event step that pauses until something happens | On the roadmap |
| Reply handling | Pause on reply, classify, suppress on unsubscribe | Available and in auto by default |
| Guardrails | Three days between touches, per-cadence caps, send window | Available |
Where it stops and a human starts
LinkedIn stops with a person on purpose. Automating the platform risks the account, and an account restriction takes the whole channel with it. A queue is slower and it survives.
Calls stop with a person for a different reason. Outbound voice through Vapi exists, but deciding to dial a list is the kind of action the default policy keeps human, and anything that spends money is human-only regardless of an agent's mode.
Writing the copy stops with a person too. An agent can draft a sequence from a brief; the draft waits in the approval queue. That is the same rule that governs every external send in the product.
Questions
- Can I put an SMS step in a cadence today?
- No. SMS step kinds are on the roadmap along with the rest of the phone pack. Email steps and the LinkedIn queue are what a multichannel sequence looks like today.
- How does a LinkedIn reply pause the email steps?
- Someone records the reply in the ledger, and the pause follows from that. It is a human-entered fact rather than a scraped one, which is the trade for not touching the platform.
- How many touches should a sequence have?
- Fewer than the temptation. Guardrails enforce at least three days between touches per contact and a cap per cadence, so the sequence cannot quietly become daily contact.