You automate law firm intake by putting a conversational agent in front of the new matter enquiry. It takes the facts in the caller’s own words, one question at a time, types them into a structured matter record, and posts that record to your case management system before an attorney reads it.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who has never instructed a lawyer, at night, having a bad week, usually on a phone.
What it costs today
A voicemail nobody leaves a message on, a PDF intake form nobody completes, or an answering service that takes a name and cannot ask a single useful question.
What it has to produce
A typed matter: what happened, the practice area, the dates, the parties, anything already listed or looming, and the questions that need an attorney.
67%
of legal clients instruct the first attorney who answers them
Wildix
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the matter |
| phone | phone | Yes | How intake calls back |
| safe_to_leave_message | boolean | — | Asked in every matter, and it matters most in family ones |
| what_happened | text | Yes | The facts in their words, not a dropdown |
| practice_area | text | Yes | Routes to the right attorney |
| when_it_happened | text | Yes | Timing an attorney will check, never the agent |
| other_parties | text | — | Feeds the conflict search |
| scheduled_dates | text | — | Hearings and letter deadlines, recorded not assessed |
| prior_counsel | text | — | Whether anyone is already acting |
| flagged_questions | text | — | What they asked that needs an attorney, verbatim |
And what it will not do
Collected data
196 collected17 this week3 need attention
Export CSVRachel Okonjo
Captured 3h ago · New Matter Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“I got let go last week, I think because I raised a complaint in writing to HR in mid-June and now there is a letter with 14 days on it.”
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 matter",
"record_id": 1234,
"attributes": {
"full_name": "Rachel Okonjo",
"phone": "+1 312 555 0164",
"practice_area": "Employment",
"what_happened": "Dismissed after an internal complaint",
"when_it_happened": "Complaint mid-June, dismissal last week",
"scheduled_dates": "Letter states 14 days"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a caller 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 matter.
Quotes are opt-in
The provenance block, the caller’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 case management system.
Free tier, no app to install, and it fires the moment the matter record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The duty attorney sees the enquiry before the office opens.
Your own endpoint
Give us an https address, verify the signature, open the matter 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 |
|---|---|---|---|
| 22:41:09 | data.collected | Delivered | 200 OK |
| 22:41:06 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 16:30 | data.updated | Delivered | 200 OK |
| Fri 19:58 | 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. Clio, Lawmatics, MyCase, PracticePanther and Smokeball 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 matter.
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 intake form | Gnosari |
|---|---|---|---|
| At 10pm on a Friday | Rings out | Downloaded, never returned | Answered, typed, delivered |
| What you get back | A name, if they left one | Whatever fitted in the boxes | The facts in their own words |
| Half-told story | You call and ask | Submitted half empty | It asks the follow-up |
| Conflict names | Whoever they mentioned | One "other party" field | A separate agent, every name and entity |
| Gets into your case system | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| The advice 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 intake conversation a law firm would otherwise take on a Friday night voicemail: the practice area, what happened at a high level, the other parties, any dates the caller knows, and how to reach them. It asks one question at a time on your practice area pages or through a link, then posts a typed matter record to your case management system. The intake coordinator opens a complete matter on Monday morning.