FlowsBook a callSign inCreate free accountSign up
AI employees and automation

An AI agent for car dealerships: rival lots, fleet buyers and test drives

How an AI agent for car dealerships watches rival lots, finds companies that run fleets, and handles test-drive questions and bookings while the showroom is closed.

Part of the guide AI employees

By the xMap team · · 5 min read

An AI agent for car dealerships is worth setting up for three tasks: keeping an eye on rival dealers around your lot, building a list of local companies that run vehicle fleets for your business sales desk, and answering test-drive questions and taking bookings after hours. In xMap Flows each task is an AI employee made of a handful of blocks, and the results reach your sales manager by email or in the Team inbox each morning.

This article is for general managers, fleet and business sales managers, and marketing leads at franchised and independent dealerships. It covers what each task needs, an invented example, common errors, and the order of blocks.

Task one: know what rival dealers are doing

Dealers compete on a short radius. A buyer cross-shops two or three lots within a reasonable drive, so what happens around you matters more than what happens across the region.

Three changes are worth hearing about the same day:

  • A new dealership or used-car lot opens within the distance you choose. The When something changes trigger checks around up to five of your locations on a timetable and runs only when it finds one.
  • A rival's rating drops below a line, such as 4.0. The same trigger watches for that, and it often follows a change in service staff or a bad run of reviews.
  • A rival closes. A closure leaves service customers looking for a new workshop, which is a short window for your service department.

For a regular view of how you compare, the how rival dealers are rated around mine template lists the dealers near each of your stores with their ratings, and my dealerships whose rating moved tells you when your own stores slip.

Task two: find companies that run fleets

Fleet sales are slow to win and steady once won. The hard part is the list: which local businesses run vans, pickups or company cars, and who decides on them.

Start with the kinds of business that almost always have vehicles, such as builders, plumbing and electrical firms, couriers, security companies, rental agencies and facility services. Nearby places lists them around your store from xMap's places database, nearest first. Job postings adds a growth signal: a company advertising for drivers or field technicians is about to need more vehicles.

If your team uses Apollo, the Apollo block can add the fleet or operations manager at each company from your own Apollo account. The companies with fleets, for leasing template puts this together.

Task three: test-drive questions and bookings

Most test-drive interest arrives in the evening, when the showroom is closed. Two blocks cover it.

A Form page gives you a booking form with the fields you choose: name, phone, email, the model, a preferred date and the nearest store as a choice. Each form sent starts the flow once, and an Email block passes the booking to the store's sales desk.

For questions, a Chat page with an AI agent and Reply answers from the files you give it: opening hours, which models you keep for test drives, what a buyer should bring. Keep pricing and stock out of it unless you update those files daily, or the agent will answer from an old list.

One more small help: the test drive weekend template checks the Weather forecast at each showroom before a weekend event, so you know on Thursday whether to plan for rain.

An invented example

Imagine a dealer group with three stores around Monterrey, one selling new cars and two selling used ones. The general manager sets the rival watcher to 3 km around each store, checked daily, for car dealers and used-car lots.

In the first fortnight it reports a used-car lot opening on the highway near the second store, and a rival franchise dealer's rating falling from 4.3 to 3.8. The service manager runs a two-week offer for oil changes aimed at that rival's area.

The fleet list arrives every Monday: around forty businesses within 10 km, of which six posted driver or technician roles in the last month. The business sales manager calls those six first. Over the weekend, the booking form takes nine test-drive requests, each emailed to the right store before it opens.

Errors that waste the effort

  • Watching too many kinds of place. Car washes, tyre shops and parts stores are not rival dealers. Keep the watcher to the kinds that sell cars, and use a separate flow for service rivals if you want one.
  • A fleet list with no growth signal. Two hundred names sorted by distance is a phone book. Rank by who is hiring drivers and who fits your range.
  • Promising a slot the store cannot keep. The booking form should collect a preferred date; the store confirms it. Say so on the form's thank-you message.
  • No owner for each email. If rival alerts, fleet lists and bookings all go to one inbox, they get skimmed. Send each to the person who acts on it.

The blocks, in order

  1. Rival watcher: When something changes (your stores, car dealers and used-car lots, a distance, daily), then xMap LLM to write what changed and why it matters, then Email to the general manager.
  2. Fleet finder: Schedule (weekly), then Area of interest around each store, then Nearby places (trades and service businesses) and Job postings (drivers, technicians), then Apollo if you use it, then xMap LLM to rank and give a reason, then Only new, then Email to the business sales manager.
  3. Test drives: Form page (name, phone, model, date, store), then Email to that store's sales desk. Add a Chat page with an AI agent and Reply for questions.
  4. Test each with Run once, check the email it sends, then Deploy. Bookings and alerts arrive by email; every result is also kept in Results.

To see how these jobs fit together as a team, read the guide to AI employees.

Questions

Can it read my dealer management system?

Only through what you give it: an uploaded table, a file, or a database connection. It does not log into other systems on its own.

Does the rival watcher cover service workshops too?

It can, if you pick those kinds of place. Most dealers keep sales rivals and service rivals in two flows so each alert reaches the right manager.

Who receives a test-drive booking?

Whoever you set in the Email block. With a store field on the form, a Branch block can send each booking to the right store's address.

Will it contact fleet companies for me?

Only if you add the Outreach block, and you can require approval of every message first. Without it, the flow builds the list and your team makes the calls.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.