The AI assistant and its tools

What the assistant does

The assistant, at /en/dashboard/ai-assistant, is a chat over the company's own data. It answers from the stays, the calendar, the bookings, the inquiries and the reviews in the database, checks which stays are free for given dates and quotes them, draws charts of bookings, revenue or occupancy by month, and acts when asked: draft a stay, block a stay's nights, confirm, check in, complete or cancel a booking, add a note, move an inquiry along, publish or hide a review, change a company setting.

• Past conversations are kept per admin, so the history survives a reload, and a conversation can be renamed or deleted.
• Answers stream as they are written, with the model's reasoning shown beside them, and a failed answer offers a Try again button.
• Images can be attached to a question, up to six at a time, each under 10 MB.
• It is a tool for the host team, not a chatbot for guests: the website has no assistant.

What it needs and who can use it

• A Google Gemini key on the API, from your own Google account. Without it a question gets "The assistant is not connected yet" with what to set, and nothing is billed.
• Each answer is billed by Google to that key, at its price for the model picked in the assistant's picker.
• The ai_chat.use permission, and ai_chat.view_models for the model picker. Both seeded roles, Super Admin and Manager, hold both.
• Nothing beyond the admin's own role: the assistant reads and changes only what the admin's other permissions allow, and checks again before every action.

The MCP server

The API also offers the assistant's tools over the Model Context Protocol, so a coding agent such as Claude Code, or any MCP client, can work with the company's stays, calendar, bookings, inquiries and reviews directly. It needs a key you choose, and refuses every request until one is set.

Models

The tools

Connecting an MCP client