Routing Enquiries Across a Dealership Group

A dealership group needs a location decision before a diary decision

When a group operates several branches, the nearest free salesperson is not automatically the right person to receive an enquiry. The vehicle may be held elsewhere, the buyer may prefer another location or a specialist team may own the sale. Routing is therefore a decision about stock, responsibility and customer intention before it becomes a search for available time.

Write down the questions that determine branch ownership. A listing-origin enquiry may already identify the stock location. A general website enquiry may need the buyer’s preference. A request about several vehicles may span sites. The assistant should use the information available and ask only what is missing, rather than defaulting every conversation to the group’s main branch.

Separate the preferred branch from the vehicle location

These two facts can be different, and neither should overwrite the other. A buyer may live near the south branch while enquiring about a car at the north branch. Record both the preference and the current stock location. That allows the team to discuss realistic options without accidentally promising that the car is already available near the customer.

If the group allows transfers, define who approves them and when a booking can be confirmed. A request for a transfer is not confirmation that one will happen. The customer-facing message should explain the next step honestly, and the internal task should identify the vehicle and proposed visit. Do not show local test-drive slots until the operational conditions for that visit have been met.

Choose an owner for cross-branch exceptions

A central inbox can make responsibility less visible if every branch assumes somebody else will act. Assign a named team or managed queue for transfer requests, unclear ownership and disputed stock information. Include a clear deadline or priority based on the proposed visit, so an appointment happening tomorrow does not sit beside a low-urgency general question without distinction.

The receiving branch should be able to accept, decline or request clarification through an agreed route. Avoid moving an enquiry repeatedly between inboxes with no acknowledgement. The customer should experience one coordinated conversation, even when colleagues work across sites. Internal handovers should preserve what has already been promised and identify the person responsible for the next external update.

Apply branch-specific booking rules

Opening hours, visit lengths and released capacity may differ between sites. So may the people who can host particular appointments. Configure those differences explicitly instead of assuming that a group-wide calendar can represent every branch. The correct location must be selected before available slots are offered, with the branch name visible in the confirmation.

Include preparation and travel considerations where they affect the commitment. A vehicle transfer may need lead time, and a combined appraisal visit may require someone who is not present every day. If the buyer changes location after booking, recheck those conditions. Moving only the calendar address can leave the appointment looking valid while the required car or person remains somewhere else.

Keep the CRM record coherent across sites

The group should agree how existing customer records are matched and how ownership changes are recorded. A buyer contacting two branches about one car should not automatically receive two independent follow-up sequences. At the same time, ambiguous records should not be merged simply because names look similar. Matching rules need a human exception route.

The current appointment owner, branch and vehicle reference should be easy to see. Preserve earlier conversations where they explain the buyer’s requirements, but do not leave an outdated owner field controlling messages after transfer. When a salesperson takes over directly, automation status should change accordingly. This prevents one branch sending a generic nudge while another is already arranging the visit.

Use confirmations that survive a multi-site journey

An appointment message should name the actual destination and purpose, not merely the group brand. Include the approved address and contact route. Where a branch change has been agreed, issue a revised invitation and stop reminders for the original location. The customer should not have to infer the latest arrangement from a chain of conflicting messages.

For instance, a buyer initially enquires through the north branch but agrees to a confirmed viewing at the central site after a transfer is approved. The final record should show the central site, the named vehicle and the new host. The earlier request remains in history, while every current reminder points to the same confirmed location.

Agree how central and local teams acknowledge work

Routing should include acknowledgement, not just delivery. A central team may have successfully placed a task in a branch queue while nobody at that branch realises that the customer expects a reply. Agree how acceptance is recorded and what happens when a task remains unaccepted. The fallback might return it to a central coordinator, but it must not silently become somebody else’s assumed responsibility.

Keep that internal process separate from the customer-facing promise. If the branch has not accepted a proposed visit, describe the appointment as awaiting confirmation. Once accepted, update the customer and the shared record together. Avoid sending a final confirmation from the central system while a local colleague still sees a tentative request.

When reviewing the group workflow, follow one exception all the way through. Identify who noticed it, who accepted ownership, who spoke with the customer and who closed the task. This exercise often reveals more than a dashboard showing that an enquiry was routed successfully. A useful route ends with an accountable action, rather than a delivered notification.

Clarify what happens when the customer contacts the original branch after a transfer. Staff there should be able to find the current owner and agreement, rather than sending the buyer back through qualification. A shared record is useful only when colleagues know how to interpret its current branch and responsibility fields.

Test the journeys that cross boundaries

Before launch, test a local enquiry, a transfer request, a buyer with an existing group record and a vehicle moved after booking. Ask staff from both branches to inspect their tasks and notifications. Each should know whether they own the customer conversation, vehicle preparation or an approval. A working central dashboard is not enough if the branch team cannot see its obligation.

Review wrong-branch visits, repeated transfers and enquiries without an accepted owner. These outcomes reveal routing problems that raw appointment totals can hide. Galaxy SaaS Agency can organise branch rules, qualification and connected calendar booking around the group’s real responsibilities, helping customers reach the right team without being asked to navigate the organisation themselves.