> 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/configuration-client/site-installation/external-alarm-monitoring/configuring-items-for-contact-id/configuring-action-plans-for-contact-id.md).

# Configuring Action Plans for Contact ID

Before an event can be sent to an Alarm Monitoring Company, the Action Plan associated with the event(s) must be set up with an Alarm Transmitter/Dialler.

**Important:**

It may not be appropriate to use the default Action Plans. If these are set up to use an Alarm Transmitter/Dialler, then all alarms will be sent. However, it may not be desirable to send some alarm types to an Alarm Monitoring Company.

All items using an Action Plan with an Alarm Transmitter/Dialler configured will send Contact ID messages. If the Alarm Zone or item has not been configured for Contact ID, then a GG or CCC of zero may be sent.

**Note:**

Alarms will be sent as many times as an Alarm Transmitter/Dialler appears on an Action Plan for the various priorities involved in an escalation. **For example:**

If a "Forced Door" alarm uses a very high priority Action Plan with an Alarm Transmitter/Dialler attached, it will escalate to a critical priority that also has the Alarm Transmitter/Dialler attached. The "Forced Door" alarm Contact ID message will then be sent twice, (i.e. once for each priority).

1. Click **Configure** from the menu bar, then **Action Plans**.

   The **Action Plan** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the Action Plan and select **Properties**.
3. Click the **Armed** (or **Set** ) tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8949a033147dc5cb2892c93efcb1e8e461f03092%2Ftab_armed.png?alt=media)
4. Click within the **Alarm Transmitter** field to display the available options, and from the list select the appropriate Alarm Transmitter/Dialler for Contact ID.
5. Click each of the remaining tabs and repeat Step 4 for each one.
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/site-installation/external-alarm-monitoring/configuring-items-for-contact-id/configuring-action-plans-for-contact-id.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.
