Using Call

Knowledge Sources in Call: Files, Web Pages, Text and Q&A

Learn which knowledge source to use for which content in Call, how to add files, website pages, text snippets and Q&A, and how to check what your agent finds.

Call editorial team · Published · 6 min read

An AI phone agent does not know your business. It knows what you tell it. The texts you give it, called knowledge sources, are the difference between an agent that sounds helpful and one that guesses. This guide explains the kinds of source Call supports, which to choose for which content, and how to keep them accurate over time.

A staff member preparing documents on a laptop to teach a phone assistant
Illustrative image

If you are still deciding how knowledge reaches a voice agent, read RAG for voice agents for the concept, and Building a Knowledge Base for Support and AI for how to write good content.

The five source types

In Call, sources belong to one AI agent. If you have several agents, pick the agent first, then add sources to it. The sidebar groups them under Sources.

What each source is for

  • FilesDocuments such as PDF, Word, plain text, Markdown, CSV and JSON. Good for manuals, price-free service descriptions and policies already written down.
  • WebsiteOne page, a whole site or pages you choose. Good for public information that already lives on your website.
  • Text snippetsShort pieces you type in, with a title such as refund policy. Good for rules that exist nowhere else.
  • Q&AA question and the exact answer the agent should give. Good for the things callers ask every day.
  • Notion importPages brought in from Notion. Good if your team already writes its documentation there.

A useful rule: put things callers ask often in Q&A, background in files or web pages, and exceptions in snippets. The agent can then give a precise answer to the common question and still have context for the unusual one.

What to put in, and what to leave out

Start from the calls, not from your documents. Listen to ten recent calls or read your inbox and list what people actually ask: opening hours, how to book, where you are, what to bring, who handles complaints. Those become your first Q&A entries.

Adding each type

Files

Drag files onto the upload area or choose them from your computer. You can add several at once. Each file then shows how many characters were added, or why it was refused. Check the status afterwards: ready means it can be used; empty or failed means the text could not be read. Scanned PDFs without selectable text are the usual cause.

Website pages

Enter the address of a page (https addresses only) and choose how to read it: that page, the whole site or pages you tick. Reading a whole site follows links and the sitemap within limits on the number of pages and the time taken. Follow the crawl's progress and stop it if it wanders. Menus, footers and cookie banners can leak into the text, so look at what was read.

Text snippets and Q&A

For a snippet, give it a title and the content. For Q&A, write the question as a caller would ask it, then the exact answer. Call can also tidy every answer for you, merging duplicates, fixing wording and shortening answers for the phone; you can undo that if you do not like the result.

A sensible order for a new agent

  1. ListWrite down the ten questions callers ask most.
  2. AnswerAdd each as a Q&A with a spoken-style answer.
  3. Add backgroundUpload the one or two documents that explain your services.
  4. Add the websiteRead the pages that describe what you do, not the whole blog.
  5. CheckAsk the knowledge base real questions and fix the gaps.

Check before you trust it

Call lets you check a question against an agent's knowledge base without making a call. It shows what the search finds. Use it with real wording: "are you open on bank holidays?" rather than "opening hours". If the result is empty or off-topic, add or rewrite a source. If two sources disagree, fix the one that is wrong; do not leave contradictions for the agent to resolve.

After a change to a source, rebuild the agent's search with the re-index button so the new text is used. Then repeat the same questions. Keep a short list of ten test questions and rerun it every time you change something. Testing a voice agent explains how to extend this into a fuller routine.

Q&A vs file vs web page

Q&AFile or web page
Suited toCommon questions with one right answerBackground and detail
ControlYou write the exact wordsThe agent paraphrases what it finds
UpkeepEdit one entryReplace the file or re-read the page
RiskMany entries drift apart over timeOld documents answer new questions wrongly

Writing answers for the ear

A phone answer is heard once, at speaking speed, with no chance to scroll back. That changes how you write. Lead with the answer, then add one detail. Replace lists with a sentence that names two or three items. Spell out anything a caller must write down, and keep numbers and dates in the form people say them.

Take a question such as "Can I change my appointment?" A web page might answer with a table of rules. A phone answer says: "Yes, you can change it up to the day before. If it is sooner than that, I can take a message for the team." It is short, it answers first and it gives the next step. Read each new Q&A answer aloud before saving it; if you run out of breath, cut it.

Keeping sources accurate

Sources go stale quietly. Give each source an owner and a review date. When opening hours, a policy or a service changes, update the source the same day. Read what callers asked that the agent could not answer; that is your list of gaps. Finding knowledge gaps from calls shows a repeatable way to do this.

Storage is shared between all agents in the organisation and is limited, so remove duplicates and old drafts rather than hoarding. Only workspace managers can add, change or delete sources; members can read them. Deleting a source removes it from what the agent can use, so check before you delete something the agent depends on.

Monthly source review

  • Opening hours and holiday notes match reality
  • Every source has an owner
  • Five random Q&A answers read aloud and still sound right
  • Last month's unanswered questions turned into new entries
  • Duplicates and old files removed
  • Test questions rerun after the last change

Doing it in Call

In Call, open Sources in the sidebar and pick Files, Website, Text snippets or Q&A. Choose the agent at the top right if you have several. Use Check a question under Data sources to see what the knowledge base finds, and Re-index agent to rebuild its search after edits. Suggestions built from caller questions can point to gaps worth filling. Setting Up an AI Agent in Call shows where sources fit in the larger setup.

Frequently asked questions

Which source type should I start with?

Q&A. It gives you exact control over the answers to the questions callers ask most. Add files and web pages afterwards for background.

Can the agent read my whole website?

You can read one page, a whole site within limits, or pages you choose. Reading only the pages that describe your services usually gives cleaner results than the entire site.

Why does an uploaded file say empty or failed?

The text could not be read. Scanned documents without selectable text are a common cause. Re-export the document as text or a normal PDF.

How do I know what the agent will find for a question?

Use the check-a-question tool in the data sources view. It shows what the knowledge base returns for the wording you type, and no call is made.

Do I need to re-index after editing?

Re-indexing rebuilds the agent's search, so use it after meaningful edits and then repeat your test questions to confirm the change took effect.

Who can change sources?

Workspace managers can add, change and delete sources. Other members can read them.

Add your first knowledge sources to an AI agent in Call

In the demo console you can try incoming calls in a simulation.

Related guides