> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/behavior/wissensdatenbank.md).

# knowledge base

In addition to individual customer questions, you can provide your agent with a knowledge base containing your own content, such as FAQs or product information.

Your agent uses this content to better understand inquiries and derive suitable answers. You can expand or update the knowledge base at any time.

{% hint style="warning" icon="user-headset" %}
**Note:** You can find the knowledge base in sipgate sona by opening the agent overview, clicking your agent, and **Knowledge** selecting.
{% endhint %}

### Preparing documents for the knowledge base optimally

To ensure that your AI Agent can process the uploaded documents as effectively as possible, you should consider the following when preparing them.

#### **Structure & format**

* Use a clear structure with meaningful headings
* Use plain text instead of scanned documents
* Avoid tables where possible or convert them into plain text

{% hint style="info" %}
**Supported formats:** PDF, TXT, DOCX, Markdown, PPTX, XLSX, PNG and JPEG. One file per upload is possible, with a maximum of 10 MB.
{% endhint %}

#### **Content optimization**

* For extensive content, split it into several topic-specific documents
* You can rename automatically generated document titles at any time. Meaningful titles make later overviews easier
* Avoid duplicates with customer questions that have already been stored

#### What does a good document look like?

{% columns %}
{% column %}
**Well suited:**

* Clearly structured text documents with a clearly defined topic, because your agent evaluates text particularly reliably
* Meaningful headings for each section
* Files with copyable text, for example Markdown or PDF
  {% endcolumn %}

{% column %}
**Less suitable:**

* Content that mainly consists of tables, images, or graphics
* Scanned PDFs in which the text is only available as an image
  {% endcolumn %}
  {% endcolumns %}

{% hint style="warning" %}
**Notes:**

* Do not upload process descriptions or behavioral instructions to the knowledge base. Such workflows belong in playbooks, because playbooks specifically control conversation steps and behavior. Content from the knowledge base cannot be interpreted as process instructions.
* Only store information that may be passed on to callers. Your agent can use content from the knowledge base in conversations. Confidential or internal information therefore does not belong there.
  {% endhint %}

### Expand and update the knowledge base

Your agent's knowledge base can be expanded and updated at any time. If content changes, upload the updated version manually. New or changed documents will then be taken into account in future conversations.

If answers seem incomplete or inappropriate, download the document or edit it in the original source. Then upload the updated version and delete the old document.

{% hint style="info" %}
**Note:** If your agent uses inappropriate information in individual conversations, sipgate can [**customer support**](https://www.sipgate.de/support-anfrage) check which knowledge document was used in the respective call. Have the date and time of the call ready for this.
{% endhint %}

### Knowledge base vs. playbooks – what is the difference?

The features serve different functions.

{% columns %}
{% column %}
**Knowledge base:**\
Determines, **what** the AI Agent can say.

That is, which information, facts, and answers are available to it.
{% endcolumn %}

{% column %}
**Playbooks:**\
Determine, **how** the AI Agent proceeds.

That is, which steps are followed in a conversation, for example capturing callback details or forwarding a request to an employee.
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
In the [**Enterprise plan**](https://help.sipgate.com/documentation/en/plans-and-pricing/enterprise-tarif-leistungen-und-einfuhrungsprozess.md) Knowledge sources and processes can be connected and automated in a more individual way. Our team supports you from conception to implementation.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sipgate.com/documentation/en/behavior/wissensdatenbank.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
