ZELIQ applies a strict FIFO rule (First In, First Out) to determine how steps are executed in your sequences.
How it works
This FIFO logic applies to all automated steps in your sequences β including emails, call tasks, and LinkedIn actions β and follows two main principles:
1. Lead order matters
The order in which leads are added to a sequence determines when their steps are executed.
π The first lead added will be the first to receive each action (email, call, etc.) and gets priority to respect the time delays between each step.
2. Execution order across sequences
When multiple sequences are running at the same time, lead addition time is the only thing that matters.
ZELIQ applies a global FIFO logic β but only based on when each lead was added, not when the sequence was created. Leads are executed in the order they enter the system, regardless of the sequence they belong to.
π Oldest lead in = first action out β across all sequences. Sequence creation date has no impact on priority.
π Example
You create two sequences:
Sequence A (created Monday)
Sequence B (created Tuesday)
Then you add three leads:
Alice β Sequence A at 10:00
Bob β Sequence B at 09:00
Charlie β Sequence A at 11:00
π Execution order:
Email 1 β Bob (added first, even if in the newer sequence)
Email 1 β Alice
Email 1 β Charlie
How to run multiple sequences in parallel
To avoid one sequence eating up all your sending volume, stagger the sending days of your sequence steps.
Example:
Sequence | Sending Days |
Sequence 1 | Monday β Wednesday |
Sequence 2 | Tuesday β Thursday |
Sequence 3 | Friday |
π‘ This spreads out your outbound actions over the week and ensures a smoother, more balanced execution across sequences.
π§ Summary
Behavior | FIFO Applied? | Explanation |
Lead order in a sequence | β | First added = first executed |
Sequence creation date | βοΈ | No impact on execution order |
Global execution order | β | One unified queue, processed step-by-step globally |
π©πΌβπ» For further information, please do not hesitate to contact us: