# Q\&A Node
{% hint style="info" %}
#### [Introducing Knowledge AI](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai) ✨
### Building an Intelligent Virtual Assistant with Knowledge AI
**Looking to create a smart virtual assistant using your own data?** Knowledge AI in AI Studio empowers your Virtual Assistant (VA) to generate accurate answers based on your content. Instead of depending on predefined intents and entities, **Knowledge AI** directly utilizes your uploaded or linked materials, called **Sources**, to respond contextually to user inquiries.
When used with the **Q\&A Node**, **Knowledge AI** leverages a system based on RAG (Retrieval-Augmented Generation). It combines semantic search with Google Gemini’s large language models (LLMs) to produce relevant answers efficiently.
{% endhint %}
{% hint style="danger" %}
*This node requires the **Knowledge AI** tab to be set up before use. Learn more* [*here*](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai)*.* 🔍
{% endhint %}
***
The **Q\&A node** allows the Virtual Assistant to access the Indexes you’ve created in the Knowledge AI tab, enabling smooth and informative conversation flows with minimal build time.
It is designed to dynamically generate responses by pulling from your uploaded **Sources** via an **Index**, using **Knowledge AI’s RAG (Retrieval-Augmented Generation)** pipeline, which includes Vonage’s proprietary **Semantic Search** and **Google Gemini's LLM** response generation.
{% hint style="success" %}
#### Pro Tips 🔥
#### Managing Indexes Across Multiple Q\&A Nodes and VAs
* You can use **multiple Q\&A nodes** in the same VA to handle different knowledge domains.\
→ Assign a **different Index** to each Q\&A node.
* **Indexes are restricted to one VA** per API key.\
→ If you can’t find an Index in the dropdown, check if it's already in use by another VA.
* Want to use the **same content across multiple VAs** under the same API key?\
→ **Duplicate the Index** and assign it to the other VA.
\
💡 Duplicating [Indexes](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai#group-your-sources-to-create-indexes) lets you reuse knowledge content without cross-VA conflicts; ideal for scaling VAs efficiently.
{% endhint %}
***
## Setting Up the Q\&A Node
To configure the Q\&A node:
{% stepper %}
{% step %}
### Select an Index
Choose one Index that will serve as the Knowledge Base for that node. Only Indexes created under the API key for the selected VA — and not used elsewhere — will appear in the dropdown.
🔍 *Learn more about grouping your Sources into Indexes* [*here*](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai)*.*
{% hint style="warning" %}
Each **Q\&A node** is restricted to one Index, but you can use multiple Q\&A nodes within a single VA to access different Sources across different parts of the flow.
{% endhint %}
{% endstep %}
{% step %}
### Assign the User Query Parameter
Select the parameter from the User Query dropdown that captures the user input, which will then be processed by Knowledge AI.
{% endstep %}
{% step %}
### Capture the Response
Under the Output Parameter dropdown, select the parameter to store the generated answer. This parameter can then be passed into Speak/Send Message or Collect Input nodes.
{% hint style="warning" %}
There may be a 2- 5 second delay while the system processes the query and generates the response.
{% endhint %}
{% endstep %}
{% endstepper %}
***
## Configurations
### Handle Follow-Up Questions *(Optional)*
{% hint style="warning" %}
This setting is available in both the **Q\&A Node** and the [**Index Tester**](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai#test-your-indexes). It controls how **Knowledge AI** interprets user queries within a conversation.
{% endhint %}
The **Handle follow-up questions** toggle allows **Knowledge AI** to understand and respond to follow-up queries based on the ongoing conversation, without requiring the user to restate previous context.
{% columns %}
{% column width="50%" %}
#### 🟢 When **ON**
* Enables contextual understanding for follow-up questions.
* Uses session conversation history to interpret meaning.
* Adds 300–1000 ms latency as Knowledge AI retrieves and processes context.
{% endcolumn %}
{% column width="50%" %}
#### ⚪ When OFF
* Each query is processed independently.
* No additional latency.
* May lead to “I don’t know” responses if context is required.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
#### ➡️ Example 1: Handle Follow-Up Questions *ON*
**End User:** What is the price of an economy ticket?\
**VA:** It is $1000.\
**End User:** What are its cancellation charges?\
**VA:** Cancellation charges are $250.
Knowledge AI uses the conversation history to link “its” to “economy ticket.”
{% endcolumn %}
{% column %}
#### ➡️ Example 2: Handle Follow-Up Questions *OFF*
**End User:** What is the price of an economy ticket?\
**VA:** It is $1000.\
**End User:** What are its cancellation charges?\
**VA:** Sorry, I don’t know.
With context handling disabled, the VA treats this as a new question and cannot infer context.
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
#### ➡️ Example 3: Extended Context Example
🟢 **Handle Follow-Up Questions *****ON***\
**End User:** *What animals are allowed on a plane?*\
**VA:** Passengers can bring up to two animals (dogs or cats) in approved containers, either in the cabin or cargo hold.\
**End User:** Give me more details!\
**VA:** Containers must not exceed 118 cm (55 × 40 × 23 cm) or 47 in (22 × 16 × 9 in), with a total weight of 8 kg. They must be leak-proof and lined with absorbent material.
{% endcolumn %}
{% column %}
⚪ **Handle Follow-Up Questions *****OFF***\
**End User:** *What animals are allowed on a plane?*\
**VA:** Passengers can bring up to two animals in approved containers.\
**End User:** Give me more details!\
**VA:** Sorry, I don’t know.
{% endcolumn %}
{% endcolumns %}
{% hint style="success" %}
#### Pro Tip 🔥
Keep this toggle **ON** 🟢 for smoother, more human-like interactions.
Turn it **OFF** ⚪ if each query is unrelated, or if lower latency is required.
⚠️ Always **test your VA flows** to understand how context affects accuracy and response time.
{% endhint %}
{% hint style="info" %}
**Accessing "Handle Follow-Up Questions" Feature in Index Tester**
You can access this toggle in the **Index Tester** by clicking the **gear icon ⚙️** at the top-right corner of the interface.
🔍 Learn more about how to test your Sources using the **Index Tester** [here](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai#test-your-indexes).
{% endhint %}
### **Answer Length *****(Optional)***
Use Answer length to control how detailed Knowledge AI’s responses should be.
Choose whether the response should be:
* **Shorter**: Good for simple answers
* **Longer**: Best for complex, context-heavy queries
Minimum: 100 characters/ 20 words - no upper limit.
{% hint style="danger" %}
**Longer answers increase accuracy but also increase latency**. Always test what works best for your use case.
{% endhint %}
{% columns %}
{% column %}
If **not** defined, **Knowledge AI** automatically determines the best answer length based on the query and the Knowledge Base.
{% endcolumn %}
{% column %}
If defined, **Knowledge AI** treats it as a *soft constraint*. The response will generally fall within a small range of the specified value.
{% endcolumn %}
{% endcolumns %}
{% hint style="warning" %}
Exact control is **not guaranteed** due to the non-deterministic nature of the LLMs used by Knowledge AI.
{% endhint %}
{% hint style="info" %}
The **Answer Length field** is disabled in both the **Q\&A Node** and the **Index Tester** when **Output mode** is set to [*Search*](https://studio.docs.ai.vonage.com/voice/nodes/basic/q-and-a-node#search)*.*
{% endhint %}
###
### **Response Guidelines *****(Optional)***
You can set the tone, format, and boundaries of responses with custom instructions.
* **Tone**: Formal, friendly, concise, etc.
* **Topic Restrictions**: Prevent the assistant from veering off-course.
* **Custom Guardrails**: Rules for responses based on testing feedback.
* **Company-Specific Terminology**: Ensure branding consistency (e.g., use "Vonage" instead of "we").
These guidelines help you match your assistant’s voice to your brand and use case.
🧩 Best Practices on Response Guidelines
Use **Response Guidelines** to define how Knowledge AI should respond — including tone, structure, and topic scope. This helps ensure responses are clear, accurate, and aligned with your brand.
#### 1. Keep It Simple
Start with 3–4 key rules. Too many constraints can confuse the model.
**Avoid repeating system logic:**
* **Do not define the "Don't Know" response:** The logic for vague or missing answers is pre-defined in the backend. Avoid instructions like: "If the input is vague, say 'I'm not sure'" or "Only provide a found response".
* **Do not define the Role:** The Q\&A node's role is also pre-defined. Avoid instructions like: "You are a virtual agent for XYZ handling ABC topic".
#### 2. What to Include
When writing custom instructions, focus on these areas:
| Category | What to Define | Example |
| ---------------- | ---------------------------------------- | ------------------------------------------------------------------------ |
| **Tone** | Choose the tone and style for responses. | Formal, friendly, empathetic, or instructional. |
| **Topic Scope** | Define what’s in or out of scope. | “Answer only questions about product and billing.” |
| **Terminology** | Specify brand or company language. | Use “Vonage” instead of “we.” |
| **Custom Rules** | Add guidance based on testing. | Adjust clarity, phrasing, or coverage. Don't include long lists of URLs. |
#### 3. Write Clear Instructions
Give examples of **correct** and **incorrect** responses so Knowledge AI understands your intent.
**Instruction:** Summarize retrieved information in a clear, neutral, and concise tone.\
✅ *Correct behavior:* Studies show that moderate protein intake and reduced refined carbohydrates can lower diabetes risk.\
❌ *Wrong behavior:* Wow, carbs are terrible! Everyone should stop eating rice immediately. (Subjective, emotional, and exaggerated tone).
#### 4. Test and Refine
Review outputs and adjust your guidelines based on user testing or QA feedback.
{% hint style="warning" %}
Knowledge AI operates in **single-turn mode**:
* The Q\&A Node processes one input and returns one output.
* After returning the response, the node is marked as *completed*.
* It does not support back-and-forth conversation. If you want to reuse the same Q\&A Node, add a **loop** in your Virtual Assistant flow.
🔍 [Learn more about how to set up your Q\&A node in your VA flow here. ](https://studio.docs.ai.vonage.com/voice/nodes/basic/q-and-a-node#using-the-q-and-a-node-in-your-va)
{% endhint %}
{% hint style="info" %}
The **Response Guidelines field** is disabled in both the **Q\&A Node** and the **Index Tester** when **Output mode** is set to [*Search*](https://studio.docs.ai.vonage.com/voice/nodes/basic/q-and-a-node#search)*.*
{% endhint %}
### **Waiting Time**
This determines how long your VA will wait for a response.
* **Default**: 3 seconds
* **Customizable range**: 2 - 10 seconds
{% hint style="success" %}
#### Pro Tip 🔥
* **Shorter wait times** feel more natural in human conversation.
* **Longer wait times** reduce API timeout risk but may affect flow pacing, especially for Voice channels.
{% endhint %}
***
## Managing Outputs
The **Output mode** setting defines how **Knowledge AI** processes and returns information from your Knowledge Base.
There are two modes available:
### ➡️ **Search & Respond**
This is the **default output mode** used by Knowledge AI.
In this mode, Knowledge AI retrieves information and generates a refined response that can be sent directly to the end user.
🧩 Configure "Search & Respond" Output Mode
#### How It Works
1. When a user query is received, Knowledge AI performs a **knowledge search** and retrieves the most relevant information from your Knowledge Base (the *search output*).
2. The search output is then passed to a **Language Model (LLM)** for processing.
3. The LLM filters, summarizes, and structures the information into a single, concise response.
4. The resulting **text answer** is sent back to the end user during the Virtual Assistant session.
#### Output Characteristics
* Responses are typically **100–500 characters** long.
* Answers are short, structured, and optimized for clarity.
* Best suited for customer-facing conversational use cases.
{% hint style="success" %}
#### Pro Tip 🔥
Use **Search & Respond** when you want **Knowledge AI** to handle both the retrieval and generation of responses automatically.
{% endhint %}
### ➡️ **Search**
The **Search** mode performs a knowledge search and retrieves relevant information without generating a summarized response.
This mode is useful when you want to access the raw search results for further processing by other systems or AI components.
🧩 Configure "Search" Output Mode
#### How It Works
1. When a user query is received, Knowledge AI performs a **knowledge search** and retrieves the top relevant text chunks (the *search output*).
2. The retrieved content can then be passed to another AI process, workflow, or agent for flexible handling.
This mode is often used when **Knowledge AI** acts as a **tool within an AI Agent** or when minimizing latency is a priority.
#### Output Characteristics
* The search output consists of multiple **text chunks**, typically ranging from **250–2500 characters** each.
* The raw text may include long passages or multiple paragraphs.
* It is **not recommended** to send this output directly to end users.
* Using this mode can help **reduce response latency** and improve **AI Agent performance**.
{% hint style="danger" %}
When **Output mode** is set to *Search*, the configuration fields **Answer length** and **Response guidelines** are disabled in both the **Q\&A Node** and the **Index Tester**.
{% endhint %}
***
## ⚙️ Diagnosing Knowledge AI Outputs
If Knowledge AI gives incomplete or incorrect answers, check its behavior manually using **AI Studio Reports** or upcoming **Knowledge AI Insights**.
#### Common Issues and Fixes
| Problem | Likely Cause | Recommended Action |
| -------------------------------- | --------------------------------------------- | ------------------------------------------------------- |
| **Ambiguous user question** | Query unclear or incomplete. | Ask the user to clarify or rephrase in the VA flow. |
| **Outside Knowledge Base scope** | The index lacks relevant data. | Add new, relevant material to the Knowledge Base. |
| **Search issue** | Information exists but isn’t being retrieved. | Review and optimize source formatting. |
| **Partial or inaccurate answer** | Model retrieved but misunderstood content. | Improve Source structure or revise Response Guidelines. |
***
## Using the Q\&A Node in your VA
The **Q\&A node** is most effective when used as part of a broader conversational setup. Examples include:
* Collect input ➜ Run Q\&A node ➜ Return result
* Use as a fallback if other nodes fail
* Route back to the Q\&A node after collecting more context
{% hint style="warning" %}
The **Q\&A node** doesn’t remember previous answers. Add context before sending the query if needed.
You can also use the [**Context Switch node**](https://studio.docs.ai.vonage.com/voice/nodes/flow-control/context-switch) to allow the VA to pivot between topics.
{% endhint %}
{% hint style="success" %}
#### **Pro Tip 🔥**
If one **Index** doesn’t return an answer, route the “Don’t Know” path to another **Q\&A node** with a different Index.
{% endhint %}
***
## What's next
Now that you understand how to configure and optimize the **Q\&A node**, you're ready to start building experiences that not only respond but respond smartly.
👉 **Next Steps:** [Ensure your Knowledge AI setup is complete and thoroughly tested](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai). Then build and scale Q\&A nodes across your assistant flows to maximize their value and performance.
### 🔍 Related Links
* [Knowledge AI Overview](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai#smarter-brand-safe-answers-with-generative-ai)
* [Index Tester](https://studio.docs.ai.vonage.com/ai-studio/knowledge-ai#create-indexes-group-your-sources)
---
# 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://studio.docs.ai.vonage.com/voice/nodes/basic/q-and-a-node.md?ask=
```
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.