CRM for Multi-Location Dealer Groups

Group standards where they matter, local control where it counts, and one customer record across every rooftop you run.

A group does not become a group on the day the paperwork closes. It becomes a group about six weeks later, when a customer calls the wrong store and nobody can tell whether somebody is already working with them.

The failures arrive in a predictable order. Duplicate customer records come first, because the same shopper submits on two sites and lands in two inboxes. Then phone confusion, because the number on a marketing piece points at a location that is not holding the car. Then reporting, because two stores count an appointment differently and the comparison stops meaning anything. Then, quietly, the shadow systems: a spreadsheet at one store, a group text thread at another, and a manager keeping his own list because he does not trust either.

None of that is a software problem at the start. It becomes one when the software cannot express the difference between a group standard and a local exception. Most automotive CRMs treat an additional location as a separate tenant, which means duplicated configuration and no shared view, or as another pool of users, which means no separation at all. Multi location work needs both at the same time: a standard that travels and a boundary that holds.

If you buy lead generation by territory and your rooftops sit twelve miles apart, the map matters more than the software. Two stores in the same group covering the same ZIP codes will pay twice to reach one household, then compete for the appointment, and the shopper will read the second call as pressure rather than service.

LeadLocate sells lead programs by zone around a store. Every submitted lead inside that zone is delivered to you exclusively rather than resold to three dealerships, and nothing is filtered or scored before it reaches you. For a group, the useful consequence is that zones become a planning tool. You draw them deliberately: which rooftop owns which corridor, where the boundary sits, and what happens to a lead that lands on the line. The Leads Manager zone editor lets you see and adjust that map yourself instead of filing a request and waiting a week.

The harder decision is not technical. It is deciding in advance which location takes a shopper who is closer to store A but asked about a unit parked at store B. Groups that write that rule down before launch stop having the argument. Groups that do not have it every Monday for a year. Our page on automotive CRM for dealer groups covers the distribution mechanics that enforce whatever you decide.

Phones are where multi location groups leak the most and measure the least. Every rooftop has a main line, a service line, a used car manager's cell that ended up on a billboard in 2021, and a tracking number from a vendor nobody remembers signing with.

AutoMail is the voice side of the platform and it exists to make that mess deliberate. It covers IVR with call routing, number management, call forwarding and full call history, so an inbound call at 7:40 in the evening goes somewhere defined rather than ringing into an empty showroom at whichever store happens to be printed on the ad. Calls are logged, and call recording with transcription means a group manager can read what happened on a call in half a minute instead of listening to eleven minutes of it.

Two habits are worth adopting on day one. Give each location its own numbers for each channel you spend money on, so attribution is a fact rather than an argument between a marketing director and a general manager. And walk the after hours call path yourself, at each rooftop, before you assume it works. Most groups that do this discover at least one number that rings nowhere, and one that still rings a person who left in 2023.

The instinct after an acquisition is to make the new location do everything the way the flagship does. That is right about half the time and expensive the other half.

Some things should be identical everywhere and are worth being rigid about: how fast a lead gets a first response, what a follow up cadence looks like before a lead is treated as cold, how an appointment is defined, how opt outs are honored, and the way money is presented to a customer. Some things should stay local: staffing shape, hours, which channels the market actually responds to, and how the floor gets covered on a Saturday in a town with one traffic light.

The platform supports that split with group level defaults layered over per store settings. Global lead distribution rules and distribution lists set the standard, and individual locations deviate where they have a documented reason. Automations, follow up processes and drip campaigns are built once and reused, so a store that joins in March runs the cadence the group agreed on in January instead of inventing its own. Task automation puts work in front of the right person with the context attached rather than as a note somebody has to interpret.

Decide which category each rule belongs in before you configure anything. The configuration is the easy part, and it is not where groups get stuck.

Ranking rooftops on units sold is the most common group report and one of the least useful. A metro point with four times the traffic wins every month, which tells you nothing about whether it is being run well or whether the small store is quietly outworking it.

The comparisons worth building are ratio based and process based. Time to first response by location. How many follow up touches a lead receives before the store stops trying. The share of leads that ever get a second attempt, which in most stores is lower than the general manager believes. Contact rate by channel, so you can see that one location is carrying text while another is still trying to win on voicemail. Appointment show rate, which exposes whether appointments are being set or invented.

Three reporting layers cover this: activity reporting for what individual people did, company reporting for a location's performance, and management reporting for the roll up. The numbers are real rather than self reported, because the texts, calls and emails happen inside the platform instead of on personal handsets. That is the entire reason to insist on adoption, because a report built from a system nobody uses is fiction with a chart on it. There is more on group level views on the executive dashboard page.

Groups move people. A BDC that covers three stores, a finance manager who floats, a used car director responsible for every rooftop, a salesperson who transfers in June. Most CRMs handle this badly, which is why so many groups end up creating the same human being three times with three passwords and three sets of half correct permissions.

Role based user management with per user access control is the mechanism that fixes it. A used car director sees used inventory and used deals at every location without seeing new car gross. A BDC manager sees their team plus the stores that team covers. An outside agency gets reporting access with no customer detail attached at all. Login activity is recorded, which nobody thinks about until the week a salesperson leaves for a competitor down the road and somebody asks what they could reach and when.

The floor side matters just as much. A mobile workspace means a salesperson standing in the lot at a different store can text, call, scan a VIN and pull a payment from a phone rather than walking back to a desk that is not theirs. Personal salesperson websites travel with the person rather than the rooftop, which removes one of the honest reasons good people keep a private list.

The week a new location goes live is the week its habits get set, so it is worth having a sequence that does not depend on anyone being heroic.

1. Numbers and routing first. Provision the location's numbers, build the IVR path, and test the after hours route before a single lead arrives.
2. Territory second. Draw the zone, confirm it does not eat a neighboring rooftop's map, and agree the boundary rule in writing.
3. Users and roles third. Create people once with the correct role rather than cloning a permissive account and promising to tighten it later. Later never comes.
4. Cadences fourth. Copy the group's follow up processes, drips and message templates instead of letting the new store write its own from memory.
5. Data last. Import the customer records you actually want, with blacklist and opt out status intact, and do not import a list whose consent history you cannot describe out loud.

Then run overlap. Keep the previous system live for a few weeks rather than cutting cold, because a group that loses a fortnight of lead flow at a new store also loses that store's first impression of the platform, and first impressions decide adoption. The CRM migration checklist works through the data questions in order and is written to be used with any vendor, not just this one.

Ask a group operator where the customer data lives and you get an org chart answer. Ask a salesperson and you get the truth: some of it is in the CRM, some is in a phone, some is on a notepad, and the good material is in somebody's head.

Shadow systems are a symptom rather than a discipline failure. People keep private lists when the official system is slower than the alternative, when they are not confident a lead will stay theirs, or when they have watched a transfer erase a year of relationships. Retiring the shadows means removing those three reasons, not sending a memo about compliance.

In practice that means making the platform faster than a personal phone for the twenty small things a salesperson does every hour, which is what a real mobile workspace and one tap texting and calling are for. It means making ownership visible so nobody wonders whether a lead will be reassigned quietly overnight. And it means giving people something they would lose by going around it, like call transcription that writes their notes for them and templates that turn a good message into a two second job.

The group payoff is not tidiness. It is that a customer contacted by two of your locations shows up as one person, on one record, with one opt out status, which keeps you out of a compliance problem as well as an embarrassing conversation.

Pricing is per location and month to month. CRM Only starts at $199 per store per month for a rooftop that already has its own lead sources. Programs that include exclusive local leads start at $799 for inbound buyer leads, $999 for Marketplace Acquisitions on the seller side, and $1,599 for the Buyers and Sellers Hybrid Plan. Lead Data Only is $599, and Skip A Month is $199 for a location pausing between seasons. Current figures live on the pricing page.

Most groups begin one of two ways. Either CRM Only across two or three rooftops to prove the workflow and the reporting, then lead programs added at the locations that are short on volume. Or lead generation at a single store in a market where the group is underperforming, then expansion once that store's response times and appointment numbers move. Turning on six locations and every module on day one is the approach that stalls, and the reason has nothing to do with the software.

No DMS integration and no inventory feed is required to run any of this, which is why a newly acquired rooftop can be live while its back office is still mid transition. We cannot guarantee unit counts, close rates or results at any location, because the consumer controls most of the outcome and your process controls the rest. What we can do is show the platform running on your own map with your own rooftops on it, and price it so that continuing is a monthly decision.

How do you stop two of our own stores from chasing the same shopper?

Territory zones are drawn per rooftop and adjusted in the Leads Manager zone editor, so coverage does not overlap by accident. The rule for a lead that falls on a boundary should be agreed in writing before launch, and lead distribution rules then enforce it automatically.

Can each location keep its own settings while the group sets standards?

Yes. Group level defaults cover distribution, cadences, permissions and reporting, and an individual location can deviate where it has a reason to. Reporting still rolls up across every store regardless of local configuration.

Do stores share customer records?

That is configurable. Most groups share customer history so a repeat buyer is recognized anywhere in the organization, while restricting deal and gross data by role. Opt out status should always be shared, so a customer who unsubscribes at one location is not contacted from another.

How are phone numbers handled across locations?

AutoMail provides number management, IVR with routing, call forwarding and call history per location, plus recording with transcription. Giving each rooftop its own numbers per marketing channel is what makes attribution a fact rather than a debate.

How long does it take to bring a newly acquired rooftop online?

Far less than an enterprise implementation, because there is less to configure and no DMS integration is required. The realistic constraint is adoption, which is why the sequence of numbers, territory, roles, cadences and then data matters more than the calendar.

Is pricing per group or per store?

Per store, month to month, with no long term contract. CRM Only starts at $199 per location per month and lead programs are priced by the territory around each rooftop. See the pricing page for current figures.

We will draw territories around each of your locations, show the group reporting and the routing rules, and give you a straight number per store. Month to month, no long term contract.