Advisory firms add AI by putting a conversational agent in front of onboarding. It runs the KYC and fact find as a conversation, asks a follow up when an answer is incomplete, and returns a timestamped record your CRM can accept without a human re-typing it.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A prospect who has already said yes, and is now looking at a 14 page PDF.
What it costs today
Chased documents, incomplete returns, and an onboarding clock that restarts every time something comes back not in good order.
What it has to produce
Identity, source of funds, goals, time horizon, risk tolerance and attestations, each timestamped and traceable to what the client actually said.
70%
of financial institutions lost a client in the past year because onboarding was too slow
Fenergo, 2025
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_legal_name | text | Yes | Identity, as it appears on documents |
| date_of_birth | date | Yes | Identity verification |
email | Yes | Where the engagement pack goes | |
| phone | phone | Yes | Second channel for verification |
| residency_country | text | Yes | Determines which regime applies |
| employment_status | text | Yes | Suitability input |
| source_of_funds | text | Yes | AML requirement, in the client’s words |
| investable_assets | number | Yes | Segments the engagement |
| primary_goal | text | Yes | What the plan is actually for |
| time_horizon | number | Yes | Drives allocation |
| risk_tolerance | text | Yes | Suitability, captured as a reaction not a slider |
| existing_providers | list | — | Transfers and consolidation |
| is_politically_exposed | boolean | Yes | Enhanced due diligence trigger |
And what it will not do
Collected data
141 collected8 this week2 need attention
Export CSVTomas Lind
Captured 1h ago · Meridian Financial Group · joina.chat
Captured data 7 of 8 fields
From the conversation
“Sale of a business last year, plus normal savings. About 400. Thousand, yes ”
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": "Client onboarding",
"record_id": 1234,
"attributes": {
"full_legal_name": "Tomas Lind",
"residency_country": "United Kingdom",
"source_of_funds": "Business sale and savings",
"investable_assets": "400000",
"is_politically_exposed": "false"
}
}Two events
data.collected fires on the first record of a kind. data.updated fires when a dossier is corrected, which is the one an audit trail cares about.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before you write to a client file.
Quotes are opt-in
The provenance block carries the client’s verbatim words per field. Absent unless you turn it on, because sending them somewhere is a decision.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination, then map the attributes onto your CRM record.
Free tier, no app to install, and it fires instantly rather than on a poll.
Straight to the tool
Anything that accepts an incoming webhook takes the payload as it is.
No middleman and no per-task billing. Compliance sees it the moment it lands.
Your own endpoint
Give us an https address inside your perimeter, verify the signature, reconcile against the log.
A few lines of code, and nothing leaves through a third party.
And every attempt is on the record
| When | Event | Outcome | Detail |
|---|---|---|---|
| 11:31:04 | data.collected | Delivered | 200 OK |
| 11:30:58 | data.collected | Failed | Timeout after 10s, retrying |
| 10:12:41 | data.updated | Delivered | 200 OK |
| Yesterday 16:20 | data.collected | Failed | 401, signature rejected |
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. Redtail, Wealthbox and Practifi are reachable the same way: through a Zap, or straight to an endpoint inside your own perimeter. For a regulated file, "it probably arrived" is not an answer, which is why the log is part of the product.
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 | PDF fact find | Form builder | Gnosari |
|---|---|---|---|
| Completion | Chased over days | Abandoned mid form | One question at a time |
| Not in good order | Returned for correction | Submitted incomplete | It asks again before submitting |
| Ambiguous answers | Interpreted by staff | Stored as typed | Clarified in the conversation |
| Into the CRM | Re-keyed by hand | CSV or a paid connector | Signed webhook on completion |
| Audit trail | The scanned form | A timestamp | The verbatim sentence per field, opt in |
| Corrections | A second form | A second submission | data.updated, delivered |
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 fact find a financial adviser would otherwise chase through a PDF and three follow-up emails: identity, financial profile, goals, risk tolerance answers, beneficiaries and the documents still outstanding. It asks one question at a time through a link or on your onboarding page, then posts a timestamped record to your CRM. The adviser opens the discovery call with the pack already complete.