You add AI to a hotel by putting a conversational agent on every guest touchpoint you currently run as a form: the direct enquiry, pre-arrival requirements, in-stay problems and post-stay feedback. Each one types the guest’s own words into a structured record and posts it to your property system.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A guest on a phone, at night, comparing you against three other places and a booking site.
What it costs today
A contact form with four boxes, an inbox nobody reads until morning, and a booking site that keeps the email address and charges you commission for it.
What it has to produce
Dates, party, what the trip is for, what matters about the room, and an email address that belongs to you.
34%
of valid guest email addresses are all a hotel typically captures
Revinate
| Field | Type | Required | Why it is there |
|---|---|---|---|
| guest_name | text | Yes | Identity on the enquiry |
email | Yes | The address a booking site would have kept | |
| dates | text | Yes | A rough window is a real answer |
| adults | number | Yes | Which rooms can work at all |
| children_and_ages | text | — | Asked as a room question, never a personal one |
| trip_purpose | text | Yes | The line an OTA never passes on |
| room_priorities | text | — | Quiet, a bath, ground floor, somewhere to work |
| needs_parking | boolean | — | Decides the arrival, and it is always asked too late |
| stayed_before | boolean | — | A returning guest handled like a stranger is the worst outcome |
And what it will not do
Collected data
368 collected29 this week5 need attention
Export CSVHelena Marsh
Captured 40m ago · Booking Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“A weekend in October, just the two of us, it’s our anniversary so somewhere quiet with a bath if you have one.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. A Gnosari cannot quote itself into your data.
From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.
Signed headers
Body
{
"type": "data.collected",
"event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
"created_at": "2026-08-11T09:14:22Z",
"payload_version": "v1",
"data_kind": "Guest enquiry",
"record_id": 1234,
"attributes": {
"guest_name": "Helena Marsh",
"email": "h.marsh@example.com",
"dates": "A weekend in October",
"adults": "2",
"trip_purpose": "Anniversary",
"room_priorities": "Quiet, a bath"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a guest corrects something.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before it touches a reservation.
Quotes are opt-in
The provenance block, the guest’s verbatim words, is absent unless you turn it on for that destination.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination, then point the Zap at your property system.
Free tier, no app to install, and it fires the moment the enquiry is complete.
Straight to reception
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The night manager sees the enquiry before the morning shift.
Your own endpoint
Give us an https address, verify the signature, write it into the guest profile yourself.
A few lines of code, and the delivery log tells you when something did not land.
And you can see every attempt
| When | Event | Outcome | Detail |
|---|---|---|---|
| 23:04:18 | data.collected | Delivered | 200 OK |
| 23:04:15 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 21:40 | data.updated | Delivered | 200 OK |
| Sun 10:12 | data.collected | Delivered | 200 OK |
Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.
These are examples, not a partner list. Mews, Cloudbeds, Apaleo, Opera and Little Hotelier are all reachable the same way: through a Zap, or straight to an endpoint you control. If it takes an HTTP request, it takes the guest.
A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.
Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.
display_mode="bubble" A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.
Four corners to choose from
display_mode="sidebar" A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.
Left or right, any width
display_mode="sidebar-push" The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.
Left or right, any width
display_mode="drawer" Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.
Left or right
01 · A link you send
Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.
02 · A code they scan
Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.
03 · A flyer you hand over
A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.
Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.
22 colour themes
44 background patterns
Every pattern, four intensities
Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.
A boutique hotel
A developer tool
fontFamily accepts fourteen faces
Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.
| What changes | Contact form | Booking site | Gnosari |
|---|---|---|---|
| At eleven at night | Sits in an inbox | Books instantly | Answered, typed, delivered |
| Whose guest is it | Yours | Theirs | Yours |
| The email address | If they typed it | Masked or withheld | Asked for, and kept |
| Why they are coming | A free-text box nobody fills | Never captured | Asked, and the answer is the record |
| Commission | None | Every booking | None |
| When something goes wrong | You find out in a review | You find out in a review | You find out while they are still in the room |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Gnosari replaces the enquiry forms a hotel runs today with a conversation: the direct booking enquiry, pre-arrival requirements, an in-stay problem, a group request, a change and post-stay feedback. It asks in your voice, one question at a time, records the guest's own words as a typed record and posts it to your property system. Reservations answers a complete enquiry, and the guest's email address belongs to you, not to a booking site.