> 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/command-centre-client/using-command-centre/licensable-features/intercom-viewer-feature/isolate-function.md).

# Isolate function

The Intercom's 'Isolate' function is an override option. It allows an operator to disable a specified intercom until the operator chooses to de-isolate it.

**Note:** Some intercoms cannot be isolated, (e.g. master and SIP intercoms).

In Command Centre, you can isolate intercoms via the Status tile or Site Plan tile while in the Intercom Viewer. See the [Intercom Viewer Configuration](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/intercom-viewer-configuration.md) topic for instructions on setting up the Intercom Viewer.

To isolate an Intercom from either the Status tile or the Site Plan tile:

1. **Right-click** the Intercom you want to isolate.

   A context menu displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-da39bd1609f20853b5f867ab4714df482924ab40%2Fcommendisolatefunction.png?alt=media)
2. Click **Isolate**.

   The Intercom is now isolated and no calls will be able to be placed from this Intercom.

To de-isolate an intercom from either the Status tile or the Site Plan tile:

1. **Right-click** the Intercom you want to de-isolate.

   A context menu displays.
2. Click **De-isolate**.

   The Intercom is now de-isolated and the operator will receive notifications related to the Intercom again.


---

# 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/command-centre-client/using-command-centre/licensable-features/intercom-viewer-feature/isolate-function.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.
