You automate auto repair shop intake by putting a conversational agent in front of the service booking. It asks for the vehicle, the reason for the visit and a preferred time one question at a time, types the answers into a structured service record, and posts that record to your shop system before anyone calls back.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone hearing a noise they can’t place, due for service, or holding a warning light they don’t recognise, usually on a phone, usually not during opening hours.
What it costs today
A phone line that goes to voicemail during the hours staff spend on the counter and the bay, or a web form that asks about the vehicle but not the symptom, so the advisor re-asks everything at check-in.
What it has to produce
A typed service record: the vehicle, the reason for the visit in the customer’s own words, the mileage, and anything urgent enough to need a call today rather than a booking next week.
154
missed service calls a month, at the average shop location
STELLA Automotive AI
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the service record |
| phone | phone | Yes | How the shop calls back |
| vehicle_year_make_model | text | Yes | Which vehicle this is about |
| mileage | number | — | Context for the technician, never a diagnosis |
| service_or_symptom | text | Yes | The reason for the visit, in their own words |
| symptom_description | text | — | The symptom, in their own words, before anyone books |
| warranty_status | text | — | Feeds the fit check, never a coverage promise |
| still_driving_it | boolean | — | Flags anything urgent, never a verdict on the car |
| declined_service_item | text | — | What was noted last time, never re-quoted |
| customer_decision | text | — | Approve or decline, recorded plainly, never talked into it |
And what it will not do
Collected data
212 collected27 this week5 need attention
Export CSVJordan Blake
Captured 1h ago · Service Booking · joina.chat
Captured data 6 of 7 fields
From the conversation
“It’s been making this sound for about a week, gets louder every time I brake , and I wanted to get it looked at before it gets worse.”
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": "Service booking",
"record_id": 1234,
"attributes": {
"full_name": "Jordan Blake",
"phone": "+1 512 555 0134",
"vehicle_year_make_model": "2021 Toyota RAV4",
"mileage": "43000",
"service_or_symptom": "Grinding noise when braking, started about a week ago",
"preferred_date": "2026-08-14"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a customer 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 repair order.
Quotes are opt-in
The provenance block, the customer’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 shop system.
Free tier, no app to install, and it fires the moment the service record is complete.
Straight to the counter
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The service advisor sees the intake before the car is even on the lift.
Your own endpoint
Give us an https address, verify the signature, open the repair order 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. Shopmonkey, Tekion, Mitchell 1 and CDK Global 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 repair order.
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 | Voicemail and a callback | PDF or web intake form | Gnosari |
|---|---|---|---|
| After hours | Rings out | Downloaded, never returned | Answered, typed, delivered |
| What you get back | A name, if they left one | Whatever fitted in the boxes | The symptom in their own words |
| Half-told story | Staff call back to ask | Submitted half empty | It asks the follow-up |
| The price question | Whoever answered guesses | Not applicable | Never guessed, and stated at the start |
| Gets into your shop system | Re-typed by hand | CSV, or an integration you pay for | Signed webhook, the moment it is complete |
| The price and safety 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.
Gnosari runs the intake conversation your shop would otherwise take by phone: the vehicle, the symptom in the customer's own words, when they need it back and how to reach them. It asks one question at a time on your website or through a link, then posts a typed service record to your shop system. The advisor opens a complete request instead of a voicemail.