Q Wait: after the Q Split node (discover also Q Split), another 'Q' node at your disposal for more efficient automated flows. The Q Wait node also revolutionises your automated flows, deciding for you which waiting times are most effective and productive.
Let's start with an example
An eCommerce company has designed and configured a flow for retrieving the abandoned shopping carts of its customers.
But what is the best waiting time? That is, how long should we wait in order not to be too persistent but, at the same time, not to miss the opportunity to turn the full shopping cart into a successful purchase? eCommerce is undecided whether it will be preferable to wait 1 hour, 4 hours or 1 day to convert more.
We then configure the node with 3 different waiting times. You can choose from a minimum of two timings to a maximum of 7 different timings.
The automated flow is self-assessing and directs the most sessions progressively to the waiting time that performs best.
Please note that when creating an automated flow from magnews you can use one of the many available templates, including those for abandoned shopping carts connected to Magento, Prestashop and Shopify eCommerce connectors.
How it works
At the initial stage, the node divides the incoming sessions randomly but equally between the different waiting times (e.g. if the node has two timings, 1 hour and 4 hours, the sessions will wait 50% 1 hour and 50% 4 hours).
After a reasonable number of sessions begin to evaluate how the automated flow is going, the percentages with which the sessions are distributed among the waiting times are gradually adjusted so that the majority of sessions converge towards the waiting time that maximises the goal.
How to set up
The Q Wait node is designed to be simple and intuitive to configure:
- Waiting times: choose how many different timing you want to evaluate. The more different timing you enter, the more sessions you will have to wait to see the automated flow self-improve. You can start with 2 or 3 waiting times for your first Q automated flow. Then fill in the proposed table with timing and units (minutes, hours, days).
-
Recalculate outputs: choose according to what you want to evaluate the automated flow. The goal can be: Automated flow success or Number of conversions.
By automated flow success we mean how many sessions ended by positive exiting an exit node.
By number of conversions we mean the number of goal conversions that were made by contacts from the communications sent by the flow. - Conversion goal: if you have chosen to evaluate the success of the automated flow by the number of conversions, you have to choose which goal to evaluate.
Back to our example
If we come back to the example described above, we set:
- Waiting times: 1 hour in the first row, 4 hours in the second row and 1 day in the third row.
- Recalculate waitings: we set the number of conversions, as we want to know which of the two communications generates more conversions, so purchases.
- Conversion goal: we choose the goal that represents purchases.
This results in increased automated flow efficiency, as more and more contacts will wait for the ideal time, thereby optimising our chances of conversion.
As time goes by
The Q Wait node will continue to learn and adapt to the performance of waiting times, automatically adjusting the distribution between different timings. You will see the current distribution percentages within the node at all times.Advantages
The advantage of the Q Wait node is in its ability to learn and adapt. Unlike a static flow that can be inefficient, Q Wait allows you to continuously maximise the conversion or success of your automated flows.You will not have to decide and make assumptions, but the node will decide for you based on realised performance.