01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
It greets the visitor, asks what they need, and gets name, email and budget or timeline before you ever reply. Every conversation lands as a lead record you can export or push to your CRM.
It opens with
What comes back
typed · validated · deduped
01Someone shows up
“What are you actually after?”
Intent, need and urgency
02Are we a fit?
“Budget, timeline, what you need it to do?”
Qualified or not, with the reasons
03What will it cost?
“Scope, volume, the specifics?”
A quote request you can price
04Sign them up
“Details, preferences, who else to contact?”
A complete client file
05Prove itAnswered by upload, not by typing
“Upload your licence and I will read it.”
Typed identity fields, nobody re-typing
06Something changed
“What do you need now?”
A change request, routed
07How did we do?
“What worked, what did not?”
Structured feedback you can compare
08Still good?
“Anything changed since last time?”
A check-in that lines up with the last
You do not buy one of these. Every step above is the same account, the same inbox, and the same five minutes.
In · the conversation
Out · Qualified lead
Qualifies visitors in conversation instead of a form, against your own criteria - need, budget, timeline, fit - and hands you the ones worth your time.
No screenshots. This is it
Five live Gnosaris, built with the same wizard you would use. Two are the chat widget, three are full conversation pages. Say anything and watch how they steer.
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 · What you write down
| Field | Type | Req |
|---|---|---|
| Full name | text | yes |
email | yes | |
| Phone | phone | — |
| Budget | number | — |
| Move-in date | date | — |
| Has pets | boolean | — |
| Must-haves | list | — |
Seven types. Every value that comes back is validated against the one you picked, so a date is a date and a number is a number.
02 · How it should ask
ai_hint on “Budget”
“A range is fine. Never push if they decline.”
It asks
“Roughly what were you hoping to spend? A ballpark is completely fine.”
One line of plain English per field, and only where you want one. It is the difference between an interrogation and a conversation.
03 · What lands
Typed, validated, and carrying the exact words it came from. Nothing the visitor did not say is ever stored.
Collected data
316 collected12 this week3 need attention
Export CSVPriya Raman
Captured 2h ago · Brightwave Studio · joina.chat
Captured data 6 of 7 fields
From the conversation
“We are a studio called Fieldnotes, and I have about eight to twelve thousand set aside for a rebrand.”
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": "Qualified lead",
"record_id": 1234,
"attributes": {
"full_name": "Priya Raman",
"email": "priya@fieldnotes.co",
"budget": "$8,000 - $12,000",
"timeline": "Before end of Q3"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a record changes, which is the one an audit trail cares about.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before you write anything to your own database.
Retried, and logged either way
A failed delivery retries on its own and the dashboard keeps every attempt with the reason it failed. Quotes from the conversation ride along only if you turn them on.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination. That is the whole setup.
Free tier, no Gnosari app to install, and it fires instantly rather than on a poll.
Straight to the tool
Anything that accepts an incoming webhook takes the payload as it is.
No middleman and no per-task billing. You map the fields once.
Your own endpoint
Give us an https address, verify the signature, write it wherever you like.
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 |
|---|---|---|---|
| 09:14:22 | data.collected | Delivered | 200 OK |
| 09:14:20 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 17:02 | data.updated | Delivered | 200 OK |
| Yesterday 11:48 | data.collected | Failed | 401, signature rejected |
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. A webhook reaches anything that accepts one, and Zapier and Make cover several thousand more between them. If your system takes an HTTP request, it takes a Gnosari record.
Conversations
Brightwave Studio22 msgs · 2h ago
Studio rebrand plus a new site, budget stated, wants to start before Q3 closes.
quoterebrandbudgettimeline
The Alder House9 msgs · 5h ago
Room was fine, check-in queue was not. Asked for a late checkout and did not get one.
feedbackcheck-instaffing
Oakline Dental14 msgs · Yesterday
New patient, existing crown, nervous about the drill. Flagged for a longer first slot.
intakenew patientanxiety
Northpoint Moving11 msgs · Mon
Two-bed flat, third floor, no lift. Asked twice about insurance and left without booking.
enquiryaccessinsurance
The summary is written from the conversation, not from the fields, so a visitor who asked three questions and never left a detail still tells you something. Those are the ones that never reach a form.
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.
01 · What you give it
02 · What it does with it
Answered from your opening-hours page
Not in your content, so it goes to a human instead
Same thread, same Gnosari. The second answer is not a failure, it is the rule working: it will not invent one.
The rule is enforced in code, not in a prompt: a value is only ever stored when it can be traced to something the visitor actually said. A Gnosari's own words can never become your data.
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.
Visitor says“We are a family of four, hoping to move somewhere quieter.”
01Passive
“That sounds like a big change. What is drawing you away from where you are now?”
The same 4 fields
You write nothing
02Opportunistic
“A quieter spot with room for four, got it. Roughly when are you hoping to move?”
The same 4 fields
You write nothing
03Active
“Lovely. So I can send the right places, what is your monthly budget?”
The same 4 fields
You write nothing
04Guided
“Thanks. First question of six: which areas are you considering?”
Your script, in your order
You write the script
Guided is the only position that takes a script of your own. The other three write their own questions from the fields you named, and every position writes the same record.
Your trait library 4 of 5 on this Gnosari
One Question at a TimeAttached
Asks a single question per message - never dumps a checklist
weight 1.5
Stays On TopicAttached
Politely refuses off-topic requests and steers back to its purpose - won't be used as a general assistant
weight 1.5
Conversational CloseAttached
Ends an intake conversation cleanly - recaps captured details, confirms, states next step, then stops
weight 1.3
Conversational ReadabilityAttached
Short, scannable chat messages with a clean bolded recap, without turning replies into a formatted document
weight 1.2
Acknowledge and Keep It ShortIn library
Reflects back what the visitor said, then responds in 2-3 sentences
weight 1.3
01 · You ask
“Build me a Gnosari for my dental practice that books first visits. Read oaklinedental.com, collect name, phone, insurance and whether they are nervous, then give me the link.”
02 · It calls the tools
03 · It is live
Published
joina.chat/l/first-visit
A real, published Gnosari. It shows up in the app like any other, and the records land in the same inbox.
Add this server
https://mcp.gnosari.com
Paste it into your client's connector settings. Sign in to Gnosari when it asks. There is no key to copy and nothing to install.
Works in
Not on the list? The setup is the same whatever the trade: name the fields, point it at your site, share the link.
Free
$0
Build one, publish it, collect real records. No card, no trial clock.
