> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/intercoms.md).

# Intercoms

Compare Command Centre intercom integrations and select the appropriate supported option.

Command Centre integrates with legacy Austco, Commend, and Jacques systems. It also supports compatible Session Initiation Protocol (SIP) intercoms.

Operators handle calls through Command Centre Client or Premier. Available functions vary by integration. SIP is the current option for new deployments.

### Intercom integrations

| Integration                                                                              | Description                                                                                        |
| ---------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Austco Intercoms](/knowledge-hub/products/integrations/intercoms/austco-intercoms.md)   | Use Command Centre Premier to display and acknowledge Austco calls, then open the associated door. |
| [Commend Intercoms](/knowledge-hub/products/integrations/intercoms/commend-intercoms.md) | Manage Commend call notifications, queues, call handling, door opening, and status monitoring.     |
| [Jacques Intercoms](/knowledge-hub/products/integrations/intercoms/jacques-intercoms.md) | Handle Jacques calls in Command Centre with live video and configured door control.                |
| [SIP Integration](/knowledge-hub/products/integrations/intercoms/sip-integration.md)     | Connect supported SIP intercom devices to Command Centre Client for audio and video call handling. |


---

# 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.security.gallagher.com/knowledge-hub/products/integrations/intercoms.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.