Skip to main content
All articles

Automation

Flow #3: a fast lane for your best-fit contacts

Not every contact deserves the same cadence. This flow gives contacts rated a high or excellent ICP match a shorter, more personal path to a first reply.

By Swimlane Updated September 14, 2026 4 min read

Most sequences treat a perfect-fit VP and a vaguely relevant intern the same way: same note, same delays, same three messages. The perfect fit deserves better, and the intern deserves less.

A Swimlane campaign can rate every contact in its audience against an ICP you write in plain language, on five levels: very low, low, medium, high, excellent, each with a short reason. This ICP-based flow is the fast lane for the top two.

The flow
  1. ICP fit Campaign audience: your source list, ICP match on, the ICP in plain words, Match strength "High match or better"
  2. Connection request A request with a note written for this persona · wait for acceptance: 5 days
  3. Condition The request's own acceptance wait: accepted within 5 days?
  4. No Tag Not accepted: tag "high-fit-pending", reviewed by hand once a month
  5. Yes Message Accepted: 1 day later, a message written for their role, ending on one precise question
  6. Yes Condition Replied to message · Last 7 days, checked 7 days after the message (outcomes below)
The reply check
  1. Condition Replied to message · Last 7 days
  2. Yes Tag Tag "replied": you take over in the inbox and move them into your pipeline by hand
  3. No Poke 7 days later, a poke: a notification without a second paragraph

Why it works

Two things change when the audience is narrow and the fit is high. You can afford a note that is actually specific, because you know who these people are. And you can follow up faster, because a slightly early nudge costs less than losing a great fit to silence.

The poke is the right second touch here. Swimlane sends a message and recalls it at once: they get a notification, and the thread gains no second paragraph.

Setting up the ICP fast lane

  1. The ICP. In the campaign’s Audience step, pick the source list and turn on ICP match. Write the ICP in two or three sentences: the role, the seniority, the kind of company, and who you do not want. Swimlane turns it into role and industry signals once, then reads each contact’s headline, current position, company and bio against them. Write it in the words people put on their profiles: a headcount nobody mentions cannot be matched. More on ICP match levels.
  2. The floor. Set Match strength to High match or better, which enrolls the High and Excellent contacts. It is the highest floor available. Contacts who join the list later are rated as they arrive, and enter if they clear it.
  3. The request. In the LinkedIn automation flow builder, a Connection Request with the persona note and Wait for acceptance set to 5 days. It branches on its own; a fast lane does not need the default week.
  4. The message and the reply check. On Accepted, Send Message with a 1-day delay, then a Replied to message condition, window Last 7 days, with a 7-day delay: a condition is checked once, when it runs. Yes: Add tag “replied”. No: Poke with a 7-day delay.
  5. Not accepted. Add tag “high-fit-pending” and nothing else. These are your best-fit people; open that tag once a month and decide by hand.

The note and the message

Request note:
Hi {firstName}, I compare notes with RevOps leads on how leads move from
SDRs to AEs, and your profile fits that exactly. Happy to connect.

Message:
Thanks for accepting, {firstName}. One question I ask every RevOps lead:
when an SDR hands a lead to an AE on your team, who owns it for the first
48 hours?

Both are written for the persona, not for one person: every word must be true for everyone above the floor. To go further, link the message step to an AI template, which adapts your example to each contact’s headline and your business context.

Guardrails

  • A contact can sit in several campaigns. Floors have no ceiling: a slow lane set to Medium match or better also enrolls your High and Excellent contacts. Give the slow lane another source list, or a longer delay before its request: by then the fast lane’s acceptances are connections, and Swimlane never invites an existing connection, so they leave the slow lane there. For invites still pending, open its Accepted branch with a Has a conversation condition, so nobody gets two first messages.
  • Low and very low fits get no campaign at all.
  • Ceilings and office hours apply to both lanes: 20 invitations and 150 messages a day by default, and every step inside your virtual office hours.

What to measure

The reply rate in each lane. The fast lane exists because these people get a better note and a better message; if its reply rate is not clearly ahead of the slow lane’s, neither is specific enough. And open the “high-fit-pending” tag every month: a best-fit contact who ignored one request is still a best-fit contact.

Do this with Swimlane

Everything in this article, minus the manual part.

Start my free trial

See how it works in Swimlane ICP scoring

Keep reading