All Collections
Drip Campaign Setup
Understanding the "Leads Queue" in Dripify Sequences
Understanding the "Leads Queue" in Dripify Sequences

Learn why your leads are queued in different stages of your sequence and how it can be helpful for you

Anna from Dripify avatar
Written by Anna from Dripify
Updated over a week ago

A lead that is entered into a sequence in your Dripify campaign goes through multiple steps until they reach the final action.

Dripify allows you to view the number of leads in the queue at each step of the sequence.

From the screenshot above, you can see that 331 leads are currently in the queue for the "Send an invite" action. This means that 331 leads are currently waiting for their turn to be processed by Dripify, and once processed, they will be moved to further stages of the sequence.

Once a lead moves through the entire sequence, they end up in the "Completed" list of the corresponding branch.

Clicking on a preferred queue will open up a list of leads that are currently in that queue.

From here, you can remove specific leads from this stage, go to a lead’s profile to change their info (first name/last name, company, position, etc), or export these prospects to a CSV file.

In some cases, you might see "Failed" on some stages in your sequence.

From the screenshot above, we see that Dripify failed to send 25 connection requests and 13 InMails.

You can click on the failed list to see all the leads that Dripify did not manage to process and see the exact reason why the software did not manage to perform an automated action with the lead by opening the prospect's profile.

You can export these "failed" prospects, then import into another campaign to try performing actions on them.

The ability to view the lead queues allows you to have a clear picture of how everything goes in your sequence.

Therefore, it's highly recommended to regularly check the sequences of your active campaigns in Dripify (especially during the first days after the campaign launch) to make sure all leads are processing well and there are not too many failed action attempts.

Did this answer your question?