You automate first notice of loss by putting a conversational agent in front of the intake conversation. It asks what happened, when, and whether anyone needs help right now, one question at a time, types the answers into a structured claim file, and posts that file to your AMS before anyone calls back.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone whose car was hit, whose pipe burst, or whose roof lost shingles in a storm, usually within hours of it happening and often outside office hours.
What it costs today
An FNOL call that averages six to seven minutes when someone actually picks up, or a voicemail that goes unanswered until Monday while the loss sits unreported.
What it has to produce
A claim file: who, what happened, when, whether anyone else was involved, and whether it needs a person right now rather than a form.
60%
of manually completed FNOL forms contain an error that has to be chased before the claim can move
EasySend
| Field | Type | Required | Why it is there |
|---|---|---|---|
| policyholder_full_name | text | Yes | Whose file this is |
| phone | phone | Yes | How the agency calls back |
| policy_number | text | — | Speeds up the file, never required to start it |
| date_of_loss | date | Yes | When it happened, for the file and for any deadline |
| loss_type | text | Yes | Routes it to the right desk |
| loss_description | text | Yes | What happened, in their own words |
| other_parties_involved | text | — | Other drivers, tenants or witnesses |
| police_report_filed | boolean | — | Whether a report already exists to pull |
| injuries_reported | boolean | — | The one field that can stop everything else |
| preferred_contact_time | text | — | When the desk should call back |
And what it will not do
Collected data
132 collected19 this week3 need attention
Export CSVDana Okafor
Captured 1h ago · Claims Intake · joina.chat
Captured data 7 of 8 fields
From the conversation
“We just got home and found water everywhere, not totally sure how long it had been running , we shut the main valve off as soon as we saw 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 claim",
"record_id": 1234,
"attributes": {
"policyholder_full_name": "Dana Okafor",
"phone": "+1 512 555 0173",
"date_of_loss": "2026-08-11",
"loss_type": "Home, water damage",
"loss_description": "Basement flooded, main valve shut off"
}
}Two events
data.collected fires the first time a claim file opens. data.updated fires when a policyholder corrects or adds to it.
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 claim.
Quotes are opt-in
The provenance block, the policyholder’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 AMS.
Free tier, no app to install, and it fires the moment the file is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The claims desk sees the file before the adjuster 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 |
|---|---|---|---|
| 02:14:47 | data.collected | Delivered | 200 OK |
| 02:14:41 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 14:02 | data.updated | Delivered | 200 OK |
| Yesterday 08:19 | 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. Applied Epic, EZLynx, Vertafore AMS360 and HawkSoft 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 | Phone call to the office | PDF or web claim form | Gnosari |
|---|---|---|---|
| After hours | Rings out to voicemail | Downloaded, never returned | Answered, typed, delivered |
| What you get back | A name, if they left one | Whatever fit in the boxes | What happened, in their own words |
| Half-told story | Staff call back to ask | Submitted half empty | It asks the follow-up |
| An active emergency | Depends who answered | Not applicable | Stops and says call 911, every time |
| Coverage questions | Whoever picks up guesses | Not asked at all | Never answered, always routed to an agent |
| Gets into your AMS | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Gnosari takes the first notice of loss an agency would otherwise receive as a 2am voicemail: the policyholder, the policy if they know it, what happened in their own words, when and where, photos if they have them, and how to reach them. It asks one question at a time on your site or through a link, then posts a typed claim file to your agency management system before the office opens.