Branching LinkedIn sequences: why 'if accepted / if not' beats a linear drip

Most LinkedIn tools run a linear drip: connect → wait → message → wait → message. It's simple, but it ignores the single most important fork in any outreach: did they accept your connection request or not?

The problem with linear sequences

If a prospect hasn't accepted your invite, you literally cannot message them. A linear sequence either stalls or — worse — keeps trying actions that fail, which hurts your account health. You're also treating a warm "accepted" lead exactly like a cold one.

What a branching sequence does

A branching sequence splits automatically after the connection step:

• Accepted branch: the prospect connected → move them into your message track (intro, value, soft CTA).
• Not-accepted branch: they didn't connect in time → switch to a lighter touch — visit their profile, like a recent post — to stay on their radar without forcing a dead-end message.

And critically: if the invite goes unanswered, it's auto-withdrawn after ~14 days so your pending pile stays small and your acceptance rate stays high.

A sequence that works

1. Day 0 — Visit profile (you show up in "who viewed").
2. Day 0 — Connection request with a short, specific note.
3. Branch:
   • Accepted → Day 1: thank-you + one-line value. Day 4: relevant resource + soft CTA.
   • Not accepted → Day 3: like a recent post. Day 7: nothing pushy.
4. Day 14 — Auto-withdraw if still pending.

Why it's also safer

Branching means you never hammer failed actions. Leads that can't be messaged simply don't get messaged — they get a softer, lower-risk touch instead. Better conversion and a healthier account.

In InstaLeadSync you build this in a 5-step wizard: a main branch plus Accepted / Not-accepted columns, with delays you control and auto-withdraw baked in.