Start with the real question.
Tell it what happened and what you need help with. A short question is enough to begin; add details as the conversation develops.
An insurer cuts the bill. Your estimator needs backup. Collision CoPilot puts collision playbooks and cited references inside the AI assistant you already use.
ONE SIMPLE SHOP PLAN
$79 per shop / month
One user included. Each additional user: $15/month.
Starting price protected for 12 continuous months.
Plus applicable tax. Your AI assistant subscription is separate.
AI-generated workshop illustration.
Not a customer shop or the sample vehicle.
Collision repair AI for body shops
Collision CoPilot is an AI add-on for auto body and collision repair shops. It connects the AI assistant you already use (ChatGPT, Claude, or Gemini on a personal Google account) to collision playbooks and research references, so your estimators and managers can ask in plain shop language and get answers with sources they can check. It does not write estimates, and it is not legal advice.
Who it is for: shop owners, estimators, production managers and MSO teams.
More than 8 million words of collision reference, with sources you can check.
Kept current. NHTSA recalls are checked live when you ask, state and federal law is monitored for changes, and the playbooks are revised and expanded regularly. Each source shows how current it is.
Your state not listed? Choose “My state isn’t listed” when you sign up and tell us which one. Every request moves that state up our build list, and we’ll email you the day it’s ready.
HOW IT WORKS
Why add Collision CoPilot?
You already have an AI assistant. Collision CoPilot connects it to collision playbooks and research tools, so when a repair question turns into a billing question your team has the facts to collect, the references to verify, and a draft to review. Your employees make the decisions.
01 / AI for body shops, on real repair questions
You do not need a perfect prompt. Pick one of the five questions below and select “Show full answer” to read a recorded Collision CoPilot response. They are starters; CoPilot handles thousands of questions about estimating, repairs, insurer responses, and running your shop.
START WITH A SHOP QUESTION
STARTING QUESTION
Yes. Before I draft anything, I need the lines that were cut. A response written without them would be a guess.
Send me this:
If you have an OEM procedure, scan reports, measuring printouts or photos that back up the lines, mention them.
How I’ll build the reply:
Anything written for the insurer will start with “Draft only. Nothing has been sent.” Any Washington law I cite is reference information from a selected collection, not legal advice. Confirm it with an attorney before using it in a demand or dispute.
What next?
Checked with Collision CoPilot: playbook_search
Recorded CoPilot response for a sample Washington shop. Full answer preserved. This is a recorded example, not a live request.
STARTING QUESTION
Explain it as math from your own costs, not as a number you picked.
Your rate is what it costs to run the shop plus the profit you need, divided by the hours you can really bill:
(Total annual costs + target profit) ÷ annual billable hours
Build the talking points in this order:
Washington rule. Nothing in chapter 284-30 WAC sets or caps labor rates. But WAC 284-30-390, effective 10/18/2026, says that “If requested by the claimant, the insurer must provide in writing how the labor and material costs and repair processes were determined and cite relevant policy language.” Under (2), if the insurer pays less than your estimate, it must “promptly and fully disclose all of the reasons.” So the insurer has to document why it pays less. The claimant may owe the difference (4)(c).
Reference information from a selected collection, not legal advice. Confirm the official source and talk to a Washington attorney before relying on it in a dispute.
I did not use your actual cost or rate figures. I don’t have them, and I won’t make any up.
What next?
Checked with Collision CoPilot: playbook_search, playbook_read, wa_get_authority
Recorded CoPilot response for a sample Washington shop. Full answer preserved. This is a recorded example, not a live request.
STARTING QUESTION
Fix before it goes out
Likely missing (top 5 of 5)
Check on the car
I did not give any hours. The calibration hours are yours or the sublet’s to quote.
I did not check recalls or Toyota’s repair procedures for this VIN. Pull the OEM position statement on scans and calibrations before you send.
What next?
Sources: ADAS diagnostics playbook, calibration trigger matrix. Checked with Collision CoPilot: playbook_search, deg_search_inquiries, deg_get_inquiry, oem_manual_search
Recorded CoPilot response for a sample Washington shop. Full answer preserved. This is a recorded example, not a live request.
STARTING QUESTION
Keep it moving: parts
Keep it moving: approvals
Keep the floor busy while you wait
This is reference information from a selected collection, not legal advice. Confirm the official source and talk to a licensed attorney in Washington before relying on it in a dispute.
Not checked: DEG precedent on delay disputes, and this specific job’s facts.
Sources: Rental Car Management, Cycle Time Optimizer.
Checked with Collision CoPilot: playbook_search, wa_search_authority
What next?
Recorded CoPilot response for a sample Washington shop. Full answer preserved. This is a recorded example, not a live request.
STARTING QUESTION
Start with the data, before you spend any money. Pull the last 12 months of departures and sort them three ways.
1. By tenure. This tells you what kind of problem you have.
2. By role and by reason. Which techs left, body or paint? Did they leave for better pay, for a better workplace, or for personal reasons? Call two or three of the people who left and ask. Exit-interview themes beat guessing.
3. What it costs you. Run a turnover cost for one tech: recruiting, trainer time pulled off production, the vacancy, 60 to 90 days of reduced output, overtime on the rest of the crew, and comebacks. Your numbers: 7 techs, 2.6 touch hours a day against a 3.5 target, and 12-day cycle against 9. Turnover and a thin crew drag on all of those. Use your own figures, not a generic one.
Then check the pay plan. A stale or unclear plan drives people out. It should be in writing and signed, with real examples for good, average and slow weeks. It should also say who gets paid for comebacks, waiting on parts, and approved supplement time. Review it yearly. Any chargeback or deduction has to stay within federal and Washington wage law. I did not pull the Washington wage rules for this answer, so confirm that with your attorney before you change the plan.
What I could not check: why your people left, and your current pay plan.
What next?
Sources: HR & Workforce playbook, Retention Compensation reference. Checked with Collision CoPilot: playbook_search, playbook_read
Recorded CoPilot response for a sample Washington shop. Full answer preserved. This is a recorded example, not a live request.
Tell it what happened and what you need help with. A short question is enough to begin; add details as the conversation develops.
Your AI assistant can retrieve CoPilot playbooks and reference material. Follow the sources and identify the facts you still need.
Verify original sources against the repair and your shop. Then prepare an explanation, a follow-up question, or an editable draft.
WHAT WE BELIEVE ABOUT AI IN COLLISION REPAIR
AI should help employees do their best work. Collision CoPilot gives your team more support for research, clearer explanations, and better questions, with the source attached so they can check what applies. Their experience and judgment stay at the center.
New to AI? Start with AI BasicsOur purpose is to assist employees, not replace them. Help your team build knowledge, confidence, and capability.
Say when AI helped. Show the sources behind a claim. Be clear about what is confirmed and what still needs checking.
Share only the information needed. Review permissions and drafts. Keep sensitive customer and employee information protected.
Your team verifies the repair information and approves the next step. A confident answer is a starting point for review.
AUTO BODY AI THAT WORKS IN CHATGPT, CLAUDE AND GEMINI
Gemini: personal Google accounts only. Google currently limits custom connectors to personal accounts, so do not upload customer documents there.
Collision CoPilot is an independent BainbridgeAI product. It is not affiliated with or endorsed by Microsoft, OpenAI, Anthropic or Google.
Your own ChatGPT, Claude, or Gemini (personal Google account) with connector access. One assistant per person.
Read-only collision playbooks and research references.
Your source checks. Your review. Your next step.
Workflow illustration. This page does not run a search. Verify original sources, especially OEM repair information. AI provider subscriptions are separate.
02 / Collision CoPilot pricing
Find the source behind the work you need to bill. Start with one user and add your team as you need them.
Collision CoPilot research inside your AI assistant.
Or pay $869 per year and get one month free.
Each additional user: $165 per year. Paid upfront; renews yearly until canceled.
For each estimator you add: $15 a month for CoPilot, on top of the AI subscription they already have. A five-person shop: $139 a month.
One missed line can pay for the month.
Applicable tax is added to monthly and yearly prices.
Our 30-day guarantee. Try it for a month. If it is not for you, email travis@bainbridgeai.ai within 30 days of your first payment and we refund it and cancel your subscription, monthly or yearly. All we ask is your feedback. Guarantee details
Choose additional users at checkout or manage seats in your shop account.
Free for every shop
No subscription needed. The state law guides quote the law word for word, the labor rate calculator works from your own costs, and the directories list associations and schools.
Free state law guides. What the law says in all 32 states, quoted word for word:
Free industry directories. Who to call in your state:
Free labor rate calculator. Work out your break-even and target rate from your own costs:
AI FOR AUTO BODY SHOPS, EXPLAINED
Learn the basics, choose your assistant, and keep your team in control.
What we believe ↑Meet Travis Johnston →For a shop team starting from scratch, we recommend ChatGPT Business as a starting point. It gives your team a business workspace, member access, and business data protections. OpenAI says workspace data is excluded from model training by default. The subscription is separate from Collision CoPilot and requires at least two paid seats. Compare OpenAI’s current plans and check its membership requirements.
Claude Team is another option we recommend. Gemini: personal Google accounts only. Google currently limits custom connectors to personal accounts, so do not upload customer documents there. For work with customer documents, choose ChatGPT Business or Claude Team. Confirm that your chosen workspace supports the CoPilot connection before purchasing.
Never used an AI assistant? Start with our first-time AI playbook. It walks through choosing ChatGPT Business or Claude Team, setting up the shop workspace, reviewing settings, and practicing a harmless conversation before connecting CoPilot.
Yes. We offer optional CoPilot setup and a one-hour Google Meet training session for $249 one time. We can walk your team through connecting CoPilot, writing useful prompts, checking sources, handling shop information responsibly, and practicing everyday research questions. AI provider subscriptions and CoPilot memberships are separate.
For a larger team, multiple locations, or training beyond that session, contact us to discuss the scope and pricing. Email travis@bainbridgeai.ai about setup and employee training.
Yes. Reach out to Travis and the team for setup help, a live demo, or training. We use AI to assist our work, and people remain responsible for the support we provide. Meet the person behind CoPilot.
Artificial intelligence is software built to recognize patterns and help with tasks. The assistants we use here generate responses from patterns learned during training and from information retrieved through tools. You can ask a question in everyday language, request an explanation, or work on a draft. AI can also get things wrong. OpenAI explains these limits.
Start with research questions, explaining unfamiliar terms, organizing the facts you already have, making a documentation checklist, or preparing a draft for a person to review. Collision CoPilot adds collision playbooks and available references to that conversation. The useful outcome is a better-informed employee who can check the support and decide what to do.
Yes. An assistant can help organize documented repair facts, research a specific operation, and draft a supplement explanation for your estimator to review. With CoPilot connected, ask for the relevant estimating reference, inquiry number and date, and any vehicle-specific information still needed.
Use the job’s actual evidence and your shop’s documented time and costs. Review the original source before sending the draft. AI should not invent completed work, a labor allowance, insurer approval, or a promise of payment.
Yes. It can invent a citation, misunderstand a procedure, or apply the wrong rule to your repair. Open the original source and check the passage, date, estimating system, vehicle, and jurisdiction. Ask it to separate verified information from assumptions and to say when support is missing. A link alone is not proof that the answer is correct.
Give it the work you are doing, the estimating system, the relevant vehicle details, your state when it matters, and the result you want. Use a general example before entering customer information.
Use Collision CoPilot to research battery support during a post-repair scan in CCC ONE. Show the relevant DEG inquiry and date, explain what it supports, and list any vehicle-specific OEM information I still need to verify. Keep the answer brief.
This is a starter prompt, not a repair instruction or a promise of a particular result.
When CoPilot is connected and selected, your assistant can retrieve collision playbooks, DEG inquiries, and available law and NHTSA references. Our setup instructions direct it to check CoPilot, cite the returned material, and distinguish the playbook’s method or example from the underlying authority and your shop’s confirmed facts.
That gives your team a source to inspect and a basis to question the answer. A published estimating allowance, an example billing line, and time measured on your job are different things. Source grounding supports verification; it does not make every AI conclusion correct. Add the provided shop instructions and keep CoPilot selected for your research.
No. Collision CoPilot is an independent BainbridgeAI product. It cites public DEG inquiries by inquiry number, with a link to the original on degweb.org, so you can read each one yourself. It is not affiliated with or endorsed by the DEG or the associations that fund it, AASP and SCRS.
The same is true of I-CAR, NHTSA and other government agencies, insurers, estimating systems such as CCC, Mitchell and Solera, paint and equipment makers, and vehicle manufacturers. When an answer names one of them, it is identifying a source or a product, not speaking for it.
A link helps you trace the claim. Verification also means reading the supporting passage and checking whether it supports that conclusion for your job. A real reference can be quoted accurately and still be applied incorrectly.
Ask the assistant to identify the relevant passage, the conditions it depends on, and what remains unconfirmed. This makes review more useful than checking that a citation is present.
Match it to the vehicle, configuration, repair operation, estimating system, and jurisdiction that matter to your question. Check the original document’s date, revision, conditions, and exceptions. The current vehicle-specific OEM procedure must be verified separately; a general playbook is not the complete procedure.
Give the assistant confirmed job facts and ask what could change its conclusion. For claim questions, the actual policy and claim circumstances may matter too. Finding no matching reference is a reason to investigate, not proof that an operation is unnecessary.
Our instructions tell the assistant to acknowledge missing support, ask for relevant job details, and continue checking when applicability is unclear or sources conflict. It should not invent an inquiry number, labor allowance, specification, or legal section to complete an answer.
Ask for the confirmed facts, unresolved questions, and next source to check. Pause the decision and involve the qualified person responsible when the missing information affects repair safety, coverage, or payment. If CoPilot is unavailable, reconnect it before relying on CoPilot-based research.
Use someone with the knowledge and authority to evaluate that specific work. A polished draft or a citation check is not enough for a repair, coverage, or legal conclusion. Your reviewer needs the job facts and original sources and must be able to recognize a mismatch or missing condition.
CoPilot helps put research in front of that person. Your shop sets its review and escalation process, records the basis for consequential decisions, and approves the final action or communication. Bring in an appropriate specialist when the question exceeds the reviewer’s expertise.
Use CoPilot as a research and learning partner. Have employees explain what a source supports, what facts would change the answer, and why the proposed next step fits the job. Review difficult cases with an experienced colleague and practice checking an answer independently.
Measure source accuracy, useful documentation, corrections, and the quality of decisions alongside time saved. Our training can help your team practice that workflow; continued hands-on experience, technical training, and qualified supervision remain part of developing capable employees.
Different tools serve different jobs. Conversational assistants such as ChatGPT, Claude, and Gemini can help with questions and drafts. Collision CoPilot brings available collision research and playbooks into those assistants. GuideCoat focuses on comparing the shop and insurance estimates in a file.
Dedicated industry products also use AI for photo-based damage assessment and estimating; examples include Mitchell Intelligent Estimating and Solera Qapter. Those are different workflows. Choose the task you want to improve, then check the product’s access, integrations, terms, and limits. Your estimating system and verified OEM procedures still have their own roles.
For a shop starting with CoPilot, our first choices are ChatGPT or Claude. Pick the one your team finds easiest to use with our setup guide. Gemini is our third option. Gemini: personal Google accounts only. Google currently limits custom connectors to personal accounts, so do not upload customer documents there. Google also requires you to be 18 or older and in the US, with Keep Activity turned on. This is our practical starting recommendation; it is not a ranking of accuracy or a promise that one will always be faster.
Try the same everyday shop question in your preferred assistant. Judge whether it actually uses CoPilot, shows support you can verify, and gives your staff a useful answer. Compare account privacy controls and connector availability before choosing.
These are our recommended starting settings based on our shop trials:
Keep CoPilot selected and use your shop project or Notebook. Model names and availability can change. More reasoning can use more time and allowance; every answer still needs source checks.
Your AI provider account is separate from your CoPilot shop subscription. For customer documents and confidential shop work, we recommend a shop-managed business workspace. A paid personal plan does not automatically have the same terms and controls. Check connector and customization access before purchasing.
Microsoft 365 Copilot support is coming soon. The CoPilot connection is not available yet. We plan to support Microsoft 365 work accounts through a business connector. We will publish the setup guide after sign-in, research, and access checks pass.
This is the Microsoft option we plan to recommend for shop staff. Copilot Studio is Microsoft’s tool for building agents and integrations; your employees would use Microsoft 365 Copilot. Under Microsoft’s current connector requirements, each person using this connection needs an eligible Microsoft 365 license and a paid Microsoft 365 Copilot add-on. An ordinary Microsoft 365 subscription alone is not enough. Your administrator must enable the connector, and each person needs their own authorized CoPilot access.
For eligible smaller shops, Microsoft’s Copilot Business add-on is the small-business version of this recommendation. Confirm compatibility with us before purchasing for CoPilot use.
The connector lets your assistant call CoPilot’s research tools. Shop instructions give it the context for your business and how you want it to respond. A skill adds reusable guidance for choosing and using the tools. A skill by itself does not connect CoPilot or activate paid access. Follow the guide for your provider, including its instruction and skill steps where available.
The selected model, the question, the number of tool calls, provider traffic, and source retrieval all affect response time. Ask one clear question and request a brief answer first. Use a more detailed mode when you need deeper research. Faster output still needs the same source checks.
Use an account and workflow approved by your shop. Never use a personal AI workspace for customer estimates or confidential shop information. Select the shop’s business workspace before uploading. A login may have access to both a personal and a business workspace, so check which one is active.
Use the information needed for the task, check the sources, review the draft, and have the responsible employee approve the next step. Be honest about AI’s role when you share its work. Business workspaces help the shop manage access; uploaded information is still processed by the provider and any tools used.
Keep passwords, sign-in codes, payment-card and bank-account details, Social Security numbers, and unrelated medical or employee records out of routine AI conversations.
For estimate research, customer addresses, phone numbers, and email addresses usually add no value. Remove them when they are unnecessary. Keep vehicle, repair, and claim details when the authorized task actually needs them. Check who can see the conversation before sharing it or using connected apps.
Yes, when your shop has approved the business workspace and the use of those documents under the provider’s terms. AI can be useful with actual job information. You do not need to remove every identifier from every estimate as a blanket rule.
Share what the task needs. A VIN may matter for exact vehicle identification, and a claim number may be needed in a claim-specific draft. Customer contact details usually are not needed for researching an operation. Remove unnecessary sensitive information and check the settings for storage, sharing, and connected apps. Keep repair decisions and final communications with your qualified team.
Uploading an estimate to your assistant is a separate workflow from connecting CoPilot’s research tools. This website does not accept or analyze estimate uploads.
It depends on the exact service, plan, settings, and how you submit feedback. Free-plan conversations are not automatically public, and paying for a personal plan does not automatically give you business data protections.
ChatGPT Business workspace data is excluded from training by default. Commercial Claude chats are not used for training unless you opt in or explicitly submit materials such as feedback. Eligible Google Workspace licenses provide Gemini Apps enterprise protections; verify that Gemini is a core service under your license. A personal Google account has different terms. Gemini: personal Google accounts only. Google currently limits custom connectors to personal accounts, so do not upload customer documents there.
Business protections still involve provider processing and storage. Review retention, sharing, feedback, and each connected app’s permissions. Read the provider’s guidance directly: OpenAI privacy controls, Claude Team account and data management, and Gemini Apps Privacy Hub.
Connections enable the functions and data access described in their permission screen. Different apps can have different permissions, including reading information or taking actions. Review each connection and enable only the access your shop needs. Collision CoPilot’s research tools are read-only; that does not make your other connected apps read-only. Review CoPilot’s Privacy Policy as well as your assistant provider’s policy.
No. Your qualified team must verify current OEM procedures for the exact repair, the applicable estimating guidance, and any relevant legal requirements. A cited reference does not automatically establish a payable labor time or guarantee insurer approval. CoPilot supports research and drafts; repair decisions, sign-off, and final communications remain with people.
Collision CoPilot is an add-on for collision repair and auto body shops. It connects your AI assistant (ChatGPT or Claude, or Gemini on a personal Google account) to collision playbooks and research references, so your estimators and managers can ask in plain shop language and get answers with sources they can check. It does not write estimates in CCC, Mitchell or Audatex, and it is not legal advice. $79 per shop per month, one user included.
Yes. Collision CoPilot is auto body and collision repair AI built on collision sources: more than 100 collision playbooks, more than 22,000 DEG inquiries, and federal and state law, with sources you can check. It works inside the AI assistant your shop already uses (ChatGPT, Claude, or Gemini on a personal Google account). $79 per shop per month.
Collision repair AI is a broad label. Some tools estimate damage from photos, some answer the phone or book appointments, and some, like Collision CoPilot, are research assistants: they help an estimator or manager find the source behind a repair, billing or insurer question and draft a reply for a person to review. Collision CoPilot does not write estimates or approve repairs. It gives your AI assistant collision playbooks, DEG inquiries, NHTSA recalls and your home state’s insurance and repair law, so each answer shows where it came from.
The founding shop offer closed October 31, 2026, at 11:59 p.m. Pacific time. Shops that started a paid monthly subscription by then keep the $49 monthly base shop rate while their subscription remains continuously active. Canceling and later restarting ends this protection. New shops pay the current published price: $79 per shop per month with one named user included, and $15/month for each additional user. A new subscription’s starting price is protected for 12 continuous months. Shops already subscribed keep the price they signed up at. Applicable tax and your AI provider subscription are separate. The annual plan is a separate option.
Start your shop subscription$79 per shop per month includes one named user. Each additional named user is $15 per month. Or pay yearly: $869 for your shop and $165 for each additional user, paid upfront, with one month free compared with monthly billing. Applicable tax is added to the price. Choose monthly or yearly billing and your users at checkout; update your seats in your shop account. Subscriptions renew until canceled. Monthly usage reports show CoPilot research activity by user and assistant. Coverage is for one location and its selected supported home state, plus shared research tools. AI provider subscriptions are separate. Optional setup and a one-hour Google Meet training session are $249 one time. MSOs can contact us to plan multiple locations.
80 ready prompts for the work collision shops do every week: supplements, short-pays, labor rates, scans and calibrations, total losses, cycle time, technician pay, DRP performance, reviews and more. Each one is a sentence or two in shop language: attach what the card lists, send it, and the answer ends with a short menu of finished things to pick from, like a letter to the adjuster, a customer text, a Google Sheet or a one-page PDF. It’s in your account the moment you subscribe, alongside a starting prompt for every playbook and a builder for your own. The library keeps growing as shops bring us new problems, and every new prompt is included in your plan. Have one you’d like built? Tell us.
Yes. We stand behind Collision CoPilot with a 30-day guarantee. Try it for a month. If it does not earn its keep in your shop, email travis@bainbridgeai.ai within 30 days of your first payment and we will refund it and cancel your subscription: the first month on a monthly plan, or the full year on a yearly plan. All we ask is your feedback on what did not work. After that you can cancel any time and keep access through the period you paid for; partial periods are not refunded.
Each person needs their own CoPilot membership and connects with their own CoPilot email. Being in the owner’s ChatGPT or Claude workspace does not automatically grant a CoPilot seat. Follow your workspace administrator’s connection rules too.
No. Each person picks one AI assistant for their CoPilot connection. If you want to change providers, email collision-copilot@bainbridgeai.ai so we can help you switch. Every employee needs their own CoPilot membership and email. Do not share a seat or sign-in.
Use the email attached to your CoPilot purchase or accepted shop invitation. It can differ from your AI provider’s login email. A sign-in code proves control of that email; paid research also requires active shop membership and coverage. Signing in with another email does not by itself create paid access.
CoPilot brings together collision playbooks, more than 22,000 DEG inquiries, NHTSA recalls and complaints, federal shop law (OSHA, EPA, and wage and hour rules), paint and equipment references, and state law for your shop’s home state.
Retrieve and verify current original OEM information for the exact vehicle; do not assume a general playbook supplies the complete repair procedure.
Supported home states: Washington, Montana, Colorado, Texas, California, Florida, New York, Pennsylvania, Ohio, Illinois, Michigan, Arizona, Georgia, North Carolina, Tennessee, Virginia, New Jersey, Massachusetts, Indiana, Minnesota, Maryland, Missouri, Wisconsin, Alabama, Louisiana, Iowa, Connecticut, Kansas, West Virginia, New Hampshire, Utah and Nevada. Each shop plan covers one location and its home state. Tennessee’s collection holds its rules, enacted acts and agency guidance; the codified Tennessee Code is published only through LexisNexis and is not included, and the CoPilot says so whenever a Code section is asked for. Your state not listed? Choose “My state isn’t listed” when you sign up and tell us which one. Every request moves that state up our build list, and we’ll email you the day it’s ready.
They serve different workflows. Collision CoPilot adds research tools and playbooks to your supported assistant. GuideCoat works with supported repair files and estimate comparisons. This landing page illustrates the research workflow; it does not analyze an uploaded estimate.
Yes. Shop owners get a monthly usage report in their CoPilot account. See research lookups, active users and days, activity by named user, and which assistants your team connects. Reports also suggest a useful next step when your team has used CoPilot less often.
These counts cover CoPilot research lookups started. One question can involve several lookups; the report does not measure all AI conversations, successful answers, time saved, or money recovered. Conversation text and tool arguments are not included. Older connections may appear as “Assistant unknown”; reconnect to record the assistant for future lookups.
Open your shop usage report. Optional email recaps can be requested from your shop usage page.
Open the setup guide for ChatGPT, Claude, or Gemini (personal Google accounts only). If you would like help connecting and learning the workflow, email us to arrange setup and training or book a live demo.
Plans, features, and policies can change; follow the linked official guidance for your account.

Travis JohnstonLinkedIn profile Founder · GuideCoat & Collision CoPilotMore than 30 years in collision repair, including owning a family collision business.
MEET THE PERSON BEHIND THE TOOLS
I grew up in this industry. Over the past few decades I’ve watched collision repair change, and a lot of those changes took decisions about how a shop runs out of the owner’s hands. Shops feel pressure every day to go against what they know is the right repair, and the safe repair, so a job fits someone else’s number.
That’s why I started studying AI: to give the keys back to the people who own these shops. Most shops want to do the right thing, but there’s so much noise now that the right thing isn’t always clear. Collision CoPilot puts the answers back in your hands: the DEG inquiry, the rule, the method, with the source attached, so you can make the call and stand behind it.
I’m here for the shops. Especially the independent that wants to hand the business to the next generation and keep it in the family. That’s how it worked for me, and I want it to keep working for you.
Questions, concerns, or just want to talk shop? Email me at travis@bainbridgeai.ai or book a time to talk.
Travis Johnston, Founder, BainbridgeAI
Coursework completed at OpenAI Academy and Claude Academy, from AI foundations to agents, retrieval and evaluation.
When you reach out, you’re talking with people. Contact Travis for help choosing a workflow, getting connected, or training your staff.
A SPECIALIST IN YOUR CORNER
One shop, one user, $79 a month plus tax. Your AI assistant subscription is separate.
Start my shop for $79/month Book a live demo