Skip to main content
Recurring follow-ups

How to use the follow-up feature to create a recurring nudge until a task is complete

Melita Gandham avatar
Written by Melita Gandham
Updated over 3 months ago

If you wish to set a recurring follow-up, you will need to set up a series of messages that contain a follow-up message part in each one. Think of it as a chain of follow-up messages.

Usually, a follow-up is used as a one-off message to get a user to complete a task or to follow up a message with extra content/a question. If you're building a flow that requires the user to complete a mandatory task, then a recurring follow-up is the perfect way to keep reminding the user to complete the flow.

In order to build a recurring follow-up, you will be using the following two features:

• Follow-ups: this will allow you to link to your next message after a specific period of time

• Attributes: specific attributes will be used in your follow-up message part and in your message content to track if the user has completed the task

How it works

To build a recurring follow-up, you will need to utilise "Cancel follow-up if..." in the modal. Your set up should look something like below:

So, we can see in the screenshot above the a follow-up nudge will be sent to a user to complete a task 1 week after this message has been triggered, and the follow-up nudge will only be sent if the bot user hasn't hit the "task completed" attribute to prove they completed what they need to.

At this point of the set up, the follow-up message would only be sent once. To make a recurring follow-up, there are two routes you can choose.

You can do an infinite message loop which stops when the attribute which shows the the flow has been complete is hit. So for example:

Message 1, sent to everyone: "Please complete this task" (contains follow-up message part, which cancels follow-up if the complete task attribute is hit)

Message 2, only sent to those who didn't hit the complete task attribute: "You did not complete this - please do so now"

In Message 2, you should add the follow-up message as Message 2 again, so that it keeps looping depending on if the attribute is still set. This is definitely a sure fire way of getting users to finish a task, but it can get repetitive after a while. You can find out how to cancel a infinite follow-up in the "Cancelling a recurring follow-up" below.

Alternatively, you can build a follow of follow-ups that escalates a message to the manager if a task is not completed in a timely manner. It would look like this:

Message 1, sent to everyone: "Please complete this task" (contains follow-up message part, which cancels follow-up if the complete task attribute is hit, and links to Message 2)

Message 2, only sent to those who didn't hit the complete task attribute: "You did not complete this - please do so now" (contains follow-up message part, which cancels follow-up if the complete task attribute is hit, and links to Message 3)

Message 3: "You still have not completed this task"

At this point, Message 3, you can ask the user to get in touch if they have issues, escalate their info to their manager.

Cancelling a recurring follow-up

You can easily cancel a recurring follow-up in the following two ways:

• upload user attributes: you can use the User Attribute Uploader in the platform to set the follow-up's user attribute to be completed so that the bot knows to stop sending the pings.

• by sending out a broadcast to your remaining audience, which contains a set attribute message part e.g. the set attribute message part will contain the attribute that was in the set up of your follow up. You can then broadcast this message out as a "silent broadcast" (the bot user won't be notified as there is no content per se). Or you could also send a message which tells the user that they will stop receiving nudges despite them not completing the task.

Silent broadcast set up:

Broadcast including content:

If you have any questions around setting up recurring follow-ups, then please reach out to us using the intercom widget!

Did this answer your question?