You automate gym intake by putting a conversational agent in front of the sign-up conversation. It asks for the goal, the experience level, the class or training style, and availability one question at a time, types the answers into a member record, and posts that record to your CRM before the front desk opens.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone browsing your class schedule or pricing page after hours, deciding whether this club or the next one gets their first message.
What it costs today
A PDF intake form or a PAR-Q handed over at the front desk, filled in once and rarely read again, with no follow-up on the goal underneath the checkbox.
What it has to produce
A typed member record: the goal in their own words, their experience level, the class or training style they want, and when they can actually come in.
50%
of new gym members quit within their first 90 days, most of them saying they felt lost from day one
SmartHealthClubs
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the member record |
| phone | phone | Yes | How the club calls back |
email | Yes | Where the confirmation and receipts go | |
| primary_goal | text | Yes | The real goal, in their own words, not a checkbox |
| experience_level | text | Yes | Sets the starting point a coach builds from |
| preferred_class_type | text | — | Which class or format actually fits them |
| availability_days | text | — | When they can realistically show up |
| condition_or_limitation | text | — | Flags a condition for a coach to review, never clears it |
| membership_plan | text | — | Which membership they are already on, for existing-member requests |
| reason_for_cancelling | text | — | The reason behind a cancellation, recorded honestly |
And what it will not do
Collected data
211 collected26 this week5 need attention
Export CSVMarcus Webb
Captured 1h ago · New Member Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“I used to lift a few years ago but it's honestly been a while and I don't really know where to start again , figured I'd just ask before showing up.”
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 member",
"record_id": 1234,
"attributes": {
"full_name": "Marcus Webb",
"phone": "+1 512 555 0148",
"email": "marcus.webb@example.com",
"primary_goal": "Get stronger, returning after a few years off",
"experience_level": "Returning, used to lift regularly",
"preferred_class_type": "Group classes"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a member 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 member profile.
Quotes are opt-in
The provenance block, the member'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 member record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The front desk sees the enquiry before the coach 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 |
|---|---|---|---|
| 18:22:07 | data.collected | Delivered | 200 OK |
| 18:22:04 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 11:15 | data.updated | Delivered | 200 OK |
| Yesterday 06:48 | 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. Mindbody, Zen Planner, Trainerize, TrueCoach and Wodify 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 member 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 | Front desk and a clipboard | PDF or web intake form | Gnosari |
|---|---|---|---|
| After hours | Waits for the desk to open | Downloaded, rarely returned | Answered, typed, delivered |
| What you get back | A name, if they stopped by | Whatever fitted in the boxes | The goal in their own words |
| Half-told story | Staff ask again in session one | Submitted half empty | It asks the follow-up |
| A condition or injury | Whatever they mention verbally | A checkbox with no detail | Recorded as described, flagged for a coach |
| Gets into your CRM | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| The training and medical 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.
Name the fields your intake form already has, point the agent at your class schedule and pricing pages, and put the link on your site. The agent runs the conversation, produces a typed member record, and posts it to your CRM through a webhook, Zapier or Make. Setup is minutes, not an implementation project.