Multi-Rooftop Dealer Website Platform

A straight look at what a group website stack has to do, what we sell, what we do not, and where the leads actually go missing.

One store with one website has one job: show the inventory, capture the lead, get it to a salesperson quickly. A group with six rooftops has a different problem, and most of it has nothing to do with page design.

The first is identity. Each store has its own name, its own market, often its own franchise requirements, and in many groups its own general manager who considers the site theirs. A platform that forces every rooftop into one identical shell creates a political fight you will lose. A platform that lets every rooftop do whatever it wants creates six different lead capture behaviors, six different form field sets, and a reporting picture nobody can compare.

The second is inventory. Vehicles move between stores. A shopper looking at the Ford point wants the Chevrolet trade that landed yesterday at the store eleven miles away. Whether your platform shows group-wide inventory, and what happens to the lead when it does, is a real decision with real gross attached to it.

The third is the one that actually costs money and is the least discussed. A lead submitted on the wrong store's site, or on a group landing page, has to end up with a specific person at a specific rooftop in minutes rather than in a shared inbox that three people assume somebody else is watching. Almost every group we talk to has a version of this leak and most of them do not know how big it is.

We would rather lose an evaluation early than waste a general manager's afternoon.

LeadLocate is not a dealer website provider. We do not build or host franchise store websites, we are not an OEM compliant website vendor, and we do not carry manufacturer program certification for site templates or co-op compliance. If your Ford point needs a site on an approved provider list to keep its money, you need that vendor, and you should evaluate one on those terms. Our page on OEM compliant dealer websites explains that requirement without pretending we satisfy it, and car dealer website platform covers the category evaluation in general.

What we do build is everything that sits on top of and behind those sites. Landing pages you control without waiting on a website vendor. Individual salesperson sites. A chat widget that drops onto whatever platform each rooftop already runs. Inventory sites generated from a template. Customer-facing deal pages. And underneath all of it, one CRM that receives every lead from every rooftop and routes it by rule rather than by hope.

For a lot of groups that is the honest answer to the question they were actually asking. The websites are fine. What is broken is what happens after the form gets submitted.

Here is the specific tooling, because vague capability language is how software gets bought and then not used.

Lead pages. A landing page builder with per-page URL settings. Your marketing manager can stand up a page for a single campaign, a single model, a single rooftop or a single weekend event, publish it at a URL you choose, and point paid traffic at it. No website vendor ticket, no queue, no change order. For a group running different offers in different markets this alone changes how fast you can move.

Personal salesperson websites. Each salesperson gets their own site. In a group that matters more than it does in a single store, because your best people build personal followings and those followings should still land inside your CRM rather than in a text thread on a private phone. See car salesperson websites for how those work.

A live chat widget. Free, and it installs on the sites you already have. One chat tool across six rooftops means one place to see the conversations rather than six vendor dashboards. More on that at live chat for car dealers.

Inventory sites from a template. My Inventory Link ingests a feed, stores it, and can publish per-salesperson inventory sites from a template, with a public inventory API and key provisioning if you want your own developers consuming the data. Worth saying plainly: a feed is useful but not required for the platform to run.

This is the part that fixes the leak described at the top.

Every lead from every source lands in one system. Lead feeds and custom source feeds take posts from third party providers and your own forms. Global lead distribution applies rules, so a lead from the Sacramento store's landing page goes to the Sacramento rooftop's up rotation and a lead mentioning a specific VIN goes to whoever owns that unit. Distribution lists and global lead settings hold the rules, and distribution history shows you exactly where a lead went and when, which ends the weekly argument about whether a lead was ever received.

Role based permissions keep the stores separate where they should be. A salesperson at one rooftop does not browse another rooftop's customers. A group executive sees across all of them. Reporting has three layers for the same reason: an activity view for the floor, a company view per store, and a management roll up for the group.

The response speed tooling is where a group usually finds its fastest win. SMS and MMS with real threading, RCS with SMS fallback, click to call with a VoIP softphone, call recording with transcription so a manager can read a twelve minute call in half a minute, voicemail drop, and automations that fire a first touch while a human is still walking across the showroom. Our page on CRM for multi-location dealer groups goes deeper on the group configuration.

Groups that grow by acquisition inherit overlapping markets. Two of your stores end up bidding against each other for the same ZIP codes, and the only party who benefits is the ad platform.

The Leads Manager zone editor is a self-service campaign builder where you draw the territory each program covers. You set a zone around a rooftop, and leads generated inside that zone are delivered exclusively to that store rather than resold to three other dealerships. When two of your rooftops are close enough to argue about a market, you settle it once on a map instead of every month in a meeting.

The paid ads module and targeting sit alongside it, so a campaign for one store's market does not spend against another store's. This is a discipline problem as much as a software problem, but software that draws the line makes the discipline stick.

One honest note. We cannot guarantee lead counts or results from any zone, and nothing about a lead is filtered or scored. We ask pre-screening questions at capture and deliver every submitted lead inside the zone. Problems get handled by post-delivery replacement review rather than by a quality promise made in advance. If you want to know what real inbound lead flow looks like before you plan around it, read what to expect from car sales leads.

Brand drift in a group is quiet and expensive. Somebody at one rooftop uses last year's logo, another store's email footer has the wrong phone number, and a third has been sending texts from a number nobody can trace.

AutoMail includes a brand manager and brand asset storage, so the approved logo, colors and assets live in one place rather than in six marketing folders. On the communications side, number management, call forwarding and IVR are configured per rooftop, which means each store's inbound calls route to that store's people while the group still sees one call history.

Email deliverability deserves its own paragraph because groups get this wrong at scale. Email domain authentication is set up per sending domain, and an email validator plus a phone validator let you check contact data before a campaign goes out. Six rooftops sending careless bulk email from a shared domain is how a group ends up in spam folders for a quarter. Validating first is unglamorous and it protects the whole group's sending reputation.

Even though we are not bidding on the site itself, these are the questions that separate vendors, and most groups do not ask them hard enough.

Ask what the per-rooftop price is at year three, not year one, and what happens when you add a store. Ask exactly what happens to a lead between the form submission and your CRM: the mechanism, the format, the timing, and what happens when the delivery fails. Ask to see a failed lead post in their logs. Ask who owns the site content and the URLs if you leave, and whether redirects are maintained, because losing your ranking history during a platform change is a cost nobody quotes.

Ask how inventory syndication works when a unit moves between rooftops. Ask whether page speed is measured on real devices in your market or in a lab. Then ask the question that matters most in a group: can one rooftop change something without breaking the other five, and who has the permission to do it.

Write the answers down. A vendor comfortable being pinned down in writing is usually the one still worth having in year three. Our website RFP template is built to be used with any vendor, including against us.

Every group meeting eventually becomes an argument about which source produced the deal. The reason is almost always that the numbers come from four different systems that count differently.

The fix is boring: measure the few things that are hard to dispute and measure them in one place. Time to first response, by rooftop and by person. Number of follow up touches before the trail goes cold. Appointments set and appointments kept. Those three predict more than any source report, and the CRM logs them natively because the messages and calls happen inside it.

Source detail still matters, and lead feeds carry their source through, so you can compare a landing page against a third party provider on the same yardstick. Just be careful about the claim you make from it. A source that produces cheap appointments in one market may do nothing in another, and a single month is not a sample. Our page on dealer website lead attribution covers the measurement design in more detail, and multi-location SEO for dealer groups covers the organic side of the same question.

Do not convert six rooftops at once. Nobody should, with any vendor.

Pick one store, ideally one with a manager who will tell you the truth rather than the answer you want. Put that rooftop's lead flow into the CRM, build two or three lead pages for its live campaigns, put the chat widget on its existing site, and leave everything else alone for three or four weeks. Measure time to first response, touches per lead and appointments set against the same period last year and against a sibling rooftop running the old way.

That is a real test, and it costs you one store's subscription for a month. CRM Only starts at $199 a month and plans that include exclusive local leads start at $799, month to month with no long term contract, which is what makes a pilot possible in the first place. Full detail is on the pricing page. If a pilot goes badly you have lost a month and learned something real. If it goes well you expand on evidence instead of on a demo.

Do you build dealership websites for each rooftop?

No. We are not a dealer website provider and we are not an OEM compliant website vendor. We build the layer above the sites: lead pages, salesperson sites, a live chat widget, inventory sites from a template, and the CRM that receives and routes every lead.

Can one CRM handle several rooftops without mixing them up?

Yes. Global lead distribution rules send leads to the correct store, distribution history shows where each one went, and role based permissions keep one rooftop's users out of another's records while group management still sees everything.

How do we stop two of our stores competing for the same market?

The Leads Manager zone editor lets you draw the territory each program covers, so leads generated inside a zone go exclusively to that rooftop. It settles the overlap on a map once instead of in a meeting every month.

Do we need an inventory feed or DMS access?

Neither is required to operate, which is why brokers and individual salespeople can run on the platform. If you do have a feed, My Inventory Link can ingest it and advertise your actual vehicles with a public inventory API available.

Will this replace our current website vendor?

In most groups, no. It runs alongside them. The chat widget installs on your existing sites and lead pages live at URLs you control, so you can add capability without a platform migration.

How long does it take to get a rooftop running?

Far less than a website migration, because there is much less to configure. The realistic constraint is your team's adoption rather than the setup, which is why piloting one rooftop first works better than converting the group at once.

We will map a territory around one store, wire its lead flow into the CRM and give you a straight number after thirty days. Month to month, no long term contract.