Someone accepted your LinkedIn connection request but did not reply to the next message. You cannot tell whether they read it or why they stayed silent. Your follow-up should give them a different reason to reply.
This is different from re-engagement because the conversation never started. If a prospect replied or took part in a real exchange before going quiet, use the re-engagement guide instead.
First, check whether your connection note gave the person a clear reason to accept. The connection request examples cover that step. Then choose an angle based on information you can honestly add:
- Use the event angle when a real deadline or capacity constraint has changed.
- Use the customer-reference angle when you can offer a relevant conversation with actual customers or peers.
- Use the helpful-resource angle when the person has shown specific interest and you can answer a likely next question.
Use a real event deadline
Use an event follow-up when something material has changed: registration is closing, the room is nearly full, or the agenda now includes a session relevant to this person. The new fact gives them a reason to act instead of merely reminding them that you wrote.
In one of our events, we expected 25 guests, reached 43 registrations, and had been asked by Sequoia not to exceed 45. Those figures were specific to that event and show how to state a real constraint without inventing scarcity.
If you're on the fence, this is a final call to join.
We expected 25 guests and are at 43 now. Sequoia kindly asked us not to exceed 45 registrations.
A good indicator of relevance is whether you're running inbound or outbound campaigns on LinkedIn or email. If you're not running any and not planning to, then the event is not relevant.
The message lets the recipient decide whether the event fits their work instead of chasing a reply at any cost. Mention the relevant topic or audience, then let them make the call.
Keep every detail checkable. If capacity is not limited, use the actual registration deadline, a newly confirmed speaker, or a relevant agenda change. If nothing changed, do not use this angle.
Change the angle with a customer reference
If the first message led with your product, offer a relevant discussion with people solving a similar problem instead of repeating the pitch.
The reference must be real, current, and specific. Keep placeholders such as Company A and Company B until you have permission to name the companies, then replace them with the real participants before sending.
Hey Alina,
How about we set up a chat with one of our customers that started using Twain at a similar stage Acme is at right now?
Considering you lead RevOps, I think you'd enjoy talking to Nadja at Company A or Liam at Company B.
Let me know and I'll connect you.
Replying now leads to a focused peer conversation rather than another product pitch. The recipient can hear from a team with relevant experience and decide whether it applies to their own setup.
Only use this when the reference exists. Never invent customer names, imply a relationship you do not have, or offer a conversation nobody agreed to join. If a company must remain private, describe its business model, stage, or GTM motion at the level you may share.
Choose the reference for the problem and setup in the message. A well-known company with a different buyer, sales cycle, or operating model may not help.
Answer a high-intent lead’s next question
For high-intent inbound, use the specific action you observed: a guide request, webinar attendance, product conversation, or workflow question. Do not treat a profile view, an assumed read, or silence as evidence of intent.
Do some of the work before asking for a meeting. Send a resource that answers a likely question, then ask about their current setup. For a GTM buyer, the stack is useful because it affects implementation.
Hi Robbie,
If you asked me what would make the biggest difference in getting the most out of Twain, I'd recommend reviewing your imported persona. Here's a two-minute video with examples you can follow one-to-one.
By the way, what does your tool stack look like?
Happy to share a walkthrough on how to connect Twain with other GTM tools.
This example uses product activity as context without pretending to know what Robbie thought. It gives him the resource without requiring a meeting, then asks a quick question that can make the next reply specific.
Match the resource to the action. Someone who asked about CRM handoff needs the relevant implementation note, checklist, or example, not a broad ebook on AI for sales. The resource should help even without a sales call.
A campaign brief keeps the reason for reaching out, audience, offer, and sequence consistent before you write individual messages. The Campaign Brief guide shows how to make those decisions once instead of improvising for every lead.
Twain researches leads and writes research-backed LinkedIn sequences. That lets a follow-up use the angle supported by a relevant event, customer context, or inbound signal instead of repeating one reminder across the list.
When to follow up again and when to stop
No fixed number of days or follow-ups fits every LinkedIn conversation. Contact the person again only when you have another honest reason and enough potential value to justify the interruption.
Follow up when something material changed: a deadline, a confirmed customer conversation, another inbound action, or a useful answer to a likely blocker. Tie the message to that fact.
Stop when the next message would only say “checking in,” repeat the pitch, or manufacture urgency. Also stop after a clear no, when the offer is no longer relevant, or when you cannot explain why this person should care.
You do not need to diagnose silence. Send a new reason plainly when it is accurate and useful; otherwise, leave the connection alone.