# Support

Support at StrongDM is broken up into three tiers: Bronze, Gold, and Platinum. Each tier has a set of expectations around response times, service-level agreements (SLA), personal interactions, and training, among other concerns. You may read more about Support levels on the [StrongDM Service Tiers](https://www.strongdm.com/pricing/service-tiers) page.

### StrongDM Help Center

StrongDM Support provides additional information about usage, deployment, installation, troubleshooting, and more, at the [StrongDM Help Center](https://help.strongdm.com/hc/).

To request help from StrongDM Support, please visit the StrongDM Help Center and submit a request ticket.

### Ticket Priority Definitions

Tickets submitted to the StrongDM Help Center can have one of four priority levels: Critical (1), High (2), Medium (3), and Low (4). Each priority level has a particular set of parameters to define it, as well as an expected update frequency. Each priority level also carries an expectation of what will be communicated by StrongDM after the resolution of the issue.

#### Critical (1)

With a critical priority issue, you cannot reasonably continue your work in your StrongDM organization. You experience a complete loss of service and/or encounter one of the following scenarios:

* All users cannot use StrongDM.
* Users cannot access any resources in their environment.

The update frequency for critical priority issues is a minimum of once per day and a maximum of once per hour. This frequency is determined by how impactful the issue is. A Zoom meeting is typically offered to the customer to recap the issue after it is resolved.

For most critical priority issues, a root cause analysis (RCA) will be provided.

#### High (2)

With a high priority issue, your StrongDM organization is running in a degraded mode. Operations can continue in a restricted fashion, although long-term productivity might be adversely affected and there is no temporary workaround. For example:

* Some users cannot use StrongDM.
* Users cannot access some resources in their environment.

The update frequency for high priority issues is a minimum of once per day and a maximum of twice per day (ideally at the start of business and again at the end of the business day). Frequency can be adjusted as needed by how impactful the issue is. A Zoom meeting is available upon request to recap the issue after it is resolved.

For most high priority issues, a root cause analysis (RCA) will not be provided.

#### Medium (3)

With a medium priority issue, your StrongDM organization experiences a minor loss of service, resulting in a partial, non-critical loss of functionality of the software. The impact is an inconvenience, which may require a workaround to restore functionality.

The update frequency for medium priority issues is once per day. Frequency can be adjusted as needed by how impactful the issue is.

For most medium priority issues, a root cause analysis (RCA) will not be provided.

#### Low (4)

With a low priority issue, you are likely making an information request, reporting a documentation error, recommending a product enhancement, or other similar issues. There is little to no impact to the operations of your StrongDM organization.

The update frequency for low priority issues is once per day. Frequency can be adjusted as needed by how impactful the issue is.

For most low priority issues, a root cause analysis (RCA) will not be provided.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.strongdm.com/admin/deployment/support.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.