assistant/
An assistant trained on your business and connected to your systems. It looks up free dates and prices, answers in any language, and it is not a generic chatbot reciting your website back at people.
It takes its look from your site, not from mine.
read what_matters()
Anyone can buy access to the same models. The difference is what the assistant knows about you and what it can reach.
It knows what you tell it, not just what is on the website. Cancellation rules, what suits children, where to park, what you do when the weather turns. Knowledge that otherwise lives only in your head and on the phone.
It looks up your calendar and your price list and answers with real figures. That is why it can answer "is the weekend free" and "what does this cost" rather than pointing at a page the guest has to read themselves.
What it does not know it says plainly, and points at your phone. That is why it is safe to leave running when you are nowhere near it.
run samples
This is the assistant itself, the same component that gets installed for clients. The business is a made-up example and the information is its own.
It is right here, sitting exactly the way it sits on your own site. Pick a question and it answers, or open it and type one of your own.
No assistant is connected to this page. The answers are written in advance and played back in the component itself, so nothing here can invent.
It does not recite a list of what it can do, it asks what it can do for you. That it is automated stands in the header and along the bottom the whole time, not in one sentence that scrolls out of the conversation. The suggestions come from your own frequently asked questions.
The mark above the answer says it looked it up. The figure arrives in a laid-out card rather than inside a paragraph a guest could misread.
Same mark, same layout. It reads the calendar, it does not change it, and the guest can carry on to a booking request if they want.
This is the one that matters most and nobody else shows it. It does not guess, it says so plainly and hands you the phone.
The traveller asks in English and gets English back, from the same information. You do not have to maintain two sets of answers.
A question with more than one answer gets them laid out. The guest reads the part they need and skips the rest.
read installation()
If I already host your site this is no work for you at all. If somebody else looks after it, it is one line.
01design()
Colours, type and corners come from your site. It is drawn inside its own compartment so neither system can break the other.
02training()
We go through the business together: prices, rules, what guests always ask, and the things written down nowhere. You approve every line before it goes live.
03testing()
You ask it ten questions in private and see exactly what a guest would see. Nothing goes live until you say so.
04caps()
Limits per question, per visitor per day, and for the day as a whole. A bill cannot run away.
read status.assistant
tilbúið
It reads the calendar and the price list and works out neither itself, so it cannot promise a price that does not exist or a day that is taken. If a guest wants to book, it prepares the booking and the guest presses confirm themselves. The assistant never books for them, and that is deliberate: a wrong date in a proposal is something the guest sees and rejects, while a wrong booking is already in your calendar. Changes and cancellations still go through the phone.
open a conversation
I set it up with your own information and you question it yourself before any guest sees it.