You add AI to a salon by putting a conversational agent on the messages you already answer by hand: the booking enquiry, the skin test that has to happen 48 hours before colour, the reschedule, the win-back and the complaint. Each one types the client’s own words into a structured record and posts it to your salon software.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A client on a phone, usually after closing, comparing you against the salon down the road.
What it costs today
A message answered the next afternoon with a question rather than an answer, then three more messages to find out hair length, colour history and when they are free.
What it has to produce
What they want, how long the appointment needs to be, whether colour is involved and therefore whether a skin test is due, and when they can actually come.
40-50%
of salon appointment bookings happen after business hours, when nobody is there to ask the questions
Boulevard Industry Report
| Field | Type | Required | Why it is there |
|---|---|---|---|
| client_name | text | Yes | Identity on the enquiry |
| contact | text | Yes | Phone or email, whichever they gave |
| service_wanted | text | Yes | What they are after, in their words |
| whats_bothering_them | text | — | For the client who cannot name a service, which is most of them |
| existing_client | boolean | Yes | A regular gets their stylist, a new client needs longer |
| hair_length | text | — | It sets the appointment length, which is why the desk always asks |
| involves_colour | boolean | Yes | Forces the skin test, and the skin test is never waived |
| last_colour | text | — | Box dye, henna, a keratin: what reacts with what |
| availability | text | Yes | A range, not a slot the agent cannot promise |
| occasion | text | — | A wedding changes the timing, and it is offered not extracted |
And what it will not do
Collected data
412 collected31 this week4 need attention
Export CSVPriya Shah
Captured 25m ago · New Client Consultation · joina.chat
Captured data 6 of 7 fields
From the conversation
“maybe balayage? my hair is a bit of a state honestly, box dye during lockdown and a keratin last year, if that counts.”
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": "Client consultation",
"record_id": 1234,
"attributes": {
"client_name": "Priya Shah",
"email": "priya.shah@example.com",
"service_wanted": "Balayage, maybe",
"previous_chemical_services": "Box dye, keratin last year",
"allergy_and_patch_history": "Reaction to home dye 2023, no patch test since",
"maintenance_commitment": "Low"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a 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 touches a client record.
Quotes are opt-in
The provenance block, the client’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 salon software.
Free tier, no app to install, and it fires the moment the consult is complete.
Straight to the front desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The morning shift sees the consult before the client wakes up.
Your own endpoint
Give us an https address, verify the signature, write it into the client profile 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 |
|---|---|---|---|
| 23:14:02 | data.collected | Delivered | 200 OK |
| 23:13:59 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 20:47 | data.updated | Delivered | 200 OK |
| Sun 11:26 | 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. Vagaro, Fresha, Boulevard, Mangomint and GlossGenius 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 client.
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 | Paper form | Booking-platform form | Gnosari |
|---|---|---|---|
| When it gets done | In the waiting room, under time pressure | If the client opens the email | Before the appointment, on their phone |
| The allergy question | Answered "N/A" down the page | A checkbox nobody reads | Asked, with a follow up when the answer matters |
| Chemical history | Whatever fits in the box | A dropdown of five options | Their own words, probed |
| Where the answers land | A drawer, then the bin | A notes field nobody opens | A typed record, posted to your system |
| At the chair | The stylist starts from zero | The stylist starts from zero | The stylist already knows |
| After hours | Nothing happens | A booking, maybe | The consult, done by morning |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Put a conversational agent on the touchpoints you already run as forms: the new client consultation, the colour emergency, the feasibility question, the lapsed client, the fix-it conversation and the reschedule. Each one asks in your voice, types the client’s own words into a structured record, and posts it to your salon software through a webhook, Zapier or Make. Setup is minutes per agent, and you can start with one.