> For the complete documentation index, see [llms.txt](https://docs.gallabox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gallabox.com/bots/bot-utilities/delay.md).
# Delay
> **Who can use this Card?**
>
> * Gallabox Users having permission to either build and deploy bots or manage bots.
> * Available on Scale and Pro Plans.
There might be a situation when you would like to wait more than seconds for the user's response and then send the next message.
This is where the **Delay Card** in Gallabox comes into picture. You can add a delay of some **seconds**, **minutes** or **hours.**
Delay Card
For Instance, if you have asked the user for any document, it is recommend to use the **Delay card** after the **Send card** to keep the conversation flowing. Refer to the below screenshot for more clarity.
Delay Card in a Chat-flow
In the above screenshot, the flow is extended accordingly for [**On Completion**](#user-content-fn-1)[^1] and for [**On Interrupt**](#user-content-fn-2)[^2] conditions.
Like the example discussed above, you could use the Delay Card as per the chat-flow you are building.
{% hint style="info" %}
When using Delay Card, please make sure the session TTL is always greater than the time in the Delay Card.
*For Example, If the session TTL is kept 3 minutes, and the time in Delay is set as 15 minutes, then the chat-flow will follow the session TTL, meaning the chat will drop after 3 minutes.*
{% endhint %}
[^1]: Success Condition: When you don't receive any message from the user's end during the time set in Delay Card.
[^2]: Failure Condition: When you receive the message from the user before the Delay time is over.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.gallabox.com/bots/bot-utilities/delay.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.