You automate coaching client intake by putting a conversational agent in front of the pre-discovery-call conversation. It asks the situation, the goal, and what’s been tried one question at a time, types it into a client brief, and hands it to the coach before the call, never quoting a fee or giving advice.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who typed "I don’t really know where to start" at 11pm, before the discovery call is even booked, because a static form felt like a wall between them and getting help.
What it costs today
A Typeform sent ahead of the call that more than half of prospects never finish, or a discovery call spent asking the same three questions the form should already have answered.
What it has to produce
A typed client brief: the situation in their own words, the goal, what they’ve already tried, and whether this looks like a one-on-one or group fit, before the coach ever picks up the phone.
47%
of prospects who start a coaching intake form actually finish it
Typeform
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Whose name goes on the client brief |
email | Yes | Where the confirmation and the brief land | |
| current_situation | text | Yes | The situation, in their own words, not squeezed into a text box |
| primary_goal | text | Yes | What they want different - the line the discovery call opens with |
| what_youve_tried | text | — | So the coach doesn’t spend the call re-asking what’s already been tried |
| preferred_format | text | — | Routes the call itself: one-on-one or group |
| best_time_to_talk | text | — | When they’re actually free, not just when the form happened to be open |
And what it will not do
Collected data
141 collected18 this week3 need attention
Export CSVJordan Ames
Captured 1h ago · Discovery Call Intake · joina.chat
Captured data 6 of 7 fields
From the conversation
“I’ve been going back and forth on this for months, not sure if I even need a coach or just need to make a decision , but a friend said I should at least talk to someone.”
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": "New prospect",
"record_id": 1234,
"attributes": {
"full_name": "Jordan Ames",
"email": "jordan.ames@example.com",
"current_situation": "Stuck on a decision for months, going back and forth on my own",
"primary_goal": "Actually make the call and move, instead of stalling",
"what_youve_tried": "Talked it through with friends, kept circling back",
"preferred_format": "One-on-one, hasn’t done group before"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a prospect or client 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 record.
Quotes are opt-in
The provenance block, the person’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.
Free tier, no app to install, and it fires the moment the client brief is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. You see the brief before the discovery call does.
Your own endpoint
Give us an https address, verify the signature, open the record 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. HoneyBook, Dubsado, CoachAccountable and Practice 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 brief.
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 | Typeform + Calendly | Discovery call, cold | Gnosari |
|---|---|---|---|
| Completion | 47% finish the form | Nobody drops off, but the call runs over | Answered and typed before the call |
| What you get back | Whatever fit in the boxes | Whatever they remember to say out loud | The situation in their own words |
| Vague answer | Left blank, or generic | The coach spends call time probing | It asks the follow-up |
| Program fit | Guessed from a dropdown | Figured out live on the call | Screened before anyone books |
| Gets into your CRM | Re-typed by hand | Typed into notes after the fact | Signed webhook, the moment it is complete |
| The advice line | Not applicable | 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 intake already asks for, point the agent at your services pages, and put the link on your site. The agent runs the conversation, produces a typed client brief, and posts it to your CRM through a webhook, Zapier or Make. Setup is minutes, not an implementation project.