You collect patient information before the appointment by putting a conversational agent in front of intake. It asks what your registration form asks, one question at a time, keeps asking until the required fields are filled, and posts a typed record to your system before the patient arrives.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A patient at home, on a phone, usually the evening before, often having put the whole thing off for months.
What it costs today
A portal login nobody completes, a clipboard filled in under time pressure, and a front desk re-typing it into the record while the waiting room backs up.
What it has to produce
A complete registration: demographics, contact that reminders will actually reach, insurance as printed, medicines, allergies, and the reason for the visit in the patient’s own words.
74%
of patients would rather complete intake digitally before the visit than on arrival
Interlace Health
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the record |
| date_of_birth | date | Yes | Matches the patient to the right chart |
| phone | phone | Yes | The number reminders go to, which is where no-shows start |
| reason_for_visit | text | Yes | In their words, so the provider reads what was actually said |
| how_long | text | — | Duration as the patient describes it, never as a finding |
| insurance_plan | text | Yes | Eligibility verified by a person, never confirmed here |
| member_id | text | — | As printed. Never a full card number |
| current_medications | text | — | Recorded as described, even "a small white one" |
| medication_allergies | text | — | The field a paper form loses most often |
| history_notes | text | — | One open question, and never pushed |
And what it will not do
Collected data
531 collected44 this week7 need attention
Export CSVNadia Sharif
Captured 1h ago · New Patient Registration · joina.chat
Captured data 7 of 8 fields
From the conversation
“My back, it has been playing up for a few months now, and I take a small white one for blood pressure but I do not know the name.”
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": "Patient registration",
"record_id": 1234,
"attributes": {
"full_name": "Nadia Sharif",
"date_of_birth": "1984-03-17",
"phone": "+1 617 555 0139",
"reason_for_visit": "Back, playing up a few months",
"insurance_plan": "Aetna Choice POS II",
"medication_allergies": "Penicillin"
}
}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 reaches 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 registration is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The front desk sees the registration before the patient arrives.
Your own endpoint
Give us an https address, verify the signature, write it into 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 |
|---|---|---|---|
| 20:12:35 | data.collected | Delivered | 200 OK |
| 20:12:32 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 14:07 | data.updated | Delivered | 200 OK |
| Yesterday 08:51 | 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. Epic, Athenahealth, eClinicalWorks, Kareo and NextGen 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 registration.
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 clipboard | Portal or PDF form | Gnosari |
|---|---|---|---|
| When it gets filled in | In your waiting room | In theory, beforehand | Whenever they have five minutes |
| What it costs the patient | Ten minutes and a pen | An account and a password | Nothing to set up |
| Half-completed forms | Staff chase at the desk | Submitted as-is, page 4 blank | It asks the follow-up |
| Vague answers | Left vague | Left vague | Recorded verbatim, flagged as unknown |
| Gets into your system | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| The clinical line | Depends who is on the desk | 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 registration form already has, then send the patient a link after they book. The agent runs the conversation, keeps asking until the required fields are filled, and posts a typed record to your practice system through a webhook, Zapier or Make. There is no portal account for the patient to create, which is the step most pre-registration loses people at.