> 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/deployment-resources/support-tools-and-troubleshooting/support.md).

# Support

As a customer using Gallagher Security solutions, the first point of contact for technical support is your certified Gallagher Channel Partner. Because we set a high standard, be assured that you will receive best-in-class product installation, expert technical advice, and unwavering support.

#### Support tiers <a href="#support-tiers" id="support-tiers"></a>

| Tier    | Who provides it                                           | Who receives it            |
| ------- | --------------------------------------------------------- | -------------------------- |
| Level 1 | Certified Channel Partner                                 | End users (customers)      |
| Level 2 | Gallagher Technical Support + Regional Teams/Distributors | Certified Channel Partners |

​

#### Certified channel partners <a href="#certified-channel-partners" id="certified-channel-partners"></a>

Our channel partners are security installation professionals who have received accreditation through our rigorous training and product certification program to deliver Gallagher systems and products.

**With more than 1,200 Gallagher Certified Channel Partners across the globe, Gallagher is in a great position to connect and introduce the right people for your project.**&#x200B;

#### Regional teams & distributors <a href="#regional-teams-and-distributors" id="regional-teams-and-distributors"></a>

Contact your local Gallagher representative to find a channel partner with the experience and expertise best suited to meet your security needs.

​[Regional Teams](https://security.gallagher.com/Meet-the-Team)

​​[Office Locations](https://security.gallagher.com/en-AU/Office-Locations)​​

#### Gallagher technical support <a href="#gallagher-technical-support" id="gallagher-technical-support"></a>

Teams of highly skilled Gallagher Security engineers and technical advisors are always available to help our Channel Partners around the world.&#x20;

Based at Gallagher Security offices in New Zealand and the United States, our global technical support service provides an exceptional customer experience. Our team is on hand to listen, help with technical queries, and provide installation and troubleshooting advice.​

#### **Third party products** <a href="#third-party-products" id="third-party-products"></a>

For third-party products; Channel Partners provide Level 1 support to customer sites, Gallagher (Head Office, regional, or distributor) provides Level 2 for Channel Partners and Gallagher Head Office facilitates escalation to the manufacturer if needed.


---

# 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/deployment-resources/support-tools-and-troubleshooting/support.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.