Routine messages, sent on time
A pre-arrival welcome, a check-in reminder, a thank-you after departure: set the recipe once and it runs for every stay.
Less repeat work. More informed decisions.
Automations send the routine messages, the copilot answers questions on live records with citations, and anything that changes a record waits for a person to approve it.
Routine messages go out on time. The copilot answers from your live records, cites them and waits for approval.
A pre-arrival welcome, a check-in reminder, a thank-you after departure: set the recipe once and it runs for every stay.
“Who arrives today with a balance?” The copilot answers from live records, in your language, and cites each reservation.
Replies to guests are drafted for staff to edit and send. The copilot does not autonomously change your records: actions wait for approval, and the log keeps every one.
Supported today. Where something is still planned, the plan table says so.
| What’s included | Starter | Growth | Enterprise |
|---|---|---|---|
| Copilot | Included | Included | Included |
| API and webhooks | Not included | Included | Included |
| AI credit packs | Add-on | Add-on | Add-on |
The copilot shortens the search; your team keeps the decision.
Type the question in plain words, in any of the eight languages: today’s balances, this week’s arrivals, a guest’s history.
Each answer cites the records it used; open them to check the detail.
Make the change in the reservation or folio yourself, or approve the drafted action. Nothing changes without a person.
Switches on automations such as a pre-arrival welcome and reviews what each one did.
Asks the copilot who arrives today with a balance and gets an answer with citations into the records.
Edits drafted replies before anything is sent to a guest.
An illustrative day
A manager asks, in Dhivehi, which of today’s arrivals still have a balance. The copilot answers from live records and cites each reservation. The automation sent this morning’s welcome messages at eight; the inbox holds a drafted reply to a late-arrival question, waiting for someone to read it and send it.
A made-up day to show the flow, not a customer story.
Recipes configure repeatable operational workflows. The current copilot answers questions about property records and provides citations. They serve different purposes; confirm the available recipes and question types in your demo.
No. The current copilot reads and cites records. Actions that change records wait for staff approval.
Copilot answers and drafted replies use credits. Every plan includes the copilot; credit packs are an add-on priced on request.
Let’s talk about your property
See how LobbyMind could fit your day, your property and your next chapter.
Book a demo