Acceptance-aware messaging
How to automate LinkedIn follow-up messages after someone connects
The first message after a connection is where many sequences become obviously automated. The person accepts, and seconds later a long pitch arrives that ignores everything about how the connection happened.
OutreachGenie can wait until the connection is visible, pause for a reasonable interval, send a message, and check for a reply before continuing. The feature is most useful when the copy is brief and the stop logic is treated as seriously as the send logic.
01
Separate invitation logic from message logic
A connection request and a message have different prerequisites. If the person is already a first-degree connection, the flow may be able to message them. If an invitation is pending, the flow should wait. If they decline or never accept, the message path shouldn't pretend otherwise.
OutreachGenie's connection checks and When user accepts action make that state visible in the flow instead of hiding it in a timer.
02
Build an acceptance-aware sequence
- 01
Send or verify the connection
Use a connection request step only for prospects who are not already connected.
- 02
Wait for acceptance
Add When user accepts. This step watches synced connection state instead of assuming acceptance after a fixed number of days.
- 03
Pause before the message
Give the connection some breathing room. An immediate pitch can make the invitation feel transactional.
- 04
Send one useful message
Use a specific observation or question. Keep the request smaller than a meeting unless the prior context already supports one.
- 05
Check reply before follow-up
A reply should remove the person from the automated branch and put the conversation back in human hands.
03
Write messages that can survive being read aloud
- Say why the conversation is relevant
- Use the person's actual work or shared context
- Ask one answerable question
- Remove the calendar link from the first touch unless it was requested
- Read the message aloud and delete anything you would not say
04
Know when the sequence is over
One thoughtful follow-up is usually more defensible than a chain of “just bumping this” messages. If there is no reply, end the sequence cleanly and leave the connection intact.
If the person replies with a question, objection, or polite decline, stop automation. Reply detection isn't only a conversion feature; it's basic respect for the conversation.
Common questions
Questions that come up in practice
Can OutreachGenie wait until a LinkedIn invitation is accepted?
Yes. The When user accepts flow action waits for synced connection state before allowing the accepted branch to continue.
Can I send a message to someone who isn't connected?
The standard Send message flow action is intended for first-degree connections. Other LinkedIn products such as InMail have different rules and are not the same workflow.
How many follow-ups should I automate?
Use as few as needed to communicate something useful. A short sequence with reply checks is easier to review and less likely to feel like a drip campaign.
Research used for this guide
Try the workflow