Q&A Node

⚠️ This feature is in public beta. You're encouraged to explore and share feedback. It’s production-ready, but may change as we improve based on real-world use.

This node requires the Knowledge AI tab to be set up before use. Learn more here.

Introducing Knowledge AI ✨

Looking to build an intelligent virtual assistant powered by your own knowledge base?

Knowledge AI is a powerful feature within AI Studio that allows your Virtual Assistant (VA) to generate intelligent, accurate answers using your own content. Rather than relying on predefined intents and entities, Knowledge AI enables direct use of uploaded or linked materials, known as Sources, to respond contextually to user questions.

Used in conjunction with the Q&A Node, Knowledge AI taps into a streamlined system built on RAG (Retrieval-Augmented Generation), combining semantic search with Google Gemini’s large language models (LLMs) to generate relevant responses.

What is the Q&A Node?

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.

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 lets you reuse knowledge content without cross-VA conflicts - ideal for scaling VAs efficiently.

Setting Up the Q&A Node

To configure the Q&A node:

1

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.

Heads Up! ⚠️

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.

2

Assign the User Query Parameter

From the User Query parameter dropdown, pick the parameter that contains the user’s input. This will be processed by Knowledge AI.

3

Capture the Response

Under the Response dropdown, select the parameter to store the generated answer. This parameter can then be passed into Speak/Send Message or Collect Input nodes.

Heads Up! ⚠️

There may be a 2 - 5 second delay while the system processes the query and generates the response.

Configurations

Waiting Time

This determines how long your VA will wait for a response.

  • Default: 3 seconds

  • Customizable range: 2 - 10 seconds

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.

Answer Length (Optional)

Choose whether the response should be:

  • Shorter: Good for simple answers

  • Longer: Best for complex, context-heavy queries

Minimum: 20 words - no upper limit.

Pro Tip 🔥

Longer answers increase accuracy but also increase latency. Always test what works best for your use case.

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.

Managing Outputs

The Q&A Node has three possible outcomes:

  • Success: A valid answer was found. The response is saved to the selected parameter.

  • Don’t know: No relevant answer could be generated.

  • Failed: System error or timeout occurred.

💡 Always design for all three paths to ensure a smooth user experience.

Heads Up! ⚠️

Changes to the Q&A Node, its Source, or Index will immediately affect live behavior. No need to re-publish. Always test thoroughly before updating production flows.

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 Q&A node after collecting more context

Heads Up! ⚠️

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 to allow the VA to pivot between topics.

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.

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. Then build and scale Q&A nodes across your assistant flows to maximize their value and performance.

PreviousListenNextAdvanced

Last updated

Was this helpful?