> 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/connections-and-integrations/cti/was-ist-cti.md).

# What is CTI?

Learn what CTI (Computer Telephony Integration) is and how to integrate telephony into your software with it.

CTI stands for **computer telephony integration**. This allows the computer to communicate with the telephone system and the telephone system with the computer. sipgate enables you, via CTI **various services** to use in your telephony interface.

With CTI, you can automatically initiate calls from computer programs, answer and end telephone calls, **conference calls** hold, **fax messages** send and receive, **phone book services** use and calls **forward**. CTI applications usually run either on the user's desktop or on an unattended server.

Do you use a CRM system such as Zoho in your company? Then you can easily integrate sipgate telephony into your Zoho interface. In the category [**Connections and integrations**](https://help.sipgate.de/hc/de/categories/4403735350673-Anbindungen-und-Integrationen-) you will find all applications that you can connect with sipgate. Among them also a setup for **API** and **TAPI**.


---

# 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.de/cloud-telefonanlage/en/connections-and-integrations/cti/was-ist-cti.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.