The contact will stay on the node where they were when they bounced, be it on email or SMS. Read more about bounces here.

If a contact is set to ‘off’, all messages to them will be paused across the platform. If they’re in a workflow, they’ll stop on the node they were on and won’t move any further through the workflow.

They will start receiving the messages again from where they are in the workflow. Depending on the time that has passed since they unsubscribed, this may not be the same node that they were on when they unsubscribed.

Un-enrolment triggers can remove contacts from a workflow based on criteria that you set. Click here to learn how to add an unenrolment trigger to the workflow.

If you delete a contact, they get removed from your list and any workflows they were on.

Each delay node counts from the last action.

When you re-launch the workflow, it will pull the contacts into the delay node, and start counting as the contacts are pulled onto the node.

The system will recalculate the remaining period for each contact. So if you change a two-day delay to three days when your contacts are on day one, they will have two days left on the delay.

Contacts who don’t meet conditions in a workflow will flow through the “No” path.

There are many reasons out of our control that affect delivery rates in web push, and as a result, we can’t guarantee delivery.