A sequence is an ordered list of steps with waits between them. Every step consumes from the sending account’s daily budget.
Step types
| Step | Daily cost | Notes |
|---|---|---|
| Connection request | 80/week | The riskiest action. Optional note, 200 characters max. |
| Message | 100/week | Only to existing connections. |
| Follow-up | 100/week | A later message in the same thread. |
| InMail | 25/week | Needs Premium or an open profile. |
| Profile view | 150/week | Low risk, useful before a request. |
Steps carry a delay in hours rather than a separate wait step, and each step can be enabled or disabled without deleting it.
See weekly limits for the actual numbers.
Branching
After a connection request you can branch on the outcome:
- Accepted → continue to your message steps
- Not accepted after N days → stop, or follow instead
After a message you can branch on:
- Replied → exit the sequence (this happens automatically)
- No reply after N days → send the follow-up
Anyone who replies leaves the sequence immediately. You never have to build that rule yourself.
A sequence that works
- Profile view
- Wait 1 day
- Connection request, no note
- On accept, wait 1 day
- Message: why you are reaching out, one question
- Wait 4 days, no reply
- Follow-up: one new piece of value
- Wait 7 days, no reply
- Short final message that is easy to decline
Three to four messages over about two weeks is the useful range. Longer sequences rarely add replies and do increase the chance of being reported.
Ending well
The last message should make it easy to say no. “If this isn’t relevant, no problem at all, happy to leave it there” gets more honest replies than another pitch, and it protects your account, because people who can decline gracefully do not report you.