AI Receptionist Knowledge Base: What to Prepare Before Launch

Start with approved answers, not a pile of documents

An AI receptionist knowledge base should contain current, approved information the business is comfortable giving a caller. Start with the questions your front desk actually answers. Give each one a clear answer, its conditions, and an owner who can approve changes. More source material is not automatically better when some of it is outdated or contradictory.

A useful buyer question is not just, “Can you read our website?” Ask what will be included, which source controls each answer, and what the receptionist does when it cannot find an approved fact. A polished voice does not establish that the information behind the answer is current.

This checklist is for preparing and evaluating a proposed setup. It does not claim that a standard RobVox plan includes a particular knowledge-base connection, automatic refresh, or retrieval tool. Those details belong in the scope for your business.

Separate factual information from instructions

Reference information explains the business. Call instructions explain what the receptionist may do with that information. Keep both explicit. A cancellation policy is a fact to communicate; permission to waive that policy is a separate decision. A service description does not authorize the receptionist to invent a recommendation or promise availability.

Retell’s knowledge-base documentation places supporting information in the knowledge base and behavior instructions in the agent prompt. Vapi’s query-tool documentation likewise requires explicit instructions about when to search; a knowledge-base description alone is not enough. These are examples from those platforms, not evidence of an integration in your RobVox setup.

Write the answer boundary alongside the source material. Specify which questions can be answered directly, when clarification is needed, and what the next step is if an answer is missing. The human-handoff rules guide covers the receiving-team workflow. Here the job is to define what information can support the answer before that handoff becomes necessary.

Build a small, usable information pack

Organize the initial material around the caller’s questions, not the folders your team happens to use. Retell recommends focused sections and explicit names, dates, and units. Vapi recommends topic-based organization, regular updates, and retrieval tests. A service business can apply that approach without assuming either platform is its provider.

Prepare these customer-facing facts first:

• Business identity and access: the name callers know, correct contact details, address, directions, parking or arrival instructions, and an approved service area where applicable.

• Hours: regular opening times, the relevant time zone, dated holiday exceptions, and temporary closures. Separate storefront hours from any central team’s availability.

• Services: plain-language descriptions of what is offered and not offered, any conditions staff have approved, and questions that require a person rather than a guessed match.

• Policies: current customer-facing rules for changes, deposits, gift cards, packages, and introductory offers. Include the conditions that make an answer true, not just a promotional headline.

• Common questions: a concise approved answer to each recurring inquiry, plus the named source and person responsible for maintaining it.

For a fitness studio, an introductory offer may apply only to a particular type of visit. Include that condition instead of letting “free trial” become an answer to every prospect. The fitness tours and trials guide explains how those calls differ from one another.

For a salon, “starting at” is not a final quote. Preserve that qualifier in the approved answer and identify the questions staff need to resolve. Use the salon service and price rules guide for the service-specific checklist. This information pack should point to the approved rule rather than contain a competing version of it.

For clinics and practices, limit material to practice-approved routine scheduling information, hours, directions, and preparation guidance. Do not use general reference documents to create medical advice, clinical triage, or emergency-handling promises. A knowledge base is not permission to broaden the approved non-clinical role.

Keep one approved answer when sources disagree

A website, brochure, and internal note can all describe the same policy differently. Resolve that conflict before using them together. Identify the authoritative answer, remove or correct the old version, and record when the replacement takes effect. Do not ask the receptionist to decide which policy the business intended.

Retell’s official knowledge-base curation guide recommends removing stale or contradictory material before indexing and keeping one authoritative source per topic. That is useful preparation guidance, not a guarantee that a system will never produce an unsupported answer.

For each important answer, keep a short maintenance record: the approved wording, source, approving person, effective date, and last-checked date. Add an expiry date for a temporary offer. These are suggested business records, not a claim that a provider includes those fields in its product.

If two sources cannot yet be reconciled, mark the answer as unresolved and define the staff-owned next step. Refusing to guess in that situation is a requirement to request and test, not a default behavior to assume. For multiple locations, keep the branch-specific source attached to the right location; the multiple-location guide addresses that extra layer.

Verify updates instead of assuming synchronization

Editing a website does not, by itself, prove that a voice agent has the new answer. Ask how each source is brought into the proposed setup, how often it is refreshed, and how a failed update becomes visible to the person responsible for it. Distinguish a connected source from a one-time exported file.

Retell documents automatic refresh every 24 hours when enabled for supported sources. It also says failed or unfinished refreshes can retain existing content. Uploaded documents and pasted text cannot be updated by that refresh operation. Those documented limits show why an “auto-refresh enabled” label is not proof that today’s change has reached the agent.

A website crawler also has a configured scope. Ask which paths are included and excluded, and whether the important policy page was actually processed. Do not assume a broad crawl includes every useful page or excludes every obsolete one. Get the source list and update method into the proposal.

For a temporary closure or an offer that ends today, ask what controlled change process applies before callers receive an answer. Verify the result through the actual proposed voice workflow. If the new fact is not available yet, decide which answer or staff follow-up is permitted during that gap. Do not let an update delay become an unsupported promise.

Test known, missing, conflicting, and changed facts

Use approved sample material and fictional customer details in demonstrations. Write down the expected answer before calling. Inspect the source or retrieved material where the proposed system exposes it, then listen to what the receptionist actually tells the caller. Retrieval evidence and the spoken answer are related checks, not substitutes for each other.

A compact test set should include:

• A known question: ask an ordinary FAQ and a natural paraphrase. Both should preserve the approved answer and its conditions.

• A missing fact: ask a question the supplied material does not answer. The expected outcome is an approved acknowledgement and next step, not a plausible invention.

• A conflicting policy: supply a controlled old-versus-new example. Confirm how the conflict is detected and resolved before the disputed answer is used with customers.

• A changed fact: replace an approved opening time or offer condition. Verify when the new source is available and that the voice response uses it rather than the old version.

• A qualified answer: ask for a final price when only a starting price is approved. Check that the qualification survives the conversation.

Retell’s documentation includes guidance to answer from relevant retrieved knowledge and acknowledge absent information. Treat that as a rule to configure and test. Neither a good instruction nor a successful test call proves every future answer will be correct.

Keep live availability separate from reference facts. Knowing that a service exists does not prove a slot is currently bookable. The appointment-booking verification guide covers the separate evidence needed before a caller hears that an appointment is confirmed.

Scope the information workflow with RobVox

Bring RobVox a focused FAQ pack, the approved policies behind it, and a list of the questions staff should own. Identify the person who will approve changes and explain which facts change often. Ask which sources can be supported in your proposed setup and how the result will be demonstrated.

The written scope should identify the information sources, update method, answer boundaries, staff follow-up, and the tests needed before launch. Keep credentials, payment details, and unnecessary customer records out of a general FAQ pack. Discuss any actual access requirements separately rather than putting them into customer-facing reference material.

Try the RobVox live voice demo to hear the voice experience. It is not a demonstration of your own knowledge sources or update process. To evaluate those, contact RobVox about your approved information and call rules and ask for a focused test using the facts your team is ready to stand behind.