Salesgear now ensures your LinkedIn messages are sent only after a connection request is accepted, when your sequence is designed that way.
This update ensures that Salesgear waits before sending a LinkedIn message — but only when it can reliably do so. The result is fewer failed steps, cleaner sequences, and better LinkedIn safety.
This article explains this logic in detail. Feel free to skip to the section you want -
When Salesgear waits for connection acceptance
Salesgear waits only if:
A LinkedIn Connection Request step exists earlier in the same sequence
A LinkedIn Message step comes after it
In this case, the message step pauses and waits for acceptance instead of sending immediately.
Salesgear does not wait when:
A message is the first step
The connection request was sent outside Salesgear
The connection step was removed or reordered
This avoids incorrect assumptions about LinkedIn connection status.
How message scheduling works after acceptance
When a contact reaches the LinkedIn Message step after a connection request:
The step status becomes Waiting
On hover, users see: “Waiting for acceptance”
No message is scheduled yet
Once LinkedIn confirms acceptance:
The contact moves from Waiting → Scheduled
Message timing is calculated from the acceptance date, not sequence start
Example:
If a message is set for 4 days after the connection step
Acceptance on Day 3 → Message sends on Day 7
What happens if the connection is not accepted
No LinkedIn API call is made
No message is sent
The contact remains safely in Waiting
If the connection is:
Declined or withdrawn → Message step is Skipped
Hover message shows: “Connection request rejected”
This prevents unnecessary failures and protects account health.
Scenarios where waiting does not apply
Waiting logic is not applied when:
A LinkedIn Message is the first step
A prospect connects outside Salesgear
LinkedIn reports the prospect is already connected
In these cases:
Messages are attempted immediately
Existing success/failure behavior remains unchanged
How sequence changes affect message sending
Sequence edits can remove the dependency:
Message reordered before connection request
Connection request deleted after enrollment
When this happens:
Waiting logic is removed
Message behaves like a standalone step
Previously waiting contacts proceed normally
Salesgear does not retroactively enforce dependencies.
Handling multiple contacts with different acceptance times
Each contact is handled individually.
Example:
Message scheduled 4 days after acceptance
Contact A accepts Day 1 → Message Day 5
Contact B accepts Day 3 → Message Day 7
Contact C never accepts → Message never sent
This keeps timing accurate without manual intervention.
Key takeaways
Waiting applies only when a connection request exists in the same sequence
Message timing is based on acceptance date, not sequence start
No acceptance = no message
Declines and withdrawals safely skip the message
Existing LinkedIn behavior remains unchanged elsewhere
This keeps sequences predictable, safer, and closer to how LinkedIn actually works.