Magnews provides different types of waiting nodes for your automation flows. Each one designed for a specific purpose.
'Wait': waits for a defined time
It is the classic of the wait nodes: when the automation flow session enters the ‘Wait’ node, it will wait for the specified time (in minutes, hours, days or weeks) to elapse before restarting.
... and the session resumes ...
Specify when to restart the session:
- On any day: in this case you can also choose any time or a time slot. For example any day, but only from 9 a.m. to 6 p.m. if you send SMS, so as not to disturb.
- From Monday to Friday: in case you want to exclude weekends, making sure that you do not exclude public holidays. Again, you can choose a specific time or time slot.
- On the weekend: if, for example, you send communications that are useful are Saturday and Sunday.
-
Only on specific days of the week: in this case you have to choose which days. For example for odd-numbered days:
-
Only on a specific day of the month: for example, if you want the session to resume only on the first day of each month, indicate ‘1’.
Note that the contact only leaves once the waiting time has ended. So if you indicate 6 and the waiting time ends on 7 January, the session will restart on 6 February.
If you indicate 31, the contact will only restart the automation flow in the first month that has this day (if it is April it will restart on 31 May).
-
Only on the last day of the month: useful because it autonomously calculates what the last day is, whether it is 28, 29, 30 or 31.
-
Only on a specific day of the year: e.g. the first day of the year or Christmas Day of each year.
-
Only on an exact date: if all sessions arriving at the node must start on the same day.
Days to be excluded
You can specify days on which the session is not restarted, but remains suspended until it is a day to be excluded.
For example, if you want to exclude all or some holidays, you can list them so that you can create days on which your contacts are not disturbed.
How to indicate days to be excluded:
Indicate the days separated by enter, in the following format:
- dd: a specific day of the month. Example: 01 skips the first day of each month.
- dd/mm: a specific day of the year. Example: 01/01 for the first day of the year.
- dd/mm/yyyy: a specific date. Example: 04/20/2025.
'Q Wait': when you have no data to decide
You configure, for your eCommerce, a flow for the retrieval of abandoned shopping carts. But what is the best waiting time? 1 day? 1 hour? If you have no data to decide for yourself, the Q Wait node finds for you which wait times are the most efficient and productive for your automated flow, with the help of magnews AI.
Read the article dedicated to Q Wait.
‘Wait for message activity": wait for contact action
The session waits for a certain time and continues with two different paths depending on whether or not the contact has performed an action on the indicated message during the indicated period.
Example: we wait for the contact to convert a communication with an invitation for up to 2 days. If they convert we send them a message thanking them for their participation, if they do not convert we try to send them a new message.
Events on the message
The events we can expect on the message are:
- Converts: if the contact converts, e.g. subscribes, we can send them a welcome.
- Clicks
- Opens or clicks: in this case we mean at least one of the two events
- Records a bounce: if the contact did not receive we could send him the message again
- It is sent to them: depending on how the flow is structured, we may not necessarily have sent them a specific message.
What message
On which message do we expect the contact to perform an action?
- Last: is the last message sent to the contact in the session before entering this node. If it is sufficient for you to know that the contact has interacted with a message from the automated flow, without distinguishing which one, you can use this option. For example, if you sent messages using the Q Message node, you cannot know which message was sent to them.
- Specific: in this case choose the message you wish to verify.
‘Wait for response": wait for the contact to fill in
The session waits for a certain time and continues with two different paths depending on whether or not the contact has responded to a landing page in the given period.
You have created a survey to which you want your contacts to respond. You can use this node to wait for a response and if the survey is not filled out within the maximum period, you can send the invitation to fill it out again.
To use the node, you only have to indicate:
- the landing page you are waiting for, selecting it from those in your account
- the maximum waiting time.
Remember to activate the landing page before activating the automated flow.