> For the complete documentation index, see [llms.txt](https://lumin-ai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumin-ai.gitbook.io/docs/lumin/what-is-lumin.md).

# What is Lumin?

Your AI-powered staff, making guest relations easier than ever.

### A new era in guest relations starts here.

Lumin is an AI service designed to ensure your guests feel at ease, providing seamless communication and support from the moment their reservation is made. Guests can easily connect with Lumin to make requests, ask questions, or seek assistance. If needed, Lumin will automatically redirect them to the hotel staff for further support.

### Scalable to your needs

Lumin is fully customizable to fit the specific needs of any business that interacts with guests. Through simple options within the app, you can scale Lumin’s services by enabling or disabling it for certain guests or during selected times. Whether it's during periods of low staffing, such as night shifts, or other designated times, Lumin can seamlessly handle guest inquiries. If an issue arises that Lumin can't resolve, it will provide appropriate guidance and ensure the guest is informed.

### A smart messaging platform

Overall, Lumin is a chat platform, with separate web applications for Guests and Hotel Staff.


---

# 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://lumin-ai.gitbook.io/docs/lumin/what-is-lumin.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.
