> 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/server-properties/mobile-sms-notifications.md).

# Mobile/SMS Notifications

### Introduction

Completing the details on this tab allows a site to send SMS notifications of events/alarms to various cardholders/operators. This tab also allows a site to enable Mobile Notifications for Mobile Client users. Mobile Notifications are sent over the internet from the Command Centre Cloud, and do not require outgoing SMS notifications to be enabled.

SMS Notifications are sent via email using a Bulk SMS Service Provider. This service provider converts the incoming email sent by Command Centre to an SMS message and delivers it to the appropriate mobile network provider.

Sites using this feature must choose and subscribe to a Bulk SMS Service. Command Centre formats the message suitable for delivery via SMS.

**Note:** This tab is only visible if your site is licensed for the Notifications feature.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Mobile/SMS Notifications** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5c31fbaa0252e06b302762a2af23665b06f87798%2Fsmsnotificationstab.png?alt=media)
3. If enabling Mobile Notifications for Mobile Client users, read the Command Centre Cloud Terms of Service. If you agree with the terms, select the **Enable Mobile Notifications** checkbox. No further configuration on this tab is required.

   Before using this feature you need to create a Command Centre Cloud item. See [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for the procedure.
4. Check the **Enable Outgoing SMS Notifications** checkbox.

   All other fields on this screen become enabled.
5. Enter the Email-to-SMS Service Provider's Domain Name in the **Domain** field.
6. Click the appropriate **Email Format** radio button to place the SMS message in either the Email body or the Email subject.

   **Note:** One or other option will work best depending on your Bulk SMS Service Provider. It is recommended you trial both options.
7. Set the required format for the Command Centre item name portion of the SMS message, by clicking the appropriate **SMS Format** radio button.

   **Notes:**

   * If there is no Short Name for the item, then the first option will use and truncate the normal (or full) Name to 16 characters, whereas the second option will use the full Name in entirety.
   * The first option allows the full message of any of Command Centres events or alarms to fit within the common 160 character SMS length. The second and third options may attempt to generate an SMS message longer than 160 characters. Depending on your SMS Bulk Service provider, such a message may be truncated at 160 characters, or may be delivered as two (or more) messages.
   * If there is a Short Name for the item, and either the first or second option is selected, then ALL event/alarm SMS messages will fall within the 160 character limit.
8. 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/server-properties/mobile-sms-notifications.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.
