# Checkpoint

Setting up checkpoints:

1. Place checkpoint node at key conversation points
2. Configure **"Wait for user input"** if interaction is needed
3. Connect both user input and signal paths if required
4. Create paths for different continuation scenarios
5. Link to appropriate next steps in the flow

Example: As shown in the screenshot, checkpoints are used after intent recognition to maintain conversation state:

<figure><img src="/files/zZIePYmB2XP1O1rfY52C" alt=""><figcaption><p>Example of using Checkpoints</p></figcaption></figure>

```
Intent matcher identifies topic:
- Pricing questions
- Troubleshooting needs
- Upgrade requests

Each path has Checkpoint:
- Wait for user input enabled
- Handle both user responses and signals
- Continue with appropriate LLM responses
- Maintain context through the interaction
```

Common use cases:

* Maintain conversation state during multi-step processes
* Handle interruptions gracefully
* Create conversation branches
* Manage form-filling and data collection sequences

{% hint style="info" %}
**Important considerations:**

* Consider both user inputs and system signals
* Consider using "Go to flow" for more complex paths
* Test checkpoint returns thoroughly
* Plan checkpoint connections carefully
  {% endhint %}


---

# 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://docs.virbe.ai/dashboard-management/conversation-flows/nodes/flow-control-nodes/checkpoint.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.