Two things went out over the last few weeks. They look unrelated and they are solving the same problem from opposite ends: a guest has a question, it is late, and the only route to an answer currently runs through you.
Ask the guidebook
There is now a chat panel in the guest view. A guest types a question and gets an answer drawn from what you wrote.
The interesting design decision was what it refuses. It answers from your guidebook and nothing else. Ask it the door code and it gives you the door code. Ask it what time the last train to London leaves and it says it does not know and suggests asking the host — rather than inventing a plausible timetable, which is exactly what a general-purpose assistant would do and exactly the failure that would make the feature unusable.
That constraint sounds like a limitation. In testing it turned out to be the feature. A host cannot hand a guest a bot that might confidently make up a check-out time. The value is not that it is clever; it is that its answers are things you typed.
Practically this means the chat is only as good as the guidebook behind it. A thin guidebook produces a chat that shrugs a lot. This has had an unexpected side effect during testing: hosts who turned it on started filling in the sections they had been skipping, because the gaps became visible.
What it is good at: the door code, the WiFi, the check-out time, whether the bins go out on Tuesday, whether there is a hairdryer — the questions with a written answer and a guest who did not want to scroll.
What it is not: a concierge. It will not book you a table and it will not tell you about the town beyond what is in the guide.
Twelve languages
Pick up to twelve languages on a guidebook, and every section gets translated when you publish. Guests switch with one tap.
The part worth explaining is what the translation leaves alone. WiFi passwords, door codes, check-in times, addresses and phone numbers pass through untouched. This sounds obvious and is the thing that goes wrong in every naive implementation: a translation engine handed seagull-harbour-92 will occasionally decide that harbour is a word, because it is, and hand a guest a password that does not work. A door code rendered in a different numeral system is worse.
So those values are held out of the translation and put back verbatim. If you have ever received a message from a guest saying the WiFi password does not work when it demonstrably does, this is one of the reasons it happens elsewhere.
Translation refreshes on publish, which means the rule is simple: edit, publish, and every language catches up. There is no separate step and no per-language editing screen to keep in sync.
Caveat, stated plainly: machine translation is good now and it is not perfect. Idiom suffers. If you wrote "the boiler is a bit temperamental", some languages will render that literally and slightly oddly. Short, plain sentences translate well, which is also how you should be writing for guests anyway.
Why these two, together
Both features are attacking the same number: how many times a guest has to contact a host to find something out. The chat handles "I cannot find it". Translation handles "I cannot read it". In combination they cover a large share of the messages that arrive after 9pm.
Neither is magic and both depend entirely on the underlying guidebook being accurate. The tooling can make what you wrote findable in the dark, in the guest's own language, without waking you. It cannot know the bins moved to Wednesday.
What is not in this release
A few things hosts have asked about, so the answer is on the record:
No property management system sync. We do not connect to Airbnb, Vrbo, or any PMS, and nothing on the roadmap is close to shipping. What exists is different and worth naming precisely: you can paste your listing URL and the assistant will draft a first version of the guidebook from what the listing says. That is a writing shortcut: nothing syncs, no bookings flow in, and nothing updates automatically afterwards.
No paid add-ons. There were some. They are gone. Everything described here is part of the plan you are already on.
Next
The work in progress is on the local recommendations — making place cards carry the things a guest actually decides on, which at the moment means opening hours and how far away somewhere is. More on that when it lands.