You add AI to a dental practice by putting a conversational agent in front of new patient intake. It asks the questions your form asks, one at a time, types the answers into a structured record, and posts that record to your practice system the moment it is complete.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A stranger, usually outside opening hours, usually on a phone.
What it costs today
A clipboard at the door, 20 minutes of a patient sitting in your waiting room, and a member of staff re-typing it into your practice system.
What it has to produce
A complete, typed chart entry: complaint, history, insurance, contact, consent to be contacted.
20+ minutes
of patient and staff time consumed by paper intake per new patient
Practice by Numbers
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the record |
| phone | phone | Yes | How the desk calls back |
email | — | Confirmation and reminders | |
| chief_complaint | text | Yes | What they came for, in their words |
| symptom_duration | text | — | Triage between urgent and routine |
| insurance_provider | text | Yes | Eligibility check before they arrive |
| is_new_patient | boolean | Yes | Routes to the right appointment length |
| preferred_time | text | — | Fewer scheduling calls |
| last_cleaning | date | — | Hygiene recall on the same record |
And what it will not do
Collected data
284 collected19 this week4 need attention
Export CSVPriya Raman
Captured 2h ago · Oakline Dental · joina.chat
Captured data 6 of 7 fields
From the conversation
“Sharp pain upper left when I drink anything cold, a couple of weeks now and I am with Delta Dental.”
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": "New patient",
"record_id": 1234,
"attributes": {
"full_name": "Priya Raman",
"phone": "+1 415 555 0148",
"chief_complaint": "Cold sensitivity, upper left",
"insurance_provider": "Delta Dental",
"is_new_patient": "true"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a patient 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 chart.
Quotes are opt-in
The provenance block, the patient’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 practice system.
Free tier, no app to install, and it fires the moment the record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The front desk sees it before they pick up the phone.
Your own endpoint
Give us an https address, verify the signature, write it into the chart 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 |
|---|---|---|---|
| 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 | 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. Dentrix, Open Dental and Curve 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 chart.
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 | Paper or PDF form | Online form builder | Gnosari |
|---|---|---|---|
| When it can be filled | In your waiting room | Any time | Any time |
| Completion rate | High, but on your time | Drops with every field | Asks one thing at a time |
| Incomplete answers | Staff chases | Submitted as-is | It asks a follow-up |
| Gets into your system | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| Where the answer came from | The sheet | The field | The verbatim sentence, kept |
| Out of hours | Nothing | A form nobody reads until Monday | Answered, typed, delivered |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Gnosari runs the new-patient conversation your front desk would otherwise take by phone or on a clipboard: the complaint in the patient's own words, insurance details as printed on the card, medical history flags, preferred times and contact. It asks one question at a time on your website or through a link, then posts a typed intake record to your practice management system before the patient arrives.