# Text

It's the simplest response type, useful when you need a consistent, unchanging message rather than AI-generated text.

#### Setting up text responses:

1. Enter the exact text to be shown (up to 1000 characters)

{% hint style="info" %}
Note: Using exact text responses is faster and completely consistent, but may make interactions feel less natural. Only use in very specific contexts.
{% endhint %}

#### Example: Greet the user

<figure><img src="/files/sw7B1dkIFr5o6ytgo2KE" alt=""><figcaption><p>Example of Text node use</p></figcaption></figure>

{% hint style="info" %}
Consider adding a follow-up Checkpoint node with a "Wait for user input" option enabled to make sure that the user's response will proceed to the next node (could be an Intent Matcher node in the above example).
{% endhint %}

#### Common use cases:

* Legal disclaimers
* Standard greetings
* Error messages
* Instructions
* System notifications

{% hint style="info" %}
I**mportant considerations:**

* Messages never vary - same text every time
* Keep content clear and concise
* Update manually when changes needed
* Consider using LLM Response for more natural interactions
  {% 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/response-nodes/text.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.