You automate school admissions intake by putting a conversational agent in front of the first parent inquiry. It asks for the child's grade, the start term and the reason for looking, types the answers into a structured inquiry record, and posts it to your admissions office before anyone calls back.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A parent researching schools after the kids are in bed, comparing a page that answers in two minutes against one that asks them to create a portal account before they can even ask a question.
What it costs today
An office line that goes to voicemail after 4pm, or a multi-page inquiry form that asks for the same family details whether the child is starting kindergarten or transferring in mid-year.
What it has to produce
A typed inquiry record: the child, the grade and term, the reason the family is looking now, and whether a tour would help - handed to the admissions office, not decided by the conversation that collected it.
24%
of families who start an application never finish it - the follow-up email arrives after they’ve already toured somewhere else
Brown University
| Field | Type | Required | Why it is there |
|---|---|---|---|
| parent_full_name | text | Yes | Identity on the inquiry record |
| phone | phone | Yes | How the office calls back |
email | Yes | Where the follow-up lands | |
| child_first_name | text | Yes | Which child this inquiry is about |
| grade_applying_for | text | Yes | Routes to the right admissions timeline |
| desired_start_term | text | Yes | When the family needs an answer by |
| current_school | text | — | Context for the transition, never a judgment |
| reason_for_interest | text | — | The reason, in their own words |
| tour_interest | boolean | — | Whether to offer a tour next, never a decision |
| learning_support_needs | text | — | Feeds the fit conversation, never an accommodation promise |
And what it will not do
Collected data
148 collected19 this week3 need attention
Export CSVAmara Osei
Captured 1h ago · Admissions Inquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“We’re moving in July and still deciding between three schools , but Naomi really wants smaller classes this time.”
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 inquiry",
"record_id": 1234,
"attributes": {
"parent_full_name": "Amara Osei",
"phone": "+1 617 555 0173",
"email": "amara.osei@example.com",
"child_first_name": "Naomi",
"grade_applying_for": "4th grade",
"reason_for_interest": "Wants smaller class sizes and more art"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a family 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 file.
Quotes are opt-in
The provenance block, the family’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 admissions CRM.
Free tier, no app to install, and it fires the moment the inquiry record is complete.
Straight to the office
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The admissions assistant sees the inquiry before the tour calendar does.
Your own endpoint
Give us an https address, verify the signature, open the file 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. Slate, Blackbaud, Veracross, FACTS and Ravenna 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 file.
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 | Voicemail and a callback | PDF or web inquiry form | Gnosari |
|---|---|---|---|
| After hours | Rings out | Downloaded, never returned | Answered, typed, delivered |
| What you get back | A name, if they left one | Whatever fit in the boxes | The reason in their own words |
| Half-told story | Staff call back to ask | Submitted half empty | It asks the follow-up |
| Grade and start term | Whatever they say on the phone | A dropdown that doesn’t fit their case | Recorded exactly, flagged to confirm |
| Gets into your admissions CRM | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it’s complete |
| The admissions 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.
Gnosari runs the admissions inquiry a school would otherwise take by phone during office hours: the child's grade and start date, what the family is looking for, tour and open-day interest, and how to reach them. It asks one question at a time on your admissions pages or through a link, then posts a typed inquiry record to your admissions CRM. Your office opens a complete inquiry the next morning instead of a voicemail.