> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/introduction/getting-help.md).

# Getting help

## Access and sign-in problems

If you cannot sign in, have lost access to a screen, or need a permission you do not have, contact your own AMIE administrator first. Administrators manage users, groups and permissions for your Space.

## Spectralink support

|                               |                                                                   |
| ----------------------------- | ----------------------------------------------------------------- |
| Customer Support Hotline      | +1 800-775-5330, Monday to Friday, 6 a.m. to 6 p.m. Mountain time |
| Technical support             | <technicalsupport@spectralink.com>                                |
| Knowledge base                | support.spectralink.com                                           |
| Return Material Authorization | <nalarma@spectralink.com>                                         |

| Region         | Telephone       |
| -------------- | --------------- |
| United States  | +1 800-775-5330 |
| Denmark        | +45 7560 2850   |
| United Kingdom | +44 1344 206591 |

When you contact support about something you saw in the console, the device or battery serial number, the screen you were on, and the time you saw it are the three things that get you to an answer fastest.


---

# 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.spectralink.net/amie-advanced/introduction/getting-help.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.