Here is the honest version. In the first 30 days on an AI service writer, your front counter does not change all at once. Week one, your advisor learns to start a repair order with a VIN and one sentence instead of a blank screen, and it feels like cheating. Week two, they stop typing and start talking to the RO, and that is usually the day the job gets lighter. Week three, inspections and texted approvals replace the voicemail tag that eats the afternoon. Week four, the schedule starts filling from the website, the booking link and review requests without anyone remembering to do it. Nothing about the shop changes. The amount of keyboard work does.
What actually happens on day one of AI service writer onboarding?
Setup is 24 to 48 hours. A Pista expert migrates your customers, vehicles and history for free, so you are not starting from an empty database. Your phone number ports in. Your website goes live. That part happens behind the scenes.
What your advisor sees on day one is a counter screen that looks like a counter screen. Phone on the left, ticket in the middle, vehicle history right there. Nothing to dig for.
The weird part on day one is trust. Advisors who have spent ten years building ROs line by line do not hand that over because a trainer said so. So do not ask them to. Ask them to write one ticket the new way and keep writing the rest however they want.
Week one: the VIN plus a sentence habit
This is the whole first week. Scan or paste the VIN. Type what the customer said in plain words. "Grinding from the front when braking, worse cold." That is it.
The AI service writer builds the ticket from there: year, make, model, engine, the likely line items, MOTOR labor times attached, parts pulled through PartsTech with live pricing and availability. The advisor reads it, fixes what is wrong, and sends it.
What feels weird: the first few tickets come back faster than you can proofread them. Advisors slow down to check everything, which makes week one feel no faster than the old way. That is normal and it is correct. Check everything.
What stops being done by hand in week one: looking up labor times in a separate tab, typing customer and vehicle info that the VIN already knows, and retyping the same brake job description you have typed a thousand times.
Week one goal: every advisor writes at least five tickets from a VIN and a sentence. Not all of them. Five.
Week two: talking to the RO instead of typing
Week two is where it clicks for most counters. Instead of clicking into a line to edit it, the advisor talks to the ticket. "Add a cabin air filter." "Change the brake job to pads and rotors front only." "What did we do on this car last spring?" "Write the customer a text explaining why we recommend the fluid service."
That last one matters more than it sounds. The hardest part of a service advisor's day is not knowing the repair. It is explaining the repair to someone who is already annoyed, twelve times before lunch. The RO writes that explanation in plain language and the advisor edits a word or two and sends it from the messaging thread.
The phone fits in the same screen. Calls land inside the ticket, so the advisor sees the customer, the car and the open RO before they say hello. When nobody can get to the phone, the AI receptionist answers, takes the reason for the call and books the appointment.
What feels weird: talking out loud at the counter. Some advisors type their instructions instead, which works fine. The habit is conversational, not verbal.
Week two goal: nobody on the counter opens a line item to edit it by hand unless they want to.
Week three: inspections and texted approvals
Now you push the work out to the bay. Techs run digital inspections on the tablet or the phone. Photos, short video of the wobbling wheel, notes. Green, yellow, red.
The advisor turns the yellows and reds into an estimate and texts it. The customer sees the photo of their own leaking strut, taps approve on the lines they want, and the tech keeps moving. Decline a line and it is saved for the next visit instead of lost.
Then text to pay closes the loop. The customer pays from the parking lot or from work. No counter line at 5:15.
What feels weird: the quiet. Advisors who built their identity on the approval phone call feel strangely idle for about three days. Then they notice they are closing more lines and arguing less, because a photo of a torn boot does not need a sales pitch.
What stops being done by hand in week three: paper inspection sheets, calling four customers who are all in meetings, and rekeying approved lines back into the ticket.
Week four: the schedule starts filling itself
Week four is the part nobody plans for because it does not happen at the counter. It happens before the customer ever calls.
Your shop website has been live for three weeks with online booking. Every closed ticket has been sending a Google review request by text. The retention side has been reminding people whose declined work is still sitting there. And the connected car app with your shop's name on it has been giving your regulars a health score, instant estimates and a booking button on their phone.
Appointments start showing up that no one answered the phone for. That is the month four through twelve story, but week four is when a shop owner first sees it on the board.
What does the front counter stop doing by hand?
| Task | Before | After 30 days |
|---|---|---|
| Starting a repair order | Type customer, vehicle, concern, lines | VIN plus one sentence |
| Labor times | Separate guide, separate tab | MOTOR times on the line already |
| Parts | Call or browse suppliers | Priced and ordered in the ticket |
| Approvals | Phone tag | Texted estimate with photos |
| Missed calls | Voicemail nobody checks | AI receptionist books it |
| Review requests | Asking when you remember | Automatic at ticket close |
What should I tell my service advisors before we start?
Three things. First, the AI writes the draft, you own the ticket. Nothing goes to a customer that an advisor did not read. Second, you will be slower for about a week and that is the deal. Third, if something is wrong on a ticket, say so in the ticket and it gets fixed, you are not filing a support request.
Service advisor training here is not a class. It is five tickets, then twenty, then it is just how you write. Shops running Pista have written 2,600+ repair orders and manage 3,200+ customers this way, and shops on the platform are running 68.9% gross margin.
What does it cost to try for 30 days?
Nothing for the first 30 days. Pit Crew is $149 per shop per month, Full Track is $299 and fits most shops, Podium is $499. Unlimited users on every plan, because charging per advisor is a tax on hiring. Migration is free. Full pricing is here.
What to do this week
- Book a setup call and get your data migrated. Setup runs 24 to 48 hours, so start the clock now, not after the holidays. Book a call.
- Pick one advisor as the first user. Not the whole counter. One person writing five tickets from a VIN and a sentence.
- Turn on the phone and the AI receptionist on day one so no call goes to voicemail while you are learning.
- Get one tech running digital inspections with photos by the end of week two, so week three has something to text.
- At day 30, compare the schedule, the review count and the number of approvals that came back by text. If it did not move, you have paid nothing. Questions first? Read the FAQ.