> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/was-ist-sipgate-conversation-intelligence.md).

# What is sipgate Conversation Intelligence?

Conversation Intelligence (CI) evaluates call content across the account. Unlike [AI Assist](/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/was-sind-die-sipgate-ai-features.md) CI functions are enabled and configured by admins or team leads – the results relate to the conversations of all users in the account, but are not directly visible to the individual user at the call event in the sipgate app.

{% hint style="info" %}
**Note in the app:** If you are working in a channel for which CI has been enabled, sipgate shows the following note directly in the channel – both in the desktop app and in the mobile apps:\
\
*"Conversation Intelligence enabled. Conversations in this channel are analyzed with AI support."*\
\
The notice is for information only: you cannot disable the feature for yourself, as CI is controlled account-wide by the admin or team lead. If you have any questions, please contact your admin or team lead. The display fulfills the transparency obligations under Art. 50 of the EU AI Act, which have applied since 2 August 2026. For more information on data protection and AI, see the article [Data protection and AI functions in the sipgate app](/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/datenschutz-und-ai-funktionen-in-der-sipgate-app.md).
{% endhint %}

## What is the difference between CI and AI Assist?

|                     | AI Assist                                     | Conversation Intelligence (CI)                                         |
| ------------------- | --------------------------------------------- | ---------------------------------------------------------------------- |
| Who activates it?   | Each user for themselves                      | Admins/team leads, account-wide                                        |
| Whose call content? | The user's own calls                          | Calls of all users in the account                                      |
| Where visible?      | Directly at the call event in the sipgate app | Not at the call event, but in separate admin areas or external systems |

## Overview of CI functions

* **Custom Fields:** Admins define fields that the AI extracts from each call and collects in the Data Hub. More on this in the article [What are Custom Fields?](/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/was-sind-custom-fields.md)
* **CI Webhooks:** Admins set up in the **App Web** webhooks through which transcripts, summaries and other call data are automatically transmitted to external systems such as a CRM. More on this in the article [How can I set up CI webhooks for sipgate Conversation Intelligence?](/cloud-telefonanlage/en/using-sipgate/sipgate-ai-agents/wie-kann-ich-ci-webhooks-fur-sipgate-conversational-intelligence-einrichten.md)

{% hint style="info" %}
CI webhooks must not be confused with the AI Assist webhook: This is set up directly in the sipgate **Desktop App** and transfers the AI Assist results of a single channel (see [How do I set up the sipgate AI Assist webhook?](/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/wie-richte-ich-den-sipgate-ai-assist-webhook-ein.md)).
{% endhint %}

**Prerequisite: F**or all CI functions, admin access as well as activated transcription for the respective channel or agent (Business or Premium plan) is required.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/die-sipgate-app/was-ist-sipgate-conversation-intelligence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.