> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/automation-apps-blocks/time-delay-block.md).

# Time Delay Block

The **Time Delay** block pauses the flow before sending the next message. It helps make conversations feel more natural and is also useful for follow-ups, lead nurturing, and onboarding sequences.

1. Go to **Chatbot** → Click **Create Bot Flow**.
2. Select **WhatsApp Chatbot**, set **Trigger + Channel**, and save.
3. Add your first **Message** node (e.g., welcome message).
4. Click **Add Node** → **Add Automation App** → Search **Delay**.
5. Select one of the delay types:

#### Option A: Time Delay (Relative)

6. Choose the unit (**seconds / minutes / hours / days / weeks**).
7. Enter the delay time (example: **45 minutes**) and save.
8. Add the next message — it will be sent after the delay.

#### Option B: Time Delay (Fixed Date & Time)

9. Select **Time Delay – Fixed Date & Time**.
10. Enter the exact **date + time** (DD/MM/YYYY + time format) and save.
11. Add the next message — it will be sent at the scheduled date/time.

This is how you control message timing to create well-timed, human-like bot conversations.

{% embed url="<https://youtu.be/85o5XKBBpyY?si=ebVvd0V_E07OFOaL>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/automation-apps-blocks/time-delay-block.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.