Deciding to standardise WhatsApp communication across a dealer group is the easy part. Most groups that get this wrong don’t fail because the idea was bad. They fail because they rolled it out everywhere at once, before anyone had proven what “good” actually looked like at a single site, and spent the next six months fixing inconsistencies that a slower, staged rollout would have avoided entirely.

Stage 1: choosing the pilot site

Not every site makes a good pilot. The right one has three things: a service manager who’s actually motivated to make it work rather than one who’s been assigned it, enough volume that results show up within weeks rather than months, and a customer base broadly representative of the rest of the group, so what works there is likely to work elsewhere too. A struggling site chosen because “it needs the help most” tends to make a poor pilot, since any improvement gets attributed to the general attention the site is receiving rather than to the WhatsApp workflow specifically.

Stage 2: what “proven” actually means before expanding

“It seems to be going well” isn’t proof. Before expanding beyond the pilot, a group should be able to point to specific, comparable numbers: response rate before and after, inbound call volume to the service desk before and after, and survey completion rate before and after. Worthing Motors’ results, a 55% increase in engagement and a 30% increase in service bookings, are the kind of specific, comparable figures worth aiming for as evidence before rolling out further, not a vague sense of improved customer sentiment.

Stage 3: turning what worked into a repeatable process

This is where most rollouts either become genuinely scalable or quietly fall apart. What worked at the pilot site needs to become a documented process, specifically: which message types go out and when, who’s responsible for reviewing and approving vehicle health check videos before they’re sent, and how DMS data flows into each message. What shouldn’t get locked down is the exact wording of every message, since a site with a slightly different customer base may reasonably want to adjust tone, as long as the underlying workflow and timing stay consistent.

The most common mistake at this stage is documenting too little, leaving each new site to reinvent details the pilot site already worked out, which is exactly the inconsistency a group-wide rollout is meant to prevent.

Stage 4: expansion and reporting

Roll out to new sites in batches rather than all at once, so any site-specific issue (a different DMS setup, a team less comfortable with the workflow) gets caught and fixed before it’s repeated across ten more sites. At this stage, group-level reporting becomes essential rather than optional: leadership needs to see response rates, engagement and booking outcomes across every site in one place, not five separate spreadsheets in five different formats. This is also the point where DMS integration consistency matters most. A group running Keyloop across multiple sites can extend the same reminders and approvals to each new site without rebuilding the connection from scratch; see how the Keyloop integration works for the detail.

Where rollouts stall

Three patterns account for most of the rollouts that stall part way through: expanding before Stage 2 is genuinely proven, under-documenting Stage 3 so each new site starts from scratch, and treating reporting as an afterthought added once problems have already surfaced rather than built in from the first expansion. None of these are technology problems. They’re sequencing problems, which is why this playbook is a sequence rather than a checklist.

For the case for standardisation in the first place, and the commercial reasons it matters at group and OEM-network level, see how multi-site car dealer groups standardise communication across sites. For the underlying workflow this playbook is rolling out, see WhatsApp for automotive aftersales.

Getting started

Book a demo to talk through a rollout sequence for your specific group, including which site makes sense as a starting point.