Set Rooftop Boundaries Before a Dealer Group Buys the Same Shopper Twice

The Same Shopper Can See Two Stores

A group with nearby rooftops may market the same brand, model, service, or trade message from several locations. Without a coordination rule, each store can pay to reach the same household while sending different promises about availability, price, or appointment timing. The customer experiences the confusion as a brand problem. The group experiences it as duplicated spend and a disagreement over which store should respond.

Begin with a map of what should be shared and what should remain local. Brand guidelines, approved legal language, measurement conventions, and creative templates may be shared. Inventory, hours, service capacity, phone routing, local sponsorships, and manager ownership may need rooftop-level control. Write the boundary down before a campaign launches. A shared audience rule is not a substitute for accurate local destinations.

Use a Priority Rule, Not a Turf Argument

When rooftops overlap, define a customer-first priority rule. Proximity may be appropriate for a routine service need; vehicle availability may matter more for a specific VIN; an existing relationship may influence where a returning customer expects help. The rule can vary by journey, but it should be understandable to the BDC and marketing teams. Avoid a rule that simply gives the largest store every lead. It may be easy to administer while being wrong for the customer.

Record exceptions for group-wide campaigns, used inventory, commercial customers, and service customers who request a particular location. Put the exception in the campaign brief and CRM routing guidance. If the group cannot determine a priority from the available information, route the request to a human queue with enough context to ask the customer rather than silently sending it to the nearest generic destination.

Coordinate the Message and the Destination

A group-level ad can still land on a page that explains the relevant rooftops, their hours, and the inventory or service choice available at each. A rooftop-specific ad should not send customers to a group page that hides the location they selected. Review phone numbers, forms, map links, and appointment availability by location. The campaign owner should be able to answer which team receives a response before budget is approved.

Hold a short overlap review during active campaigns. Compare reach, response, destination, and customer complaints by rooftop, but do not treat every difference as a failure. One store may have a different inventory mix or service capacity. The purpose is to find accidental competition, contradictory claims, and missing handoffs. Keep changes in a shared decision log so a local fix does not surprise another store.

A group can also designate a neutral escalation owner for a customer who has no clear rooftop priority. That person should have enough inventory and appointment visibility to offer choices, then record the customer’s selection. The rule protects the shopper from being passed between stores while giving each rooftop a fair explanation of why a request was assigned elsewhere. Review those exceptions for recurring boundary problems.

Rooftop Coordination Checklist

• Document shared standards and local decisions before campaign launch.
• Define customer-first priority rules by journey and list meaningful exceptions.
• Verify destination, phone, hours, inventory, and appointment context for each rooftop.
• Give the BDC routing team the same rules and context as marketing.
• Review overlap, complaints, and contradictory messages without erasing local differences.

FAQ: Should Every Group Campaign Use One Budget?

Not automatically. A shared budget can help a group respond to changing inventory or capacity, but it can also hide which rooftop receives demand and who is accountable for the outcome. Use a shared budget only with an explicit allocation rule, local reporting, and a way to protect a store’s necessary demand. Budget structure should follow the customer and operational rule, not replace it.

Rooftop coordination is successful when customers get a coherent answer without losing the local expertise that makes a dealership useful. The boundary document is the small piece of governance that makes that possible.