> For the complete documentation index, see [llms.txt](https://docs.virbe.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.virbe.ai/dashboard-management/conversation-flows/nodes/response-nodes/llm-response.md).
# LLM Response
Unlike fixed Text responses, LLM responses adapt to the conversation while following your defined parameters.
#### Setting up LLM responses:
A single LLM Response node can be used to create the Minimum Viable Flow. Simply connect the Start node to a LLM Response with general system instructions. In such a case, there is no need to connect the LLM Response further to any node – each user's input will trigger the Start and the single LLM Response node with all the existing conversation context and the conversation will keep going, naturally.
The simplest flow with LLM Response
1. Select the LLM model to use
2. Provide system instruction (what the response should achieve)
3. Add any additional context beyond the conversation history
Example for filling in the Context:
Additional Context can help guide the LLM to keep the responses under certain limit of words – this makes the responses more brief and dynamic and they are easier for users to follow.
For more complex flows:
{% hint style="info" %}
If you plan. to add follow-up nodes after LLM Response, consider using a Checkpoint (with "Wait for user input) option enabled) to take the next user's input from there. Otherwise, LLM Response does not wait for user's input and any subsequent nodes will be executed immediately.
{% endhint %}
Example of a complex flow with LLM Responses
#### Common use cases:
* Natural conversations
* Dynamic responses to queries,
* Contextual explanations
* Personalized interactions
* Complex information delivery
* Follow-up discussions
{% hint style="info" %}
**Important considerations:**
* Clear instructions guide better responses
* Additional context helps predictability
* Conversation history is included automatically
* Different models may respond differently
* Test responses with various inputs
* Monitor response quality and appropriateness
{% endhint %}
---
# 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.virbe.ai/dashboard-management/conversation-flows/nodes/response-nodes/llm-response.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.