Connect a Knowledge Base to a Voice AI Agent in Sparkforge

Knowledge Base Integration for Voice AI lets you attach a specific knowledge base to each Sparkforge Voice AI agent. When a caller's spoken input matches the trigger prompt you define, the agent searches the knowledge base and returns the most relevant answer.

What it does

• Per-agent knowledge: link a different KB to each agent so responses match the agent's domain.
• Trigger-based activation: the agent only queries the KB when the caller's input matches your prompt.
• Real-time answers: the agent fetches answers as the conversation happens.
• Instant content updates: edits to the KB take effect on the next call — no agent reconfiguration.
• Scales cleanly: manage multiple agents and KBs without custom logic.

How to set it up

Step 1 — Open Voice AI

Sign in to Sparkforge. Click AI Agents, then Voice AI.

Step 2 — Open or create the agent

Create a new agent or click the three-dot menu next to an existing one and select Edit.

Step 3 — Open Agent Goals

1. Click the Agent Goals tab.
2. Under Select knowledge base, pick an existing KB or click Create New.

Match the KB to the agent's role — sales, product support, intake, etc.

Step 4 — Write the trigger prompt

In the When to use this knowledge base field, describe exactly when the agent should query the KB. Example:

Use this knowledge base when the caller asks about the business, services, products, contact details, or anything else that requires the business wiki for an accurate answer.

Step 5 — Save

Click Save. The KB is now linked to the agent.

Best practices

Manage multiple knowledge bases

• Build separate KBs for sales, support, and product info.
• Attach the right KB to each agent so the answers stay focused.

Tune your trigger prompts

• Use clear language that matches how callers actually phrase questions.
• Test variations and keep the prompt that fires reliably without misfiring.

Keep content current

• Review articles and FAQs on a schedule.
• Edits propagate to live calls instantly — no extra config.

Monitor performance

• Track how often the KB triggers and the quality of the responses.
• Use call logs to spot gaps in the KB and refine prompts.