Sequences
Last updated
Last updated
Use sequences to automatically send follow up / delay messages to customers. You can send multiple messages with different delays.
give a sequence name
click "Add Message"
edit the settings (see Message Settings below)
choose the sub flow to send
repeat steps 2-4 to add more messages then click "Save"
This is how does the setting window look like:
Messages are sent by order.
For the first message, the countdown begins when users subscribed to the sequence.
For other messages, the countdown begins when the previous message is sent.
For "send anytime", the message will be sent immediately at the end of the countdown.
For "send between", if the countdown ends outside the time range, the message will be kept until the next available time.
Remember to check the timezone issue below.
This can affect the next message because the countdown of the next message begins when the previous one is sent.
Similarly, if you don't want to bother users at weekend, deselect Saturday and Sunday. See the example in the "send between" above.
Remember to check the timezone issue below.
See "Content Type" introduction below.
If you are not sure about which type you should use, keep it default. Although the message might not be sent due to the 24 hours rule, the system will at least help you avoid being banned by Facebook.
If a channel has a timezone in the user's profile like Facebook, when the system check "send between time range" and "send on Monday to Sunday" settings, it's based on users' timezone first. If the user doesn't have a timezone or the channel doesn't support timezone in user profiles, then it's based on the timezone of the workspace.
Messages with type “Other” or without a content type will NOT be delivered to subscribers who interacted with you via Messenger more than 24 hours ago.
Sending messages that do not match the assigned content type may result in your page being suspended or banned by Facebook.
Can contain promotions and it will only send to users who interacted with your bot in the last 24 hours. Confirmed Event Update
Send the user reminders or updates for an event they have registered for (e.g., RSVP'ed, purchased tickets). This tag may be used for upcoming events and events in progress.
Notify the user of an update on a recent purchase such as confirmation of transactions(invoice, receipt) and notifications of shipment status(product in-transit, shipped, delivered, delayed).
Notify the user of a non-recurring change to their application or account.
When you send more than 1 message in your sequence, note that all the messages are sent in order.
In the above screenshot, for example, the "Booked" sub flow will be sent "Immediately" once the user subscribes to this "Appointment Follow Up" sequence. Because the first message begins the count down once the user subscribes.
The next message begins the count down once the previous is sent. Thus, the "Appointment Follow Up" sub flow will be sent 1 day after the "Booked" sub flow is sent.
Make some sub flows to send specifically for your sequences. Please note that each Send Message step has its own "Message Tag". The tag is set to "Other" by default.
Let's say, now it is over 24 hours since the user last interacted with your bot. You choose a non-default content type for a message in your sequence. This setting automatically changes the message tag of the first Send Message step in the sub flow you send.
Later, if the user responds, you are then able to send messages normally with the "default" content type. So, usually, you won't need to change any message tag in your sub flow.
Go "Flow Actions", and you can find the 2 sequence operations.
There are a couple of examples to use sequence, such as
"Event Follow Up" - send confirm message immediately once user registers and follow-up message as reminder or helper
"Get Feedback" - ask for feedback like 2 hours after the user talked to your bot
"Send Coupon" - send coupons when user put something in the cart but doesn't make an order for a long time
Any message sent over 24 hours after a subscriber’s last interaction must have a content type that matches its purpose (in accordance with
