Skip to main content
All CollectionsCampaigns tab
Why the messages are not sent to the leads who accepted the request?
Why the messages are not sent to the leads who accepted the request?
Oleksandra Nesteruk avatar
Written by Oleksandra Nesteruk
Updated over a week ago

Our system is designed to always follow the steps and delays you’ve set in your campaign. If messages aren’t being sent to leads who accepted your request, there could be a few reasons for this:

1. A Note in Your Connection Request

If you included a note in your connection request and the contact responded to it, the follow-up messages won’t be sent. The sequence stops for these contacts once they reply to the note


2. "Immediately" Time Delay for the "If Connected" Condition

When the "Immediately" time delay is used, the system checks whether the contact will accept the request right after it’s sent. If the contact doesn’t accept immediately, the system moves them to the "No" branch, and the next steps in the "Yes" branch won’t be executed.


You can check more details about how this delay works here


3. Custom Delay for the "If Connected" Condition

If you’ve set a custom delay (e.g., 1 day) for the "If connected" condition, the system checks whether the request was accepted after that time:

  • If accepted within the delay: The system processes the steps in the "Yes" branch.

  • If accepted after the delay: The contact remains in the "No" branch, as the condition was already processed.

Please note, if a lead accepts the request after the delay has passed, they won’t be moved back to the "Yes" branch automatically. To send follow-up messages, you can add another "If connected" condition to the "No" branch.


If none of these situations apply or you need further assistance, contact us via live chat or email us at [email protected] with the campaign name and details about the case

Did this answer your question?