The Wait Component: Add Natural Pauses Between Automated DMs
Wait pauses a message automation flow for 1 to 60 seconds, then carries on by itself. Here are its settings, an example flow and the mistakes people make most often.
In this post
Wait is the component that pauses a message automation flow for 1 to 60 seconds and moves on to the next step by itself when the time is up. You use it to put a pause between two automated messages. Instead of a pile of messages landing at once, the customer sees something that feels more like a real chat.
What is Wait for?
If your flow has three messages in a row, Instagram shows them almost at the same moment. The second one arrives before the customer has read the first. Sometimes that's fine. But if you send a file or an image and then ask "Did you get a chance to look?", having the question arrive with the file feels odd.
Wait sits between the two steps. When the flow reaches Wait, it pauses for the time you set, then moves on to the connected step. It doesn't expect anything from the customer and doesn't send anything.
Typical uses:
- Waiting a few seconds after sending a catalog PDF or a product image before asking a question.
- Splitting a long piece of information into two short messages with a pause between them.
- Leaving a short pause after the welcome message instead of sending the menu right away.
Settings
Wait has a single setting: Wait Time (Max: 60 s).
| Setting | Options | Limit |
|---|---|---|
| Presets | 5 s, 10 s, 30 s, 60 s | |
| Slider | Any value from 1 to 60 | At least 1, at most 60 seconds |
| Number box | Type the time in seconds yourself | At least 1, at most 60 seconds |
When you first add the component to the canvas, the time is set to 10 seconds. Clicking a preset, moving the slider or typing a number all change the same setting.
Wait has one input and one output. Just connect the output to the next step.
The right time depends on the message before it. After a short text, 3 to 5 seconds is enough. If you sent an image or a PDF, around 10 seconds gives the customer time to open it and take a look.
Example flow: send the catalog, then ask
Let's build a flow that sends your PDF catalog when a customer writes "catalog", waits a little, then asks what they're looking for.
- Trigger: Manual Trigger with the words "catalog" and "price list".
- Text Message: "Sending you our catalog now." Don't add quick replies, so the flow carries on by itself.
- File: your catalog PDF. File sending has to be included in your plan.
- Wait: 10 s. Gives the customer time to open the file and start browsing.
- Text Message: "Did anything catch your eye? How can we help?" Add Quick Replies to this message, for example "Shipping info" and "I have another question". Connect each one to the right step.
- End Conversation: connect it to the last steps.
What the customer sees:
Catalog
Sending you our catalog now.
Autumn Catalog.pdf
10 seconds later
Did anything catch your eye? How can we help?
Before saving the flow, try it with Preview in the editor. When the preview reaches Wait, it shows the time on a countdown, so you can see how far apart the messages will arrive.
Wait vs. End Conversation
Both components have a time setting, so they're easy to mix up:
- Wait pauses in the middle of the flow. When the time is up, the flow continues.
- End Conversation ends the flow. Its Retrigger Cooldown is how long has to pass before the same person can start this flow again.
If you want to stop a customer from triggering the same flow over and over in a short time, the setting you need is in End Conversation. We cover it in our first message automation guide.
Common mistakes
- Using Wait to wait for a reply. Wait doesn't wait for the customer to write. If you want the flow to follow the customer's choice, use quick replies or a Button Menu.
- Setting a long time. 60 seconds is a long time in a DM. The customer may have left the chat. In most cases 3 to 10 seconds is enough.
- Using it for follow-ups. The longest wait is 60 seconds. You can't build a "remind them tomorrow" scenario with Wait. Meta's messaging window limits messages like that anyway; the details are in our post on Meta's 24-hour rule.
- Stretching long message chains with Wait. The editor won't save a flow that sends more than 10 automated messages in a row without waiting for a reply from the customer. Wait breaks the chain for that count, but the customer still gets a lot of messages back to back. Splitting a long explanation with a button menu follows the rule and is easier to read.
- Leaving the output unconnected. If nothing is connected after Wait, the flow stops there and the customer gets no further messages.
Browse the other message automation components on our Instagram DM automation page.
Frequently asked questions
Can I use Wait to send a reminder the next day?
No. The longest wait is 60 seconds. Wait is meant for short pauses between messages in the same conversation.
What happens if the customer writes something during a Wait?
Wait doesn't wait for the customer's reply. When the time is up, the flow carries on by itself. If you want the flow to follow the customer's answer, add quick replies to a Text Message or use a Button Menu.
Can I use more than one Wait in a flow?
Yes. Each Wait runs with its own time. We still recommend keeping the pauses short so customers aren't left waiting to read your messages.
