> 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-management/notifications/acknowledging-alarms-via-sms-or-email.md).

# Acknowledging alarms via SMS or email

### Introduction

This procedure allows an operator who receives an alarm SMS or email message, to acknowledge it remotely via SMS and/or email message response. Operators require the "Edit Alarm" privilege to acknowledge an alarm.

**Note:** Mobile Client users can use the Mobile Client to acknowledge Mobile Notifications.

***

### Considerations

* Set the Event Group "Unrecognised Sender" to "Log an event" on the **Event Defaults** tab of the Server Properties, while testing or troubleshooting alarm acknowledgements via email or SMS. This will log an event if an incoming **ACK** cannot be processed for some reason.
* If your sites Bulk SMS Service Provider attaches the outbound message to the incoming acknowledgement, then the Alarm ID is not necessary, (e.g. behaves like email. **ACK** only is required).

***

### Configuration

Use the appropriate procedure below for the type of message you want to acknowledge:

<details>

<summary>Acknowledging Email messages</summary>

1. Select either **Reply** or **Reply with History**.

   **Note:** Either option for replying is acceptable as the Alarm ID is always in the subject line.
2. Type the letters **ACK** in the body of the email.

   **Note:** This is not case sensitive, as long as the letters are typed in sequence without spaces.
3. Select **Send**.

   **Example reply**: **ACK**

</details>

<details>

<summary>Acknowledging SMS messages</summary>

1. Select **Reply**.
2. Type in the Alarm ID number.

   **Note:** Only the numbers need to be entered. There is no need for the "ALM" characters.
3. Enter a space and type in the letters **ACK**.

   **Note:** This is not case sensitive, as long as the letters are typed in sequence without spaces.
4. Select **Send**.

   **Example reply**: **36 ACK** (where 36 is the Alarm ID).

</details>

### Result

Command Centre does the following:

* Receives the response and correlates it to the outbound event/message.

  **Note:** If correlation cannot be determined, an event is raised.
* Processes the inbound message and acknowledges the alarm.
* Logs an acknowledgement response/inbound message details.


---

# 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-management/notifications/acknowledging-alarms-via-sms-or-email.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.
