You automate SaaS data collection by putting a conversational agent in front of each moment that matters: demo requests, bug reports, security questionnaires and churn exits. It asks one question at a time, types every answer into a structured record, and posts that record straight to your CRM or database.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A visitor who read the pricing page twice, clicked "request a demo," and is now looking at a six-field form that asks for a job title before it asks what they are trying to solve.
What it costs today
A form that either asks too little, so sales spends its time on leads that were never going to buy, or asks too much, so the visitor abandons it before the submit button.
What it has to produce
A qualified record: who they are, the team size, the tool they use today, the exact workflow they want automated, and how soon they need it live.
40%
of a sales team's time goes to leads that were never qualified to begin with
PreCallAI
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Who to follow up with |
| work_email | email | Yes | How the team reaches back out |
| company_name | text | Yes | Routes the record to the right account |
| team_size | text | Yes | Sizes the opportunity, honestly |
| current_tool | text | — | What they are replacing, if anything |
| primary_workflow | text | Yes | The actual workflow, in their language, not "efficiency" |
| timeline | text | Yes | How urgently this needs to happen |
And what it will not do
Collected data
211 collected34 this week6 need attention
Export CSVPriya Anand
Captured 1h ago · Demo Qualification · joina.chat
Captured data 7 of 8 fields
From the conversation
“Honestly our onboarding form is killing signups, people just abandon it halfway through , we have no idea how many we are losing there.”
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": "Demo request",
"record_id": 1234,
"attributes": {
"full_name": "Priya Anand",
"work_email": "priya@northlineops.com",
"company_name": "Northline Ops",
"team_size": "~15 people",
"current_tool": "Google Forms + spreadsheet",
"primary_workflow": "Onboarding intake, too many drop-offs",
"timeline": "This month"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when someone 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 CRM record.
Quotes are opt-in
The provenance block, the visitor'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 CRM or helpdesk.
Free tier, no app to install, and it fires the moment the record is complete.
Straight to the team
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The right team sees the record before it ages into a stale ticket.
Your own endpoint
Give us an https address, verify the signature, write it 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. Salesforce, HubSpot, Zendesk, Linear and Jira 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 record.
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 | A static demo form | Slack, tickets, spreadsheets | Gnosari |
|---|---|---|---|
| What you get back | Whatever fitted in the fields | Whatever someone remembered to type up | The workflow in their own words |
| Half-told story | Sales calls back to ask | Sits until someone triages it | It asks the follow-up |
| Unqualified leads | Sales finds out on the call | No qualification step at all | Filtered before it reaches a rep |
| Churn signal | A checkbox: "too expensive" | Never collected at all | The actual reason, in their words |
| Gets into your CRM | Re-typed by hand | CSV export, if anyone remembers | Signed webhook, the moment it is complete |
| The commitment line | Depends who wrote the copy | 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 demo form already has, point the agent at your pricing and product pages, and put the link or widget on your site. The agent runs the conversation, produces a qualified record, and posts it to your CRM through a webhook, Zapier or Make. Setup is minutes, not an implementation project.