All plays › Local trades and home services

Local trades and home servicesGrok Bot

Give your techs a diagnostic bot that runs the scan tool and hands them a plan

Picked and checked by Olga Pearson, host of The Practical AI Show · Published

Result

self-reported

The shop’s Diag bot pulls a full vehicle scan in about 15 to 30 seconds, and the owner says Grok Bot took at least 7 hours a week off his plate in his first two weeks.

Brandon Miller co-owns Miller Auto, a family tow and repair shop in Omro, WI, with his son Austin. They run more than a dozen Grok Bots, each with one job. The Diag bot drives the scan tablet itself. It pulls codes and live data, digs through repair info and gives the techs a diagnostic plan to follow. It isn’t allowed to clear codes or reprogram anything. Another bot keeps a shop wiki of policies, procedures and what each bot does.

Who did it

Brandon Miller (@milleratr)Miller Auto, Omro, WI (sales, service and towing)Brandon Miller on X · Oct 19, 2026

Try it now

  1. Start with one bot and one job: when a tech asks, it pulls codes and live data and writes up what it found.
  2. Write its hard limits down first: it never clears codes, reprograms modules or orders parts. Those calls stay with the tech.
  3. Have it turn each scan into a short diagnostic plan: what to check first, what readings would confirm it, and which parts not to throw at it yet.
  4. Ask a second bot to keep a shop wiki of every policy, procedure and bot job, so what the bots learn isn’t lost.
Copy-paste prompt
You are the diagnostic assistant for [shop name]. When a tech gives you a vehicle (year, make, model, VIN) and a complaint, pull the codes and live data from [scan tool], look up [repair info source], and write a one-page plan: the likely causes in order, what to test first and the reading that would confirm each one, and what NOT to replace yet. You may read data only. Never clear codes, reprogram, or order parts. The tech makes every repair decision.

Make it run every week

A play works once. Turn it into a routine in three small steps:

  1. Run it once and check the result yourself.
  2. Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
  3. Keep a log. One line per run: what was checked, anything flagged, what you did.

See how owners turn plays into systems →

What to watch out for

Self-reported. The 7-hours figure is from his separate Oct 18 reply (https://x.com/milleratr/status/2111960158112776261), and only two weeks in. Hooking a bot up to a scan tool depends on your hardware, so keep it read-only. Build it with Page: a services page with honest pricing that the bot can link in estimates.

Did it work?

PageMotor keeps this site free.