> 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/austco-intercom-feature/answering-a-call.md).

# Answering a call

An operator can answer a call from:

* an Austco Console connected to a Command Centre workstation,
* an Austco Intercom item configured in Command Centre (located on a Site Plan tile or Status tile), or
* an Austco Intercom Viewer.

**Notes:**

* You can configure the Austco Intercom Viewer not to pop to the front, if required. See [Creating the Austco Intercom Viewer](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/austco-intercom-feature-configuration/creating-the-austco-intercom-viewer.md) for detail.
* When a new call appears in the "Ringing" state in the list, the workstation plays the "IntercomCall" sound as configured in the workstation "Sound" control panel in Windows. By default, the notify.wav sound file from the Windows Media folder is configured to play. You can choose to select a different sound file, if required.
* If a call arrives while the operator is handling another call, the new call is added to the list.

1. Open the Austco Intercom Viewer.
2. Click on the row of the call event you want to respond to, so it becomes highlighted.

   Either the Panel configured specifically for the intercom for which the call event was generated, or the default Panel will display.
3. To connect to the call event click the **Connect** button.

   The call event is cleared from all other workstations. The time remaining is cleared, and the console will connect to the intercom.

   **Note:** If you fail to connect to the call event within the time remaining, (i.e. the time indicated in the "Seconds Remaining" column), the cardholder will be denied access and the call event is cleared from the list.

   You can now:

   * talk to the cardholder, if required via the Austco console,
   * open the door associated with the intercom, or
   * end the call.

   Take the appropriate action as required:

#### Opening the door associated with an intercom

1. Click the **Open Door** button.

   The door that is associated with the intercom opens.

   **Notes:**

   * If no door is associated the **Open Door** button is disabled.
   * You need the "Override - Open Door" operator privilege to perform this function.

#### Ending a call

Once you have answered a call, you have the option to end the call at any time.

1. Click the **Cancel** button.

   The call event is cleared from the list and removed from all other workstation PCs. The next call event is selected automatically, and the appropriate Panel displayed.

   **Note:** If an operator attempts to cancel a call from another workstation, the error message *"Access is denied"* displays in the Austco Intercom Viewer. A workstation can only cancel its own calls.


---

# 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/austco-intercom-feature/answering-a-call.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.
