Delays: Follow-ups and queued actions
When setting up two or more automated drip campaign actions, it is possible to set a minimum delay for each one.
Note: the first action is scheduled immediately after enrolling, i.e. once Dux-Soup adds the LinkedIn prospect to the campaign.
The timestamp of delayed action is set according to the rules below.
Actions set before the connection request:
The action delay is set once Dux-Soup executes the previous action.
Actions set after the connection request:
When enrolling 2nd and 3rd-degree connections, the first action delay set after the connection request is triggered when Dux-Soup detects the new connection.
For 1st-degree connections, the first action delay is counted from the time Dux-Soup enrolled them on a campaign if the campaign starts with a connection request. In this case, the connection request is skipped.
All subsequent action delays are set after the previous action has been performed.
The actual delay may not match the minimum delay you have set, as the robot's operations will always abide by the current daily limit and speed settings. Actual action delay can be longer due to the following:
- daily visit limit has been reached
- daily message limit has been reached
- the schedule of the Dux-Soup Planner stops the robot from doing work ( Dux-Soup Options > Planner )
- the computer is switched off, or Chrome isn't running (The On/ Off switch )
- the robot pauses after 20 visits.