# The missed call becomes a typed repair order by morning.

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.

## The process this page is about

Not "AI for auto shops". One process, the one that decides whether a driver with a noise they can’t place calls your shop or the next one on the search results: the service intake, the message that arrives before anyone has spoken to a person.

- **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.
- **missed service calls a month, at the average shop location**: 154 (source: STELLA Automotive AI)

## What it asks, and what it never asks

You name the fields your intake form already has. It does the asking, in whatever order the story comes out, and it keeps asking until the required ones are filled.

| Field | Type | Required | Why |
|---|---|---|---|
| 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 | no | Context for the technician, never a diagnosis |
| service_or_symptom | text | yes | The reason for the visit, in their own words |
| symptom_description | text | no | The symptom, in their own words, before anyone books |
| warranty_status | text | no | Feeds the fit check, never a coverage promise |
| still_driving_it | boolean | no | Flags anything urgent, never a verdict on the car |
| declined_service_item | text | no | What was noted last time, never re-quoted |
| customer_decision | text | no | Approve or decline, recorded plainly, never talked into it |

### And what it will not do

- It never diagnoses a fault, and never says whether a noise, light or symptom is serious, minor or nothing to worry about.
- It never quotes, estimates or confirms a repair price, for any job, ever.
- It never says whether a vehicle is, or is not, safe to drive. Anything that sounds urgent gets a call-now, not an answer.
- It never confirms or denies warranty coverage. The advisor checks the file and calls with the answer.
- It never re-quotes a price from a past visit, or pressures anyone to approve work they are unsure about.
- It never invents a field. If they did not say it, the record says "Not captured" instead of a guess.

## Try the run yourself

Six situations a service counter actually handles, each running its own agent with its own fields. Pick one and answer it the way a real customer would, out of order and mid-worry, and watch it ask the follow-up instead of accepting the blank.

- [I need to book my car in](https://joina.chat/l/tb-booking): Chat widget. The service booking, right where a visitor is reading your services page.
- [What’s that noise?](https://joina.chat/l/tb-noise): Conversation page. Describe a symptom and watch it stop and say call now if it sounds unsafe.
- [Do you even work on my car](https://joina.chat/l/tb-fit): Conversation page. Vehicle and warranty fit, qualified before anyone books.
- [It’s been a while since that repair](https://joina.chat/l/tb-declined): Conversation page. No pressure, just checking back on something declined.
- [How’s it running since the visit](https://joina.chat/l/tb-after): Conversation page. Catches a real concern before the survey lands.
- [Found something else while it’s in](https://joina.chat/l/tb-approve): Conversation page. A record against a car already on the lift, not a new lead.

## Frequently asked questions

**What does Gnosari do for an auto repair shop?**

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.

**How do I stop losing repair requests that come in after the shop closes?**

Create a free Gnosari account and tell it which fields your repair order already has: vehicle, mileage, symptom, drop-off window, contact. Put the link on your website and in the voicemail greeting. Gnosari runs the conversation at any hour, follows up when an answer is incomplete, and posts the record to Shopmonkey or Tekion through a webhook, Zapier or Make. The advisor calls back with the job already written up.

**Will Gnosari diagnose the fault or tell a customer the car is safe to drive?**

No. Gnosari is instructed never to diagnose a fault, never to name a likely cause, and never to say whether a vehicle is safe to drive. When a symptom sounds urgent, such as brakes, steering, smoke or a fluid leak, it stops collecting fields and tells the customer to call the shop right now. Every value is stored with the sentence it came from, so the advisor sees exactly what was said.

**Can Gnosari quote a repair price or confirm warranty coverage?**

Neither. Gnosari never quotes, estimates or confirms a price, and never repeats a figure a past advisor gave. It records what the customer believes about manufacturer or extended warranty coverage, marked as their statement, and says the advisor confirms both price and coverage once the vehicle is in the bay. Pricing and warranty stay shop decisions, made by a person with the car in front of them.

**Does Gnosari work with Shopmonkey or Tekion?**

Yes, through a webhook. The moment a service record is complete, Gnosari posts a signed JSON payload to the address you give it, and Zapier or Make routes it into Shopmonkey, Tekion or the shop management system you already run. There is no Gnosari app to install on either side, and the record is already in your Gnosari inbox before delivery starts, so a down endpoint never loses a request.

## Five minutes from now your missed calls could be typed repair orders.

Build the agent, put it on your service pages, and watch the first repair record arrive. Free to start, no card.

Full page: https://gnosari.com/for/automotive