Your industry · Your work OS
Your hotel’s services in ChatGPT.
Present your hotel’s services and practical information in its application. Guests can submit an enquiry; availability, reservations and payments follow the tools and journeys actually connected.
What customers can do with your application.
What customers browse: The property’s services and practical information that you publish.
What you receive: The service or question, voluntarily supplied details and contact information.
Your benefit: Receive the guest’s question and context before handling it.
What services does your hotel offer?
What practical information do you publish for planning a stay?
I would like to contact the hotel about a specific request.
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
This AlefOS journey does not promise live room availability, reservations, payments or replacement of the PMS. Valyo’s offer is not part of this page.
Your initial scope and extensions.
The Customer AI Application includes your company identity, an authorised offer catalogue, conversational search, contextual enquiries, an administration dashboard and WebApp, plus initial configuration and launch testing.
Additional team workflows: Requests across reception, housekeeping and maintenance, shift handovers and promised responses.
Booking journeys, business integrations, private documents and the internal workspace are defined separately, according to available features and the quote. They are not automatically added to the customer application.
Workflow example
A concrete workflow, from the signal to the next step
A guest reports an issue during the night shift.
The request is linked to the relevant internal service and pending response.
The morning team sees what was reported and what remains unresolved.
A reviewed response continues the same guest relationship across the handover.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
Hospitality: a request that follows the change of shift
On this page
One request, several departments
Reception, housekeeping, maintenance and a manager may contribute to the same request. Context must indicate who is waiting for what and which update the guest should receive.
When the shift changes
The next team retrieves promises, open actions and recorded decisions. Guests should not have to repeat their whole story because their contact has finished a shift.
Incidents and arrival preparation
A special request before arrival may require several internal preparations. An incident can preserve its history and actions already attempted without automatically producing a technical diagnosis.
Decisions and team knowledge
A manager’s decision and approved answers can be preserved in an authorized group. Reusable experience must not unnecessarily expose a guest file or sensitive information.
Languages and multi-property operations
A compatible experience can explain a guest message in another language before a reply is prepared. Manager and hotel-group views depend on authorized scopes; they are not universal staff surveillance.
Professional scope and responsibilities
AlefOS does not replace the PMS: reservations, rooms, rates, payments, check-in, check-out and housekeeping status remain in hotel tools. It does not manage key cards, inventory, payroll or revenue. This workflow does not encourage storing passports, full payment card numbers or unnecessary sensitive data.
Your team’s tools
Explore features, connections and access rules in the AlefOS documentation.
Explore the documentation ↗Continue exploring
This workflow uses capabilities configured in your company’s environment, under your brand. Your team can use a compatible assistant to consult authorized context through its configured MCP connection. Understand your AI connection ↗