What is a delay action?
The delay action causes a contact to "wait" before moving on to the next element (minutes, days, hours).
For example, you may want to send a personalised email following a request for a demonstration. To make the response seem more natural, you can add a one-hour delay rather than sending the email directly.
How do you use it?
Place the delay block in your workflow, usually following a trigger or action;
Set the delay (in minutes, hours or days)
Good to know!
What happens if I change the delay after a contact has entered the element?
Contacts are subject to the delay at the time they enter the delay element. If you change the configuration and re-publish the workflow, only those contacts who enter the action in the future will be affected by the change.
How are "days" measured?
A delay element starts counting from the moment the contact enters the element. If a contact enters at 5pm on Monday, the contact will move to the next element at 5pm the next day, 24 hours later.
What is the minimum time frame?
Give your contacts time to react to your emails/content.
In your workflow, allow a minimum of 3 days, ideally 7 when the next condition is a download. If you are testing your workflow internally, allow for a delay of at least 15 minutes as a precaution. Indeed, if your Plezi has several tasks to manage during this delay (emailing, promotions, etc.), it is possible that the tasks planned in your workflow will be put on hold. You might as well plan a little ahead.