You automate restaurant intake by putting a conversational agent in front of the messages that arrive before staff answer the phone. It asks for the event, the headcount, the date and any allergy in the guest's own words, types it into a structured record, and posts it to your POS before anyone calls back.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone planning a birthday dinner, an office party, or a rehearsal dinner, usually typing mid-thought, usually not during the coordinator's hours.
What it costs today
A phone line answered between table service, or an inbox thread that starts with a PDF menu and takes four back-and-forth emails just to get the headcount and the date.
What it has to produce
A typed event brief: who to call back, the date, the kind of event, roughly how many guests, and anything the group already knows it needs, before the coordinator ever picks up the phone.
43%
of inbound restaurant calls go unanswered, and most of those callers never call back
Hostie AI
| Field | Type | Required | Why it is there |
|---|---|---|---|
| contact_name | text | Yes | Who the coordinator calls back |
| phone | phone | Yes | The callback number |
email | — | Email if the guest prefers it | |
| event_date | date | Yes | The date the group has in mind |
| event_type | text | Yes | Routes the inquiry to the right template |
| guest_count | number | Yes | Sizes the room and the kitchen prep |
| budget_range | text | — | Feeds the coordinator's quote, never a promise from the agent |
| space_preference | text | — | Private room, patio, or a full buyout |
| dietary_needs_mentioned | text | — | Flags a group dietary conversation before anyone commits to a date |
And what it will not do
Collected data
138 collected19 this week3 need attention
Export CSVJonah Ferreira
Captured 1h ago · Private Event Inquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“We're doing a holiday party for the office, not totally sure on the final headcount yet , could be anywhere from 30 to 45.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. The chatbot 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": "Private event inquiry",
"record_id": 1234,
"attributes": {
"contact_name": "Jonah Ferreira",
"phone": "+1 415 555 0132",
"event_date": "December 12",
"event_type": "Corporate holiday party",
"guest_count": "40",
"space_preference": "Private room preferred"
}
}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 opens a ticket.
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 reservation system or POS.
Free tier, no app to install, and it fires the moment the record is complete.
Straight to the floor
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The manager sees the inquiry before the coordinator opens email.
Your own endpoint
Give us an https address, verify the signature, open the ticket 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 |
|---|---|---|---|
| 19:14:09 | data.collected | Delivered | 200 OK |
| 19:14:02 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 11:22 | data.updated | Delivered | 200 OK |
| Yesterday 08:47 | 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. Toast, Square, OpenTable, Resy, SevenRooms and 7shifts 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 booking.
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 | Phone tag and voicemail | Generic web form | Gnosari |
|---|---|---|---|
| After hours | Rings out | Downloaded, never returned | Answered, typed, delivered |
| What you get back | A name, if they left one | Whatever fitted in the boxes | The event, in their own words |
| An allergy question | Whoever answers guesses | Not applicable | Recorded and routed to the kitchen, never guessed |
| Party size grows same-day | A scramble at the door | No way to flag it | Escalated to a manager before arrival |
| Half-told story | Staff call back to ask | Submitted half empty | It asks the follow-up |
| Gets into your POS | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Name the fields your intake form already has, point the agent at your menu and events pages, and put the link on your site. The agent runs the conversation, produces a typed record, and posts it to your POS or reservation system through a webhook, Zapier or Make. Setup is minutes, not an implementation project.