You automate travel agency intake by putting a conversational agent in front of the trip enquiry. It asks for the destination, the dates, the group size and the kind of trip, one question at a time, types the answers into a traveler record, and posts it to your booking software before anyone replies.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone comparing five browser tabs at 11pm, unsure where to start, typing instead of calling because the office closed hours ago.
What it costs today
A 42-hour average reply time on emailed questionnaires, or a PDF intake form that asks a solo backpacker the same questions as a family of six.
What it has to produce
A typed traveler record: the destination, the dates and how flexible they are, the group, the kind of trip, and anything urgent enough to need a person today rather than next week.
78%
of travelers buy from the first travel company that responds
Vendasta
| Field | Type | Required | Why it is there |
|---|---|---|---|
| traveler_name | text | Yes | Identity on the traveler record |
| contact_method | phone | Yes | How the agency follows up |
| destination_interest | text | Yes | Where the trip is headed |
| travel_dates_flexibility | text | Yes | Times the itinerary is built around |
| group_size | number | Yes | Sizes the proposal and any group rates |
| trip_type | text | Yes | Sets the pace: adventure, leisure, luxury |
| budget_range | text | — | Shapes options without a promised price |
| dietary_or_medical_notes | text | — | Feeds the operational record before departure |
| insurance_interest | boolean | — | Flags a travel-insurance follow-up |
| special_occasion | text | — | The moment behind the trip |
And what it will not do
Collected data
164 collected21 this week4 need attention
Export CSVPriya Anand
Captured 1h ago · New Trip Enquiry · joina.chat
Captured data 6 of 8 fields
From the conversation
“We are six people total, my sister’s family and us, thinking maybe Portugal, maybe Greece, not totally sure yet , sometime in the spring.”
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": "New trip enquiry",
"record_id": 1234,
"attributes": {
"traveler_name": "Priya Anand",
"contact_method": "+1 512 555 0148",
"destination_interest": "Portugal or Greece",
"travel_dates_flexibility": "Spring, dates not fixed",
"group_size": "6",
"trip_type": "Mixed: beach and exploring"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a traveler 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 proposal.
Quotes are opt-in
The provenance block, the traveler’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 booking software.
Free tier, no app to install, and it fires the moment the traveler record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The consultant sees the enquiry before the itinerary does.
Your own endpoint
Give us an https address, verify the signature, open the record 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:04:22 | data.collected | Delivered | 200 OK |
| 19:04:18 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 09:37 | data.updated | Delivered | 200 OK |
| Yesterday 07:52 | 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. FareHarbor, Rezdy, Checkfront and TravelJoy 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 record.
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 | Back-and-forth emails | Static intake form | Gnosari |
|---|---|---|---|
| After hours | Sits in an inbox until morning | Downloaded, never returned | Answered, typed, delivered |
| What you get back | Whatever they thought to write | Whatever fit in the boxes | The trip in their own words |
| Half-told story | Staff email back to ask | Submitted half empty | It asks the follow-up |
| Group and dates | Buried in a paragraph | A dropdown with no context | Structured, ready for a proposal |
| Gets into your booking software | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| The fare and visa line | Depends who answered | Not applicable | Never crossed, and stated at the start |
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 destinations pages, and put the link on your site. The agent runs the conversation, produces a typed traveler record, and posts it to your booking software through a webhook, Zapier or Make. Setup is minutes, not an implementation project.