AI in your toolkit

Where car dealerships use AI today, and the check to run on each before a customer sees it.

By Dr. Canary · Updated

Four ways to bring it in

Who runs the tool, now to later

Buy

The vendor runs the tool.

A product you buy or an AI feature inside a tool you already use.

Check: Get in writing what the vendor secures, what is yours to secure, and what they owe you if it goes wrong.

Build

Your store runs the tool.

Your team builds a tool for one job the store knows well.

Check: Name who owns the code, the logins, and each outside service.

Buy and build together

Your store drafts the reminders. The vendor sends them.

Your vendor sends service reminders. Your team keeps its own tool to draft them in the customer’s preferred language.

Check: Name who owns the draft and what stops the vendor from sending it after a cancellation.

Build now, buy later

Your store drafts first. Then the vendor takes over.

Your team drafts bilingual reminders until a vendor can handle that job. Once its drafts pass the same tests, retire your tool.

Check: At the switch, name who moves the pending reminders and shuts off the old ones, so each customer gets one message.

Weigh the gain against the risk

Drafting a reply for a service advisor carries a different risk from promising a customer a Saturday appointment.

Each risk, what to weigh, and the tests and lists on these pages that cover it
RiskWhat to weighTests and lists
The customer relationshipWrong answers and conflicting follow-ups reach the customer in your store’s name.Sold car Cancelled visit
LiabilityCheck who can promise prices, availability, or appointments, and what the terms cover.Expired payment Trade value
CybersecurityThe model, the code, the servers, the logins, and each vendor’s access all need a lock. Limit what it can reach in the CRM and DMS, and name an owner for each connection.Questions to ask an AI vendor Before the build ships
It shifts as you buildYou answer for what you run. List what your team runs and what each vendor runs.Before the build ships
Your store
Dr. Canary

Before go-live

0 / 3

A checkup

Dr. Canary shops your site the way a customer would and keeps an annotated capture of each step. That is your record of today.

See checkup plans

On launch day

0 / 2

A check on launch day

Dr. Canary shops the site again the day the tool goes live, as a one-time checkup or on your monitoring plan. Set the new screens beside the first.

See an example report

After go-live

0 / 4

How often to look depends on how often the tool acts, how many people it reaches, and what a wrong answer costs.

Monitoring

Dr. Canary shops the site again monthly, every 14 days, or weekly, and sends test leads to read what comes back. An alert reaches you the morning something breaks.

See monitoring plans

a day Dr. Canary shops your sitego-live

The checks, to copy
Before go-live
1. Save the reply or booking a test shopper gets today. Name the person who can verify the matching CRM or scheduler record.
2. Rehearse an ordinary request, then change one fact: the car sells, the slot fills, or the shopper opts out. Agree on the expected result for each.
3. Decide who reads the first live replies, who can pause the tool, and how a customer reaches a person.

On launch day
1. Repeat the same inquiry on the live site from a phone. Match the customer’s message or confirmation to the store record.
2. If they do not match, turn that part off and have a person take the request. Run the test again after the fix.

After go-live
1. Assign someone to read the full follow-up sequence and check handoffs.
2. Compare a sample of customer replies with the inventory, CRM, or scheduler records behind them.
3. Run the tests again after any change to the tool, its data, or what it may do.
4. Before you expand, compare what customers get, the hours staff spend, and the cost with what you recorded before launch.
Dr. Canary giving the OK sign

See what your customers see.

Compare plans

More from the field