> For the complete documentation index, see [llms.txt](https://docs.intelliticks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelliticks.com/ai-builder/nodes/additional/user-input-wait.md).

# Wait

The **Wait** node does nothing. It just stops the execution of the conversational flow. It, however, comes with a timeout feature and can be used to simulate a wait time before pushing new messages to the visitor. &#x20;

{% hint style="info" %}
A wait of a **Wait** node is over if it accepts any kind of input response from the visitor. The input response could be a simple text message sent by visitor. &#x20;
{% endhint %}

### Actions&#x20;

Two types of Actions are available

* **Actions on Entry** - These Actions are executed as soon as the **User Input/Wait** node is reached during a conversation.
* **Actions on Response** - These Actions are executed after the response is received from the end visitor.&#x20;
* **Actions on Timeout** - These Actions are executed if no response is received from the end visitor and the timeout has occurred.

### Timeout

By default, it is set to "**Waits forever**" and the conversation is stuck until the user provides any response.&#x20;

You can also set a fixed timeout. If you have set a fixed timeout, the conversation will wait for the user's response for the specified time. The conversation will move forward if any of the response or the timeout event occurs.&#x20;

You can also set the timeout to "**Does not wait**". This looks weird but it can be used to do some actions without having a node.

&#x20;


---

# 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.intelliticks.com/ai-builder/nodes/additional/user-input-wait.md?ask=<question>&goal=<endgoal>
```

`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.
