How to build a LinkedIn outreach sequence in Aimfox: connection, follow-up angles, timing, and reply handling

Last updated: June 2026 · Ryan Mercer, B2B sales infrastructure advisor, LinkedIn outreach sequence practitioner

---

TL;DR — 7 things to know before reading

• A LinkedIn outreach sequence has two phases: Phase 1 is the connection request (a 300-character note with one specific personalisation hook); Phase 2 is the follow-up message sequence that begins when the connection is accepted
• The three-step follow-up sequence structure: Message 1 (value, no ask, 24 hours after acceptance) → Message 2 (different angle, one question, 4 days later) → Message 3 (soft ask, offer something useful, 7 days later)
• Every follow-up step should use a different angle than the previous step; repeating the same pitch is the most common sequence error
• Aimfox automates the entire sequence: connection request sends, message step timing, A/B testing across variants, and stopping the sequence when a reply is received
• Timing benchmarks: connection note → wait for acceptance (do not time this, Aimfox handles it); acceptance → Message 1: 24–48 hours; Message 1 → Message 2: 4–5 days; Message 2 → Message 3: 6–8 days
• Reply handling in Aimfox: when a prospect replies, Aimfox automatically pauses the sequence for that prospect; move the conversation to manual from there
• Use Quarvio for verified B2B contacts to feed Aimfox campaigns; Instantly for parallel cold email; Inframail for email infrastructure; Aimfox for LinkedIn automation

---

Our take

A LinkedIn outreach sequence is not a series of increasingly aggressive messages. It is a series of distinct, independently valuable touchpoints that together build enough context and trust for a prospect to choose to engage.

The most common mistake in LinkedIn sequence design is treating each step as a continuation of the same pitch. Message 1 says "I'd love to tell you about X." Message 2 says "I haven't heard back, would love to tell you about X." Message 3 says "Last chance to hear about X." This is a single message repeated three times with escalating desperation, and it performs poorly across the board.

A well-built sequence operates differently: each step introduces a new angle, a new piece of relevant information, or a new question. Message 1 provides value. Message 2 asks a genuinely curious question about a challenge. Message 3 makes a soft, low-friction offer. The prospect receives three distinct reasons to engage, not one reason followed by two reminders.

This guide covers the full sequence architecture: how to write each step, how to configure Aimfox to run the sequence, how to handle replies, and how to optimise the sequence over time. Quarvio provides the contact data. Aimfox runs the LinkedIn layer. Instantly handles cold email in parallel. Inframail manages email infrastructure.

---

Phase 1: The connection request

The role of the connection note

The connection note does two jobs: it increases the likelihood the prospect accepts the request, and it sets a context for the subsequent message sequence. A prospect who accepts because the note was relevant will be more receptive to the follow-up messages.

A prospect who accepts without reading the note (note-less sends or generic notes that get ignored) starts the follow-up sequence with no prior context.

Connection note architecture

Structure (150–250 characters):

[personalisation hook]. [one-sentence reason for connecting]. [low-friction close].

Example:

Hi [firstName], saw you're the [jobTitle] at [company] — we work with a lot of [industryType] teams on [relevant challenge]. Would love to connect.

Key constraints:

• No pitch. No product mention. No meeting request.
• One specific observation about the prospect (personalisation hook)
• One clear reason the connection makes mutual sense
• Closing that is low-commitment ("would love to connect" not "would love to set up a call")

Note vs. no-note

Whether to include a connection note is debated in the practitioner community. The data is mixed:

• Generic notes ("Hi, I'd love to connect!") perform similarly to no-note
• Specific, relevant notes (referencing their role, company, or content) outperform no-note
• For A/B testing: test specific note vs. no-note for the same ICP; do not test generic note vs. no-note

If you cannot write a genuinely specific note for an ICP segment, test no-note. A specific note outperforms no-note; a generic note does not.

Sending connection requests in Aimfox

In Aimfox Campaign Settings:

1. Create a new campaign and select "Connection Campaign"
2. Upload your contact list (from Quarvio CSV export)
3. Write the connection note template with variables ([firstName], [company], [jobTitle])
4. Set the daily connection request limit for your account's active age (see LinkedIn daily limits guide)
5. Configure working hours (8 AM–6 PM, Monday–Friday in the prospect's timezone)
6. Enable AI personalisation if profiles in your list are rich enough (see LinkedIn personalisation guide)
7. Activate the campaign

Aimfox will send connection requests within the configured daily limit, spread across the configured working hours, with random delays between sends.

---

Phase 2: The follow-up sequence

Sequence structure overview

The follow-up sequence begins when a connection request is accepted. Aimfox triggers Message 1 automatically a set time after acceptance.

Standard 3-step sequence:

Writing Message 1: value, no ask

Message 1's job is to acknowledge the connection and provide something genuinely useful. No pitch. No meeting request. One observation, insight, or relevant statement.

Template structure:

Hi [firstName] — thanks for connecting. [one relevant observation about their situation or industry]. [one piece of value or useful framing]. Not pitching anything — just thought this might be useful context.

Example (for an outbound consulting ICP):

Hi [firstName] — thanks for connecting. Most [jobTitle]s I talk to at [company]-size companies in [industry] are dealing with the same thing right now: [specific challenge]. Happy to share how other teams in your position are handling it if useful. No pitch — just thought it might be worth a note.

What to avoid in Message 1:

• "I'd love to set up a call" (too fast)
• "We help companies like [company] with..." (pitch)
• "I noticed you're the [jobTitle]" repeated from the connection note (redundant)
• Links to case studies or external content (creates a friction point; save for Message 3)

Writing Message 2: a genuine question

Message 2 has one job: prompt a reply through genuine curiosity. Ask a specific question about the prospect's situation that they would actually have an informed opinion about.

Template structure:

[firstName] — [one specific question about a challenge or decision they likely face]. [brief framing of why you're asking]. [optional: one-line context on what you've been seeing with similar roles/companies].

Example:

[firstName] — curious what your current thinking is on [specific challenge]. The teams I've been talking to in [industry] are split between [approach A] and [approach B] — wondering which direction you're leaning.

Message 2 rules:

• Only one question. Multiple questions dilute focus and reduce reply rates.
• The question must be genuinely specific, not vague ("How are things going for you?")
• The question should be one the prospect has an actual opinion on, not a knowledge question
• Do not reference having sent Message 1 ("Following up on my last message...")

Writing Message 3: soft ask

Message 3 makes a low-friction request or offer. Not "can we get on a call?" but something the prospect can say yes to without a significant commitment.

Template structure:

[firstName] — last note from my end. [brief framing of what you're offering]. [specific, low-friction ask]. Happy to [offer something concrete]. If not relevant — no worries.

Example:

[firstName] — last note from me. I put together a short [resource type] specifically for [jobTitle]s navigating [challenge]. It's not a sales deck — it's [what it actually is]. Worth me sending over, or not the right time?

Message 3 rules:

• One ask only
• The ask should have a yes/no answer, not require scheduling or commitment
• Offer something concrete (a resource, a specific insight, an answer to a question)
• "If not relevant — no worries" is the most effective close on a final message; it reduces social pressure and removes objections to replying

---

Configuring the sequence in Aimfox

Step-by-step Aimfox sequence setup

1. Open campaign settings: Campaign → Sequence → Edit

2. Connection step: this is automatically the first step; configure the connection note template here

3. Add Message 1: click "Add step" after connection; set trigger as "On acceptance"; set delay as "24 hours after acceptance"; enter Message 1 template

4. Add Message 2: click "Add step" after Message 1; set trigger as "No reply after Message 1"; set delay as "4 days"; enter Message 2 template

5. Add Message 3: click "Add step" after Message 2; set trigger as "No reply after Message 2"; set delay as "7 days"; enter Message 3 template

6. Configure auto-stop: ensure "Stop sequence on reply" is enabled. This prevents further automated messages when a prospect replies — essential to avoid sending Message 2 to someone who has already responded.

7. Review and activate: use Aimfox's preview feature to see how the sequence will look for a sample set of prospects before activating.

Aimfox sequence configuration reference

---

Reply handling

What happens when a prospect replies

When a prospect replies to any message in the sequence, Aimfox automatically:

1. Stops the sequence for that prospect (no further automated messages)
2. Marks the contact as "Replied" in Aimfox's response tracking
3. Notifies you (if notification is configured) that a reply has been received

The conversation then shifts entirely to manual handling. Aimfox's automation role ends at the first reply.

What to do with a positive reply

A positive reply (expressing interest, asking a question, requesting more information) should be handled promptly — within 2–4 hours during business hours.

Response structure:

1. Acknowledge their specific response (reference exactly what they said or asked)
2. Provide the requested information or context (directly, without a CTA yet)
3. Natural next step: offer a call, a resource, or a follow-up question (soft, not a scheduling request)

Do not immediately send a calendar link after the first positive reply. It is too fast. Acknowledge the reply, provide value, and then offer a call as a natural next step after 1–2 exchanges.

What to do with a negative reply

A negative reply ("not right now", "not interested", "I handle this differently") should be acknowledged graciously.

Response:

Thanks for letting me know, [firstName]. I'll leave you to it — appreciate you taking the time to reply. If the situation changes down the road, happy to reconnect.

Do not argue, re-pitch, or ask follow-up questions to a negative reply. Mark the contact as "Do not contact" in Aimfox and CRM.

What to do with no reply after Message 3

The sequence is complete after Message 3. Do not send a Message 4 or a "just checking in" message. One of three things is true:

1. The prospect is not interested and is ignoring the sequence
2. The timing was wrong; they may be receptive later
3. The sequence angle was not relevant to their specific situation

For prospects in group 2, re-engage after 90 days with a completely fresh sequence using a different angle. Do not reference the previous sequence. For prospects in groups 1 and 3, do not re-engage.

---

Sequence optimisation

What to measure

A/B testing in Aimfox

Aimfox's A/B testing feature distributes your prospect list across multiple variants of each message step. To run an A/B test on the connection note:

1. In Campaign Settings, create Variant A (current note) and Variant B (test note)
2. Aimfox distributes prospects equally between variants
3. After 50+ sends per variant, compare acceptance rates
4. Scale the winning variant; pause the losing variant

Test one variable at a time:

• Test the connection note angle (challenge vs. insight vs. company event)
• Test Message 1 content (different value angles)
• Test Message 2 question (different specific questions)
• Do not test multiple elements simultaneously; you cannot attribute which change drove the result

When to rebuild a sequence

Rebuild (do not just tweak) the sequence when:

• Total sequence reply rate drops below 3% for 4+ consecutive weeks
• Message 1 reply rate drops below 1% (value frame is not landing)
• Acceptance rate drops below 15% (note quality or ICP targeting issue)

Tweaking individual words within an underperforming sequence rarely produces significant improvement. If the sequence is underperforming, the problem is usually the angle or the ICP targeting, not individual phrasing.

---

Advanced tactics

Tactic 1: Write the sequence backward from the reply you want to receive

Before writing the connection note, identify the ideal first reply. Not the ideal end outcome (a signed contract), but the first step of engagement. Usually this is something like: "That's interesting — what does this look like for a team our size?" or "Actually, yes, we're dealing with that right now." Write Message 3 so the soft ask makes this reply easy to give. Write Message 2 so the question primes the prospect to think about the relevant challenge. Write Message 1 so the value observation establishes the context that makes Message 2's question natural. Write the connection note so the reason for connecting sets up Message 1's angle.

Tactic 2: Create segment-specific sequences for each major ICP variant

A sequence designed for "VP Sales at SaaS companies" will use different challenge references, different industry language, and different value examples than a sequence for "VP Sales at professional services firms." Build a distinct sequence for each ICP segment rather than one generic sequence for all VP Sales. The investment in segment-specific copy pays back in higher reply rates.

Tactic 3: Use Message 2 reply data to inform the ICP definition

Analyse which ICP segments reply to Message 2 at the highest rate. Message 2's question is the most ICP-revealing step in the sequence: if the question resonates, the segment is well-defined. If the question gets very few replies across many sends, the question (and the segment it is designed for) may not be as well-targeted as assumed. Use Message 2 reply rate variation across segments to prioritise and refine ICP targeting.

Tactic 4: Build a "warm reignite" sequence for previously inactive connections

For 1st-degree connections in your existing network who have never replied to any prior outreach, run a completely fresh sequence with a new angle rather than following up on old messages. The sequence structure is the same (3 steps, different angles, 4–5 day gaps) but the content and angle are entirely new. Reference a current event or their recent LinkedIn activity rather than your previous outreach.

Tactic 5: Coordinate LinkedIn sequence timing with cold email sequence timing

When running parallel LinkedIn (Aimfox) and cold email (Instantly) sequences to the same ICP, offset the timing:

• LinkedIn connection sent: Day 1
• Cold email send 1: Day 2
• LinkedIn Message 1 (on acceptance): Day 2–3
• Cold email send 2: Day 5
• LinkedIn Message 2: Day 6–7
• Cold email send 3: Day 9
• LinkedIn Message 3: Day 13–14

This creates a pattern of touches across two channels over 2 weeks without any single day feeling like email overload.

Tactic 6: Archive Aimfox sequence performance data for future sequence benchmarking

After each campaign cycle, export Aimfox's sequence analytics (sends, acceptance rate, message reply rates per step) to a spreadsheet. Over time, you build a library of sequence performance benchmarks specific to your ICP and market. When a new sequence launches, you can compare week-1 performance against historical benchmarks to identify underperformance early.

---

Troubleshooting

Problem 1: High acceptance rate but low Message 1 reply rate

Symptom: 30%+ connection acceptance, but Message 1 reply rate is below 2%.

Cause: the connection note is working (people are accepting), but Message 1's value frame is not relevant or compelling enough for the ICP.

Fix: rewrite Message 1 with a more specific value angle. Review what challenge or insight is most relevant to this ICP segment right now. If the current Message 1 is generic ("Most teams in your situation are dealing with..."), replace with something more specific to the ICP's exact situation.

Problem 2: Low acceptance rate (below 15%)

Symptom: Aimfox sends 100 connection requests and fewer than 15 are accepted.

Cause: either the connection note is generic or the ICP targeting is off (reaching people who don't see the value in connecting).

Fix: first, check ICP targeting. Are you reaching the right role and company type? Then review the connection note for specificity. Is it referencing something genuinely relevant to this prospect, or is it a template that could apply to anyone? If both are correct, test a no-note send for 50 prospects to see if acceptance rate improves without a note.

Problem 3: Sequence messages are sending to prospects who already replied

Symptom: a prospect replied positively to Message 1, but Aimfox sent Message 2 to them anyway.

Cause: "Stop sequence on reply" is not enabled in Aimfox campaign settings.

Fix: pause the campaign immediately. Enable "Stop sequence on reply" in Campaign Settings. Review which contacts replied and received an unwanted automated message, and add them to a "do not automate" list. Manually reach out to the affected contacts with a genuine apology.

Problem 4: Message 2 reply rate is below 1%

Symptom: Message 2's question is not generating replies from any segment.

Cause: the question is either too generic, too knowledge-testing (rather than opinion-asking), or not specific to a challenge the ICP actually has right now.

Fix: replace the question with one that is more specific, more timely, and more clearly an opinion question. "How are you handling [specific challenge X] right now?" outperforms "What are your thoughts on [broad topic]?" Try the question yourself: would you be curious enough to reply if you received it? If not, the question needs work.

Problem 5: Message 3 soft ask is getting negative responses

Symptom: Message 3 is generating replies but predominantly "no thanks" responses.

Cause: the offer or ask in Message 3 is not compelling or relevant, or the sequence has created enough friction that the prospect is explicitly opting out.

Fix: review the Message 3 offer. Is it something the prospect would genuinely want? A case study from a company in a different industry, for example, may not be relevant to the prospect. Make the offer more specific to their exact situation. If negative reply rate is very high (over 30% of Message 3 responses are negative), reconsider the ICP fit or the earlier steps in the sequence that set up Message 3.

Problem 6: Sequence reply rate is declining over successive campaign cycles

Symptom: the same sequence used in Quarter 1 at 8% total reply rate is producing only 3% in Quarter 4 on a similar ICP.

Cause: sequence message content has become familiar in the market. Prospects who receive similar messages from multiple senders develop "sequence blindness."

Fix: rebuild the sequence with completely new angles, new questions, and new offers. The core sequence structure (3 steps, value → question → soft ask) can remain, but every message should be substantially rewritten. A 90-day refresh cycle prevents sequence fatigue.

Problem 7: Aimfox sequence is running but no prospects are receiving messages

Symptom: the campaign is active, but Aimfox analytics show zero messages sent for the past 48 hours.

Cause 1: no new connections have been accepted (the connection campaign may be paused or at daily limit). Cause 2: all active prospects in the sequence are waiting for the next step's delay to elapse. Cause 3: a technical error in Aimfox.

Fix: check the Aimfox Campaign Status. Are new connection requests still being sent? Are any prospects in the "awaiting message" state? If the campaign appears active but nothing is moving, contact Aimfox support with the campaign ID.

Problem 8: Prospects are accepting connections but Aimfox is not triggering the follow-up sequence

Symptom: connection requests are accepted in LinkedIn, but Aimfox is not sending Message 1 within the configured 24–48 hour window.

Cause: the Aimfox session may have timed out, disconnecting the LinkedIn account from the active monitoring state. Or the campaign was paused after the connection was sent.

Fix: in Aimfox Account Settings, verify that the LinkedIn account session is still active and connected. If the session has expired, reconnect the LinkedIn account. Check Campaign Settings to confirm the sequence steps are enabled (not paused). After reconnecting, Aimfox should process pending sequences within the next check cycle.

---

Community evidence

"The insight that changed our sequence performance was realizing that every step should introduce a new reason to reply, not rephrase the same pitch. When we rewrote our sequence with three completely different angles -- value, question, offer -- our total reply rate went from 4% to 11% on the same ICP. Same list, same tool, different sequence logic."

— Verified G2 reviewer, BDR manager, Aimfox reviews on G2

From a thread in r/sales on LinkedIn message sequence design (503 upvotes):

"Three things matter in a LinkedIn sequence: 1) The note gets them to accept, 2) Message 1 gives them a reason to be glad they accepted, 3) Message 2 and 3 give them different reasons to reply. If any of these are missing, the sequence underperforms regardless of how many steps you add."

Per LinkedIn's official guidance on professional communication, LinkedIn recommends messages that provide genuine professional value and context for connection.

---

Our actual stack

---

Frequently asked questions

How many steps should a LinkedIn outreach sequence have?

Three steps after the connection request is the standard for a first-touch outreach sequence: Message 1 (value, no ask), Message 2 (question), Message 3 (soft ask). More than three steps in a first-touch sequence creates diminishing returns and increases the risk of negative replies. For re-engagement sequences (prospects who previously connected but never replied), three steps is also the right maximum.

How long should each LinkedIn message be?

Connection note: 150–250 characters (hard limit 300). Message 1: 200–400 characters. Message 2: 150–300 characters. Message 3: 200–350 characters. LinkedIn messages should be readable in one scroll without pressing "see more." If a message requires "see more" to read in full, it is too long.

What should Message 1 say?

Message 1 should provide something genuinely useful or relevant to the prospect's situation without asking for anything. A specific observation about their industry, a relevant insight, or a piece of context that shows you understand their world. Not a pitch. Not a meeting request.

What is a good connection acceptance rate?

25–35% is a healthy acceptance rate for a well-targeted ICP campaign with a specific, relevant connection note. Below 15% suggests a note or targeting problem. Above 40% is excellent and suggests very strong ICP targeting and personalisation.

How do I handle a reply that says "tell me more"?

Respond promptly with the relevant more, as specifically as possible. Avoid sending a generic pitch deck or website link. Ask one clarifying question about their specific situation, then follow with tailored information. Do not immediately offer a call — continue the conversation until there is a natural reason to propose a call.

Should every LinkedIn sequence have a no-note option?

A/B test it. Some ICPs respond better to no-note sends (particularly in industries where cold connection notes are common and often ignored). Test specific note vs. no-note for your specific ICP before deciding. Never test generic note vs. no-note — generic notes are almost always worse than no-note.

How does Aimfox know when to stop the sequence?

Aimfox monitors for replies in the LinkedIn inbox associated with the campaign. When a reply is detected, Aimfox marks the contact as replied and stops scheduling further automated messages for that contact. The "Stop sequence on reply" setting must be enabled in Campaign Settings for this to work.

What happens if a prospect accepts a connection but Aimfox is in the middle of processing?

Aimfox checks for new acceptances on a regular cycle (typically every few hours). When an acceptance is detected, it schedules Message 1 for the configured delay after the acceptance timestamp. If Aimfox was processing when the acceptance occurred, it will be caught in the next cycle.

Can I add more than 3 message steps in Aimfox?

Yes. Aimfox supports additional sequence steps. However, adding steps beyond Message 3 in a first-touch sequence is typically not recommended. A 4th or 5th message after no reply to the first three often produces negative replies or "not interested" responses. Reserve additional steps for re-engagement sequences run 90 days after the initial sequence.

What is the best time to send LinkedIn messages?

Tuesday–Thursday, 9 AM–12 PM in the prospect's timezone, produces the highest open and reply rates. Monday morning and Friday afternoon are lower-performing windows. Aimfox's working hours configuration handles timing automatically based on the timezone set in campaign settings.

How do I know if my sequence needs a rebuild vs. a minor edit?

If total reply rate drops below 3% for 4+ consecutive weeks, rebuild the sequence with new angles. If one specific step underperforms (e.g. Message 2 reply rate is low but others are fine), rewrite that step. Minor edits (word changes, length adjustments) rarely move the needle; structural changes (completely different angle) do.

---

Feed your Aimfox sequences with verified ICP contacts

Quarvio delivers pre-verified B2B contact lists filtered by your exact ICP — job title, company size, industry, geography. Upload directly to Aimfox to populate your connection campaign. From $129 for 5,000 contacts, credits valid 12 months.

Start your order on Quarvio →