# Stay in Session Block

The **Stay in Session Block** is used to keep the conversation active within the automation. Unlike other blocks, it does not send messages, collect data, or route the user to another step. Instead, it ensures that the current session remains open so the user can continue interacting with the bot.

Normally, once a flow is completed, the session may end or expire. By using the **Stay in Session Block**, you instruct the system to keep the conversation active and allow further interaction without restarting the automation.

#### How to Use the Stay in Session Block

1. Open your **Chat Flow**.
2. Click **Add Node**.
3. Go to **Native Tools**.
4. Select **Stay in Session**.

Once added, the block will automatically keep the conversation session active.

#### Why Use the Stay in Session Block

This block is useful in scenarios where you want the user to continue interacting with the automation after completing a flow.

For example:

* A user checks **pricing details** and may want to ask additional questions.
* A user selects a **service** and might explore other options.
* You want the user to **trigger other keywords** without restarting the flow.

#### Common Use Cases

You can use the **Stay in Session Block** when:

* You expect **follow-up questions** from users.
* You are building **conversational funnels**.
* You want **ongoing engagement** within the chat.
* You do not want the automation to terminate after completing a flow.

The **Stay in Session Block** helps maintain continuity in conversations and ensures a smoother, more natural automation experience.

{% embed url="<https://www.youtube.com/watch?v=jA4-nY6i7DQ>" %}


---

# Agent Instructions: 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:

```
GET https://helpdocumentation.gitbook.io/user/bot-builder/stay-in-session-block.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.