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.
Want to see it first? Book a demo
- One reply pauses the sequence
- LinkedIn stays human-executed
- SMS and call steps in the sequence
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.
- SMS steps and call-task steps sit inside the cadence itself, and an await_event step holds a contact until something happens, such as a booking or a form.
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 with an owner, so every touch is on the record.
- 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 inside one SalesCrew cadence.
| Channel or step | How the step runs |
|---|---|
| Sent automatically through the mailbox pool | |
| Queued for a person; the ledger records what they did | |
| Call step | A call_task step with an owner, outcome recorded with call_log |
| SMS step | An sms step kind with consent and STOP handling |
| Wait for an event | An await_event step that pauses until something happens |
| Reply handling | Pause on reply, classify, suppress on unsubscribe, in auto by default |
| Guardrails | Three days between touches, per-cadence caps, send window |
Where it stops and a human starts
LinkedIn stays with a person on purpose. Automating the platform puts the account at risk, and a restriction takes the whole channel with it. The queue keeps your profiles safe while every touch still lands on the record.
Calls stay with a person for a different reason. Outbound voice runs through Vapi, but deciding to dial a list is an action the default policy keeps human, and anything that spends money is human-only whatever an agent's mode.
Your team signs off the copy 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
- Which channels can one cadence use?
- Email steps from the mailbox pool, LinkedIn steps in the human-worked queue, SMS steps and call-task steps. An await_event step can hold a contact until a booking or a form arrives.
- How does a LinkedIn reply pause the email steps?
- Someone records the reply in the ledger, and the pause follows from that. The reply is a fact your team enters, so the record stays accurate and your LinkedIn account stays untouched.
- 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.