Why some LinkedIn prospects stopped getting follow-up messages after accepting your invitation

What you're seeing

Short answer: your LinkedIn campaign is running, your invitations are being sent, people are accepting them — but your follow-up messages aren't arriving for some of those prospects. Two different things cause this. The common one is that those prospects are waiting their turn at a step you placed before your message, which is working exactly as you set it up. The less common one is a problem with the personalization placeholders in your follow-up step. Neither has anything to do with the prospects themselves or with their acceptance.

The typical fingerprint is: a portion of your accepted prospects move forward and receive your follow-up message, while another portion sit at the same step with their acceptance recorded but no follow-up sent. Sometimes it's a handful of prospects; sometimes it's most of them. Either way, the prospects are not lost, the invitations are not affected, and the campaign is not broken.

WarmySender is a 4-pillar outreach platform — Cold Emailing, Email Warmup, LinkedIn Outreach, and Multichannel sequences. This page covers the LinkedIn Outreach pillar, but the same template-personalization logic applies on every channel — the fix you make here will resume paused prospects on cold email follow-ups too.

Accepted, but the message hasn't sent yet — is it stuck?

Short answer: no. Queued is not stuck. If your sequence has any step before your first message — a "View profile" or an "Engage with post" — then a prospect who accepts correctly waits at that step until its turn comes. The message step simply hasn't been reached yet. Nothing has been dropped, skipped or lost, and you don't have to do anything: each prospect moves on to the message automatically as the queue clears.

This is the more common of the two causes on this page, and it isn't a fault at all. It's your own sequence order, combined with the safe pace your LinkedIn account sends at.

A campaign runs your steps in the order you wrote them, one at a time, for each prospect. So a sequence like this:

1. View profile
2. Send connection request
3. Engage with post
4. (if the connection was accepted)
5. Send message
6. (if they replied)
7. Send message

...has "Engage with post" sitting before your first "Send message". When someone accepts your invitation, they advance to the next step in line — which is "Engage with post", not the message. They will get your message; it comes right after that engagement runs.

So why doesn't the engagement just run immediately? Because engagement actions — liking or commenting on a prospect's post — are deliberately paced. Your LinkedIn account performs only a small number of them each day, and that number increases week by week as the account warms up. It's the same protection that keeps your invitations and messages at a natural, human rhythm instead of firing in a burst that looks automated. If ten accepted prospects are all queued at "Engage with post", that queue drains over the next several days rather than all at once — and each person moves on to your message as their turn arrives.

Two more things worth knowing while they wait:

• Your accepted prospects go first. When the day's budget is handed out, people who accepted and haven't been messaged yet are prioritized ahead of brand-new connection requests. Your warmest prospects are at the front of the line, not the back.
• Nothing expires while it waits. A queued prospect is never dropped, never timed out, and never needs re-importing. Every pacing gate defers the action to the next available opportunity — it doesn't cancel it.

On the campaign page you'll see a green note at the top when this is happening, reading something like "7 connections accepted — their first message is queued, not stuck." It names the step they're waiting on, names the message step that follows it, and shows when the next action is due.

How do I tell which of the two causes I have?

Short answer: look at the prospect's row on the campaign page. A prospect queued behind an earlier step names its next action and shows a time for it — and that prospect keeps moving. A prospect paused for a message fix shows an amber "needs a fix" note with no upcoming action, and it never moves until you edit the step.

Queued behind an earlier step — benign, nothing to do:

• A green note at the top of the campaign saying accepted connections are queued, not stuck.
• The prospect's row names the action that runs next — for example "Next: Engage with post" — with a scheduled time beside it.
• The prospect moves. Come back tomorrow and some of the queue has drained and the times have advanced.
• The prospect's status shows the connection as accepted, and the step it's sitting on is one you placed before your message.

Paused waiting for a message fix — needs about a minute of your time:

• An amber banner at the top of the campaign saying prospects are waiting for the message template to be fixed, with a Fix step → button.
• The prospect's row shows an amber note instead of an upcoming action and time.
• Nothing moves, no matter how long you wait. This pause is waiting on you, not on the clock.
• The rest of this page is about exactly this case and how to clear it.

If you see the green note and no amber banner, you're already done — everything below this point is about the amber one.

What can I do about a queued message?

Short answer: usually nothing — the queue drains on its own and every prospect gets your message automatically. If you'd rather messages went out sooner, you can reorder your own sequence, and there's one honest trade-off to weigh before you do.

• Do nothing. This is the right answer most of the time. The queue clears by itself, in order, at a pace that keeps your account safe. Accepted prospects are already at the front of the line. There is no button to press and no ticket to raise.
• Check the prospect's row if you want to see exactly where someone is. Open the campaign and find the prospect. The row now names the step that runs next and shows the time that action is scheduled for, so a scheduled prospect reads as scheduled rather than as a mystery. When the wait is a pacing one, there's a Why? link beside it that opens the sending account's Safe sending pace card and explains, in plain language, what that account can do today and why.
• Optionally, reorder your own sequence. If your priority is getting messages out faster, open the campaign's sequence editor and move "Engage with post" (or "View profile") to sit after your first "Send message", or remove it. Here's the honest trade-off: viewing a profile or engaging with a post before you message measurably lifts reply rates — the prospect has already seen your name once, so the message lands warm instead of cold. Removing those steps gets messages out sooner and gets fewer replies per message. It's a speed-versus-warmth trade, not a free win. Your sequence is yours: WarmySender will never reorder, skip or remove a step on your behalf. We run the campaign exactly as you authored it, so this change is only ever one you make.
• If everything feels slow, check the history you declared for the account. An account on the most cautious warm-up ramp paces every action — views, engagements, invitations, messages — more slowly and for longer. That ramp is chosen from what you told us when you connected the account. If you declared a past LinkedIn restriction but the account has in fact never been restricted, you can correct that yourself: open the account's Safe sending pace card and use Update account age & history. Please only declare "never restricted" if that is genuinely true. The cautious ramp is protection, not punishment — an account that really has been restricted before needs the slower build, and overstating its health is the quickest route back into trouble. Correcting the declaration adjusts the pace gradually from that point; it never jumps an account straight to full speed.

For more on how the pace itself is decided, see Why does my new LinkedIn account start slow? and How WarmySender protects your LinkedIn account. For the ceilings that sit above the ramp, see LinkedIn sending limits and account tiers. For how sending windows and pacing decide the clock time of each action, see How campaign sending schedule and pacing works.

Why does the other cause — a paused prospect — happen?

Your follow-up messages use placeholders like {{firstName}} or {{companyName}} to personalize each message — one template, many prospects, each one receiving a version that reads as if it was written for them. Sometimes there's a problem with these placeholders: a missing bracket, a typo in the variable name, or a custom variable that hasn't been filled in for some of your prospects.

When that happens, WarmySender pauses the affected prospects rather than sending a broken message. We do not send "Hi {{firstName}}," — that's the kind of mistake that ends up in screenshots on social media. We also do not silently send "Hi ," with the variable blank — that's not personalized, it's just impolite. Instead we pause the prospects on that step and surface a banner in your campaign so you can fix the template once and resume every paused prospect at the same time.

There are two common shapes of this problem:

• A template typo affects everyone. If you wrote {{firstName} with one closing bracket instead of two, every prospect on that step is paused — because the typo prevents the message from rendering for any of them. Symptom: nobody on this step has received a follow-up.
• A missing-on-some-prospects variable affects a subset. If you wrote {{custom.video_url}} and only half of your imported prospects have a video_url field filled in, only the half without the field are paused. The other half receive their personalized message normally. Symptom: some prospects on this step got their follow-up, others did not.

How do I fix it?

Short answer: open the campaign, click the amber banner that says some prospects are paused, fix the typo or the missing variable in your step's message, and save. Paused prospects resume automatically — you do not need to click Resume or manually re-enroll anyone.

Step-by-step:

1. Open your LinkedIn campaign. Go to the LinkedIn campaigns list and click into the campaign that has stopped sending follow-ups.
2. Look for the amber warning banner at the top. If any of your prospects are paused for a template problem, you'll see a soft amber notice at the top of the campaign page that reads something like "N prospects are waiting for the message template to be fixed." The banner includes a Fix step → button.
3. Click "Fix step →" to open the step with the problem. This jumps you directly to the editor for the step that needs your attention, with the problem field highlighted.
4. Check your message text for typos in variable placeholders. Every {{ needs a matching }}. A common typo is missing one of the brackets, like {{firstName} with one closing bracket instead of two. Another is a space inside the brackets, like {{ first name }} instead of {{firstName}}.
5. Make sure any custom variables you use are filled in for all your prospects. If you use {{custom.video_url}}, either every prospect in your audience needs a value in the video_url column, or you need to add a default value with the fallback syntax described below.
6. Save the step. The save button validates your message text — if anything's still wrong, WarmySender tells you exactly what to fix before the save completes. The instant your save succeeds, every paused prospect on this campaign is automatically queued back into the normal sending flow. You don't have to click Resume.

The first follow-ups for the previously paused prospects typically start landing within a few minutes, respecting your sending window, your daily limits, and your account ramp — same as any normal send.

What are the common template mistakes?

Short answer: the three most common are a missing bracket, a space or capitalization difference inside the brackets, and referencing a custom variable that doesn't exist on every prospect. All three are quick to fix in the step editor.

• {{firstName} (missing one closing bracket) — should be {{firstName}}. Every opening {{ needs a matching closing }}.
• {{ first name }} (extra spaces and the wrong capitalization style) — should be {{firstName}}. Variable names are typed without spaces. The picker uses the snake_case or camelCase form depending on the variable.
• {{custom.video_url}} (a custom variable that isn't present on every prospect) — either fill the video_url field in your prospect list for every prospect, or use a default value to handle the missing case. The fallback syntax is {{custom.video_url | default: ""}} if you want the placeholder to render as nothing when the field is missing, or {{custom.video_url | default: "our short demo"}} if you want a sensible substitute string instead.

A few less common mistakes that show up in real campaigns:

• {firstName} (only one opening bracket and one closing bracket) — should be {{firstName}}. Single brackets are not personalization placeholders; they appear in the message as literal text.
• {{firstName | default 'there'}} (missing the colon before the fallback value) — should be {{firstName | default: 'there'}}. The colon between default and the quoted fallback string is required.
• {{ first_name}} (a stray space right after the opening brackets) — usually fine on its own, but combined with other typos it can confuse the editor. We recommend no spaces inside the brackets unless you're using the fallback syntax.

If you're unsure whether your message text is valid, click Preview in the step editor. The preview pane renders your message with a real prospect's data substituted in, so you'll spot empty spots, literal token text, or formatting glitches before you save.

Which built-in variables can I always use?

Short answer: WarmySender ships with a set of built-in personalization variables that are always available on every prospect — names, company, job title, email, and the LinkedIn profile URL. You can use these in any follow-up message without importing anything extra.

The built-in variables you can use in any LinkedIn follow-up:

• {{firstName}} — the prospect's first name.
• {{lastName}} — the prospect's last name.
• {{fullName}} — the prospect's full name (first plus last).
• {{companyName}} — the prospect's company.
• {{jobTitle}} — the prospect's job title.
• {{email}} — the prospect's email address (when known).
• {{linkedinUrl}} — the prospect's LinkedIn profile URL.

Variable names are case-flexible — {{firstName}} and {{first_name}} both work and resolve to the same value. Pick whichever style your team prefers, and stick with it for consistency. The Insert Variable button in the step editor inserts the canonical form so you do not have to remember the exact spelling.

How do custom variables work?

Short answer: any extra column you add to your prospect CSV becomes a custom variable you can use in messages with the {{custom.<column-name>}} syntax. WarmySender now warns you at save time if you reference a custom variable that isn't filled in on any prospect in your audience.

If you import a CSV with a column called video_url, you can use {{custom.video_url}} in your follow-up message and each prospect receives their own value substituted in. If you import a column called shared_connection, you can use {{custom.shared_connection}}. Whatever column you import, however you spell it, you can reference it as a custom variable. The token name matches the column name, normalized to lowercase with underscores.

The platform now warns you at the moment you save a step if your message text references a {{custom.<name>}} variable that nobody in your audience has a value for. This catches the most common cause of paused prospects: typing {{custom.video_url}} when your CSV's column is actually {{custom.videoUrl}} or {{custom.videolink}}. The save dialog tells you which variable name doesn't match any column in your prospect list, so you can fix the name or update the column on the spot.

If your custom variable is only present on some prospects and you want the others to get a sensible substitute, use the default fallback syntax — for example {{custom.video_url | default: "our short demo"}} will substitute the words "our short demo" for any prospect whose video_url field is blank. You can also use an empty default with {{custom.video_url | default: ""}} if you want the placeholder to render as nothing for prospects without the field. The Insert Variable button guide covers fallbacks in more depth with worked examples.

What does WarmySender do for you now?

Short answer: we check your message at save time, we tell you exactly what's wrong before the save lands, and we automatically resume paused prospects the moment a clean save goes through. You don't have to babysit the campaign or click Resume.

• At save time, we check your message for typos and missing variables. If you write {{firstName} with a bracket missing, the save dialog flags it before it lands. If you reference a custom variable that isn't defined on any prospect in your audience, the save dialog tells you exactly which variable name doesn't match and lists the column names that DO exist.
• If you find out about the problem after you already shipped the campaign, fixing the template auto-resumes paused prospects. The instant your save succeeds, every prospect that was paused for this campaign's template problem is queued back into the normal sending flow. The first follow-ups typically start landing within a few minutes, respecting your sending window and daily limits.
• You'll see a banner at the top of your campaign while prospects are paused. The amber banner shows the count of paused prospects and includes a Fix step → button that jumps you straight to the affected step in the editor. As soon as the count clears, the banner disappears.
• No prospects are lost. Paused prospects sit in a recoverable state with the reason recorded. They are not consuming your daily limits, they are not affecting your sender reputation, and they are not eating ramp budget. They simply wait for the template to be fixed.
• The pause is purely on our side. No LinkedIn API calls are made on failed attempts — the message-text check runs before we ever reach out to LinkedIn — so there's no rate-limit cost to fixing and retrying, and your LinkedIn account does not see any failed-send signal.

Common questions

My connection accepted — why hasn't the message sent yet?

Almost always because your sequence has a step before your first message. If you placed a "View profile" or an "Engage with post" ahead of "Send message", an accepted prospect correctly waits at that step until its turn comes — the message step hasn't been reached yet. Those engagement actions are deliberately paced: your account performs only a small number each day, increasing as it warms up, so a queue of them drains over several days. Every prospect moves on to your message automatically, and accepted prospects are prioritized ahead of brand-new connection requests. Nothing is lost. If instead you see an amber banner saying prospects are waiting for the message template to be fixed, that's the other cause — see How do I fix it?.

Is my prospect stuck if it says it's queued?

No. Queued means "next in line", not "stopped". The prospect's row names the action that runs next and the time it's scheduled for, and that time advances as the queue drains — come back tomorrow and some of the queue will have cleared. Nothing expires while it waits: pacing defers an action to the next available opportunity, it never cancels it, and no prospect needs re-importing. The one case where a prospect genuinely doesn't move on its own is a pause for a message-template fix — that shows an amber "needs a fix" note with no upcoming action, and it waits on you rather than on the clock.

Can I make messages send sooner after someone accepts?

Yes — by editing your own sequence. Open the campaign's sequence editor and move the step that sits before your message ("Engage with post" or "View profile") to run after your first "Send message", or remove it. Weigh the trade-off first: viewing a profile or engaging with a post before you message measurably lifts reply rates, because your name is already familiar when the message lands. Removing those steps gets messages out sooner and gets fewer replies per message — speed versus warmth, not a free win. WarmySender will never reorder or remove a step for you; a campaign runs exactly as you authored it, so this is always your call. What we won't do either way is speed up the account itself — the daily pace is what keeps your LinkedIn account safe.

Why does my account only do a few profile views or post engagements a day?

Because a brand-new or recently connected account that suddenly performs dozens of actions a day is exactly what automated behavior looks like from LinkedIn's side. Your account starts at a low, safe number of actions per day and that number increases week by week as it warms up. The ramp's length depends on the account history you declared when you connected it — and an account declared as previously restricted takes the most cautious ramp of all. If you declared a past restriction but the account has never actually been restricted, you can correct that yourself on the account's Safe sending pace card via Update account age & history — only if it's genuinely true. See Why does my new LinkedIn account start slow? for the full explanation.

How do I fix paused prospects?

Open the campaign, click the amber banner at the top, fix the typo or missing variable in the step it points you to, and save. Paused prospects resume automatically the moment the save succeeds — no manual Resume click is needed. The first follow-ups typically start landing within a few minutes, respecting your sending window and daily limits.

What is a template variable?

A template variable (sometimes called a merge tag or placeholder) is a token like {{firstName}} that you put in your message text. At send time, WarmySender swaps the token for the prospect's real data — so the message your prospect receives reads "Hi Marie," not "Hi {{firstName}},". You write the message once and every prospect on your list gets a version that reads as if it was written for them.

Why did my prospects stop receiving follow-ups?

There are two causes and they look different on screen. The common one is that they haven't stopped at all — they're queued behind a step you placed before your message, such as "Engage with post", and they move on automatically as your account's safe daily pace allows. The row shows the step name and a next-action time. The other cause is a typo in a personalization placeholder, or a custom variable that's missing for some prospects, which makes WarmySender pause the affected prospects rather than send a broken message. That one shows an amber banner and doesn't move until you fix the template in the step editor and save — after which the paused prospects resume automatically.

Are my paused prospects lost? Do I need to re-import them?

No. Paused prospects sit in a recoverable state with the reason for the pause recorded. Your invitations are not affected, your acceptances are intact, your campaign is not broken, and no data is lost. The moment you fix the template and save, every paused prospect is automatically queued back into the normal sending flow.

Will the pause affect my LinkedIn account safety or my sender reputation?

No. The pause is purely on WarmySender's side. No LinkedIn API calls are made on the failed attempts — the message-text check runs before we ever reach out to LinkedIn — so your LinkedIn account does not see any failed-send signal and there's no rate-limit or reputation cost to the pause. When you fix the template and the prospects resume, every send goes through the normal account-safety gates: per-account daily limits, weekly limits, ramp ceiling, and sending window.

What if I don't see the amber banner but follow-ups still aren't arriving?

Then it isn't a template problem. Check the prospect's row first: if it names a step and a next-action time, it's queued behind an earlier step in your sequence and it will move on its own — see Accepted, but the message hasn't sent yet. Other alternatives: the prospect's acceptance is still being recorded (typically lands within a few minutes), the campaign is paused for a different reason (look for a paused status pill), your LinkedIn account session needs to be reconnected (look for the reconnect banner — see Why does my LinkedIn campaign say "Unresolvable URL"?), or you've hit your daily limit (the follow-up is deferred to the next sending window). Contact [email protected] with the campaign name and an affected prospect URL if you can't tell which.

My template looks correct but the banner still says prospects are paused. What's going on?

Hard-refresh the campaign page once — the count caches briefly. If the banner persists, the most likely cause is a custom variable that's missing for some prospects but present for others. Open the step in the editor, click Preview, and step through a few prospects in your audience using the preview's prospect selector. If a custom variable shows up as blank for some prospects, either fill that field on the affected prospects (you can update individual prospects from the prospect detail page, or simply import the CSV again with the column populated — matching is automatic) or add a default fallback to the variable so the missing case renders sensibly.

Will fixing the template re-send any messages to prospects who already received their follow-up?

No. The auto-resume only touches prospects that were paused by the template problem. Prospects that already received their follow-up are not re-sent. The platform tracks per-prospect per-step send history exactly so duplicates can't happen — fixing the template only unblocks the paused subset.

People also ask

Common adjacent questions about paused prospects and template fixes that come up alongside this guide.

Where do I see which prospects are paused?

On the campaign detail page, the amber banner at the top includes the count. Clicking through to the step in the editor and looking at the prospect list filtered to "waiting for template fix" shows you the specific prospects. The list is read-only — you don't need to do anything per-prospect; fixing the template resumes all of them at once.

Does this same problem affect cold email follow-ups?

Yes, the same template-personalization logic runs on every channel WarmySender supports. If a cold email step's body or subject line has a typo in a variable, or references a missing custom variable, the affected prospects are paused on that step in the same way. The fix is identical — open the step, fix the variable, save, and the prospects auto-resume.

Can I prevent this from happening in the first place?

Yes — use the Preview pane in the step editor before launching. It renders your message with a real prospect's data substituted in. If any variables show up as blank or as the literal token text, that's your cue to fix the typo or add a default fallback. The launch-time validator and save-time check are the second and third safety nets; the Preview pane is the first.

How long do paused prospects wait before they retry?

There is no time-based retry — paused prospects wait for you to fix the template. Once you save a clean template, every paused prospect on the campaign is queued back into the normal sending flow within seconds, and the first follow-ups typically start landing within a few minutes, respecting your sending window and daily limits.

Does the pause count against my account's daily or weekly sending limit?

No. The pause does not consume your daily or weekly LinkedIn limits, because no LinkedIn API call is made for a paused prospect — the message-text check runs before any provider call. Your account's ramp progress is not affected, and your sending budget is not eaten by paused prospects.

Will resumed prospects all send at once after I fix the template?

No. Resumed prospects are released back into the normal sending flow, which respects your campaign's sending window, your account's daily and weekly LinkedIn limits, your ramp ceiling, and the per-recipient cooldown. There is no burst — sends roll back to your usual cadence over the next sending window.