> 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-essentials.md).

# AMIE Essentials

AMIE Essentials is built around SAM (Spectralink Application Management), the browser-based console for configuring and administering a fleet of Spectralink Versity smartphones: what each phone is allowed to do, how its applications behave, and how configuration reaches every handset automatically.

This documentation covers **SAM software version 1.15**.

## Start here

* [Introduction](/amie-essentials/introduction.md) — what SAM is and how it fits with AMIE
* [Planning and Deployment](/amie-essentials/planning-and-installation.md) — install the SAM server and complete first-time setup
* [Using the platform](/amie-essentials/using-the-platform.md) — the SAM console and how configuration reaches your phones

## Reference

* [Applications](/amie-essentials/applications.md) — the settings for each Spectralink application
* [Maintenance](/amie-essentials/maintenance.md) — backup, restore and upgrading SAM
* [Release notes](/amie-essentials/release-notes.md) — what changed in each SAM release
* [Appendix](/amie-essentials/appendix.md) — related Spectralink documents


---

# 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-essentials.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.