Send · Sequences
The default sequence changes rooms rather than repeating itself
When the workspace has both channels and the contact has a profile URL, one entry covers the whole chain. The email goes first. A few hours later it moves to LinkedIn: their latest post gets a like. No follow, and the connection request goes out with a fresh note. On accept, the first message waits 24 to 30 hours and is written fresh from their profile.
Opening message, written from the trigger
Like the latest post. No follow
Connection request with a fresh note
First message, written from their profile
New angle, never a bump
What is actually going on
Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.
A connection request has no follow-up on a timer
You cannot message somebody who has not accepted. An invitation unaccepted after a fortnight is marked lost, which is a status rather than a silence.
Any reply on either channel stops everything
Inbound skips every pending step for that contact. It does not pause one channel and keep the other running.
A sequence that runs out is not left looking alive
After the final touch has waited a full follow-up interval with no reply, the contact and their conversations move to lost. A real status with its own inbox folder. A reply arriving later still lands and still pulls them back out.
Without a LinkedIn side, the email cadence runs unchanged
The bridge fires only when the agent has LinkedIn and the contact has a profile URL. There is no degraded half-chain.
Step by step
How sequences runs
- 1
Step one
Email, once intent clears the threshold.
- 2
The bridge
A few hours later: like the latest post, send the connection request with a fresh note.
- 3
On accept
Wait 24–30 hours, then write the first message from their profile.
- 4
Or not
Unaccepted after fourteen days is marked lost. No timer-driven nudge to somebody who cannot receive one.
The numbers
Facts, not adjectives
Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.
- Launcher tick
- Every minute
- Bridge delay
- Hours, same day
- Post-accept wait
- 24–30 hours
- Invitation timeout
- 14 days, then lost
- Stop condition
- Any inbound, any channel
Sequences, honestly
Is the invitation detected by step number?
No. By message history. The launcher, the drafter, the acceptance webhook and the lost sweep all read the same thing, which is what stops them disagreeing.
Do follow-ups need approving?
Nothing needs approving. Once step one has left, the pre-planned follow-ups queue themselves and run on the sequence's own clock until a reply, an opt-out or the end.
Send
Out through your own accounts, at a safe pace
Sequences is one part of it. The rest runs too.
Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.