Passer au contenu
Guides 7 novembre 2026 9 lecture minimale

How to Build a Knowledge Base for a Voice Agent

What to upload so an AI voice agent answers correctly: which documents first, how to write facts for the ear, where prices belong, and how to keep it current.

D
7 novembre 2026

Réponse rapide

Upload the documents callers ask about most: hours, services, policies, locations and booking rules. Write each answer first, one fact per paragraph, under a question-style heading, because the agent retrieves passages by semantic search. Keep prices in the service catalogue, not in prose, and give every document an owner and a review date.

A voice agent is only as useful as what it knows. If the hours in a document are out of date, the agent will confidently say the wrong hours to a caller who will act on it. This guide covers what to upload, how to write it so a spoken answer comes out right, and how to keep it correct after launch. The features described here, document upload, semantic search, the price-truth guard and the service catalogue, are in Agent Studio et le agent vocal IA. This guide uses no outside statistics, only how the product works and a practical routine.

What the knowledge base does, and what the prompt does

Lives inWhat it holdsExample
Prompt and personaHow the agent behavesOne question at a time; confirm before booking; offer a person when unsure
Base de connaissancesWhat the business saysOpening hours, cancellation policy, what to bring
Catalogue de servicesServices and pricesThe amount for each service
CalendrierDisponibilitéFree times, checked live on the call

Change a document and you have changed what the agent knows, without touching a script. That is the point of keeping facts here. For writing the behaviour side, see how to write a prompt for an AI voice agent.

Which documents to upload first

  1. Hours and holidays. Regular hours, public holiday changes, and what happens outside hours.
  2. Services. What each service is, who it suits, and how long it takes. Prices go in the catalogue.
  3. Policies. Cancellation, rescheduling, late arrival, payment methods accepted, refunds.
  4. Locations. Address, parking, landmarks, how to find the entrance.
  5. Booking rules. How far ahead people can book, what is needed for a first visit, how the rendez-vous et rappels flow works.
  6. Common questions. The twenty questions your reception answers most.

Start small and accurate rather than large and messy. Ten correct documents beat fifty that disagree.

Write for the ear

The text will be turned into speech, so write answers the way a person would say them.

  • Answer first. Lead with the answer, then the detail. "We are open from nine to five on weekdays" before any caveat.
  • One fact per paragraph. Short paragraphs retrieve cleanly and are easy to read out.
  • Question-style headings. "Can I cancel on the same day?" matches how callers speak.
  • Short sentences. A sentence that needs two breaths is too long to say.
  • Spell out what is hard to say. Avoid tables of numbers and long lists of codes. Describe them in a sentence.
  • No references to the page. Do not write "see the table above". The caller cannot see it.

Example (illustrative)

Weak: "Cancellations: see policy v3. 24h. Fees may apply per T&C section 4."

Better, under the heading "Can I cancel on the same day?": "You can cancel by phone up to [number of hours] before your visit at no charge. After that, the clinic may charge a late cancellation fee. If you are unwell, tell us and we will see what we can do." Replace the bracketed value with your real policy.

Prices belong in the catalogue, not in prose

A price in a paragraph is a price that will be wrong in six months. Keep amounts in the service catalogue. The price-truth guard means only prices in your catalogue can be spoken, so if an amount is missing the agent does not make one up. In documents, describe the service and refer to the price in general terms: "the price is listed for each service, and the agent can tell you the current amount". Never paste a price list into a policy document.

This also helps when you change a price: you edit one place, and every answer follows.

How semantic search finds a passage

The agent does not scan for exact words. It retrieves the passage closest in meaning to the caller's question. That has three consequences for how you write:

  1. Headings matter. A heading phrased like the caller's question gives retrieval a strong match.
  2. One topic per section. If a section mixes cancellation and parking, a question about either may pull both.
  3. Use the caller's words. If callers say "slot", "appointment" and "session" for the same thing, use the common ones in the heading and mention the others in the text.

Avoid near-duplicate documents. Two files that say slightly different things about the same policy give retrieval a choice, and you cannot control which one wins.

Conflicting and stale facts

The most common failure is not a missing fact, it is two facts that disagree. Prevent it with simple ownership:

  • One owner per document, named at the top.
  • A "last reviewed" date at the top, and a review rhythm: monthly for hours and policies, quarterly for the rest.
  • When a fact changes, search all documents for the old value before saving.
  • Remove superseded documents instead of leaving them beside the new one.

What never to put in it

  • Card numbers, bank details, passwords or access codes.
  • Private staff data such as home numbers, rotas with names, or salaries.
  • Information about individual customers. Customer data belongs in your CRM, not in a document the agent can read aloud to anyone.
  • Internal notes such as "do not tell customers X". If you would not want it read aloud, do not upload it.
  • Legal text you have not simplified. A long contract clause is not an answer a caller can follow.

Test with real caller questions

  1. Pull thirty real questions from call transcripts, emails or messages. Use the callers' wording, not your own.
  2. Place a test call and ask each one. Listen to the answer, as a transcript hides how it sounds.
  3. Mark each as correct, incomplete, wrong or no answer.
  4. For each failure, decide whether the fix is a new document, a clearer heading, or a conflict to remove.
  5. Repeat after each change. The Arabic voice agent testing checklist has extra steps for Arabic callers.

Arabic and English documents for bilingual callers

The AI voice agent has run on live calls in Arabic and English. For any other language, test on a demo first. For bilingual callers:

  • Keep one document per language with the same facts and the same structure, rather than both languages in one paragraph.
  • Write the Arabic as a native reader would say it, not as a literal translation of the English.
  • When you change a fact, change it in both languages on the same day.
  • Give brand and place names in both scripts, to help both retrieval and pronunciation. Check the result on a test call.

Callers who mix both languages in one sentence are covered in Arabic-English code-switching in voice AI.

A maintenance routine after launch

WhenTask
Weekly, first monthReview questions the agent could not answer; add or fix documents
MensuelReview hours, policies and promotions; remove expired offers
On every change in the businessUpdate the document and the catalogue the same day
QuarterlyRe-run your thirty test questions and compare

Knowledge base checklist

  • Each of the top twenty caller questions has one clear answer.
  • Headings are phrased as questions.
  • Each paragraph holds one fact, answer first.
  • No prices in prose; prices are in the catalogue.
  • No two documents contradict each other.
  • Every document has an owner and a review date.
  • Nothing sensitive that you would not want spoken aloud.
  • Arabic and English versions match fact for fact.
  • Tested by phone with real caller wording.

If you are setting up a receptionist from scratch, the full sequence is in how to set up an AI receptionist et le réceptionniste IA page describes what the agent does on a call.

Foire aux questions

What should I upload to an AI voice agent's knowledge base first?

Start with what callers ask most: opening hours, the services you offer, locations and directions, booking and cancellation rules, and your main policies. Read a week of call transcripts or your inbox and list the top twenty questions, then make sure each has a clear answer in a document before adding anything else.

Should prices go in the knowledge base?

No. Put prices in the service catalogue. DialerBee's price-truth guard means only prices in your catalogue can be spoken, which stops the agent inventing a number. Keep the knowledge base for descriptions and policies, and refer to the catalogue for any amount.

How does the agent find the right answer in my documents?

By semantic search: the agent retrieves the passage whose meaning is closest to the caller's question, rather than matching exact keywords. That means clear headings, plain wording and one topic per section make retrieval more reliable. A caller who says they need to move their slot will still match a passage titled how to reschedule.

Can I use the same documents in Arabic and English?

Write each language as its own document rather than mixing both in one paragraph, and keep the facts identical. DialerBee's AI voice agent has run on live calls in Arabic and English. For other languages, test on a demo first.

How often should I update the knowledge base?

Whenever a fact changes, and on a fixed review date even if nothing has. Assign one owner per document and put the last-reviewed date at the top. Review caller questions the agent could not answer each week for the first month, then monthly.

What should never go into a knowledge base?

Card numbers, passwords, private staff details, other customers' data and anything you would not be comfortable hearing read aloud to a stranger. The agent may read out anything the documents contain, so treat every document as something that may be spoken on a call.

Sources

This guide cites no external statistics or regulations. Product behaviour (document upload, semantic search, the price-truth guard, the service catalogue and Agent Studio test calls) is described on the DialerBee Agent Studio et agent vocal IA pages (checked November 7, 2026).

Lectures complémentaires

À lire aussi : AI Voice Agent Security: Can Callers Trick It? · Who Pays When an AI Agent Gets It Wrong?

Prêt à voir DialerBee en action ?

Demandez une démo en direct de 15 minutes, ou démarrez un essai gratuit de 14 jours — sans diaporama, sans engagement. Les appels démarrent dès que votre propre trunk SIP ou PBX est connecté et approuvé.

Essai gratuit de 14 jours · crédit IA gratuit · sans carte · 11 langues · BYOC · contrôles qui contribuent à la conformité

Voir le site complet en anglais →