> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/ai-receptionist/additional-knowledge.md).

# Additional knowledge

FAQs, policies and files the assistant can draw on.

Open **AI Receptionist → Additional Knowledge**.

Everything that does not fit the other three Knowledge pages — the facts, policies and documents your assistant should be able to draw on.

## What to put here

**Frequently asked questions.** Start with the questions your team actually answers every day. If you have to explain your parking situation six times a week, write it down once here.

**Policies.** Cancellation terms, deposits, refunds, guarantees, what happens if someone is late.

**Procedures.** What a first appointment involves, what to bring, how long things take.

**Facts that do not fit elsewhere.** Accreditations, languages spoken, accessibility, whether you are dog-friendly.

## Writing good entries

Write in question-and-answer form where you can. It matches how callers ask and gives the assistant a clear pairing.

Be complete in the answer. A partial answer produces a follow-up question the assistant may not be able to handle.

> **Do you take card payments?** Yes — all major cards including Amex, plus Apple Pay and Google Pay. We do not take cheques. Card payment is taken at the end of the appointment, not in advance.

That answers the question and the two that follow it.

## Files

Upload documents the assistant can draw on — price lists, terms, service brochures, FAQs you already maintain.

Keep uploads focused. A well-structured two-page FAQ is more useful than a forty-page brochure, because everything in a long document competes for relevance.

Text-based PDFs work; a scanned image of a document does not, unless it has been through OCR.

## Keeping it accurate

Uploaded files are a common source of stale answers, because a document uploaded once is easy to forget. When you revise a price list, replace the file here too.

{% hint style="info" %}
If the assistant gives a wrong answer, the fix is almost always here or in the other Knowledge pages — not in the scenario instructions. Correct the fact rather than instructing the assistant around it.
{% endhint %}

## What not to put here

Do not upload anything containing personal data about your customers, internal credentials, or commercially sensitive material you would not want read aloud. Assume anything here can be surfaced to a caller who asks the right question.

## Testing

After adding knowledge, call the assistant and ask about it — in your own words, not the words you wrote. Then ask something adjacent that you have deliberately not covered, and check it says it does not know rather than inventing an answer.