> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/getting-started/maintenance-and-support-m-and-s-services.md).

# Maintenance & Support (M\&S) Services

This page is intended as a first introduction to **Akamas Maintenance & Support** (**M\&S**) **Services**.

Please refer to the specific contract in place with your Company.

Akamas M\&S Services include:

* access to Software versions released as major and minor versions, service packs, patches, and hotfixes according to [**Support levels for software versions**](/akamas-docs/getting-started/maintenance-and-support-m-and-s-services/support-levels-for-software-versions.md).
* assistance from [**Akamas Customer Support**](/akamas-docs/getting-started/maintenance-and-support-m-and-s-services/customer-support-services.md) for inquiries about the Akamas product and issues encountered while using Akamas products where there is a reasonable expectation that issues are caused by Akamas products, according to [**Support levels for Customer Support Services**](/akamas-docs/getting-started/maintenance-and-support-m-and-s-services/support-levels-for-customer-support-services.md)

Akamas M\&S Services do not include any installation and upgrade services, creation of any custom optimization packs, telemetry providers, or workflow operators, or implementation of any custom features and integrations that are not provided out-of-the-box by the Akamas products.


---

# 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://docs.akamas.io/akamas-docs/getting-started/maintenance-and-support-m-and-s-services.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.