Vehicle health checks generate the most valuable conversation a service department has with a customer all year, yet most dealerships still fight it out over the phone: three missed calls, a voicemail, and a customer who authorises the brake pads two days later once the courtesy car has already gone out. Setting this workflow up on WhatsApp instead removes most of that friction, because the results, photos, and pricing can sit in one thread that the customer approves with a single tap.
This guide walks UK dealership service managers through building that flow end to end: from template creation and Meta approval through to routing approved jobs back to your service advisors.
Before any template goes near a customer, your inbox needs to reflect how your service department actually works. Users are created with a first name, last name, email address, and are then assigned to specific inboxes and teams, so a technician or advisor only sees the conversations relevant to them. Permissions control who can access features like bulk broadcasting, template editing, and automation administration, with team leaders and admins given elevated access compared to regular users.
For a service department, this typically means creating a dedicated team for service and vehicle health checks, separate from sales or parts, so approvals land with the right advisor rather than getting lost in a general inbox. Once a user account is created, that team member receives an email with login credentials and instructions for downloading the app, so they can respond to customers from their desk or the workshop floor.
Getting your team structure right first means that once approvals start coming in via WhatsApp, they route to the person who can actually act on them, not to whoever happens to check the shared inbox next.
Every message you send to a customer outside an active 24-hour conversation window needs to go through an approved template, because WhatsApp does not allow businesses to freely initiate or restart conversations without one. This is the mechanism your vehicle health check approval flow depends on, so getting the template right is the most important step in the whole setup.
a. Create the template in your platform, not directly with Meta. Templates must be created in the platform's templates tab rather than submitted to Meta directly.
b. Follow Meta's formatting rules precisely. Template names must be lowercase with underscores instead of spaces, no emojis are allowed in buttons, and there can be no double spaces or multiple line breaks in the message body. Variable fields, such as the customer's name or vehicle registration, cannot start or end the message.
c. Choose the right category. Set the category to "utility" rather than "marketing," since utility templates are transactional or service-related messages and cost less per message than marketing templates. Meta sometimes reassigns a template to "marketing" regardless, but utility remains the correct starting category for a vehicle health check notification.
d. Draft content around a simple structure. An effective template follows a pattern used across other service-notification templates: a brief greeting, a note on what's happened (in this case, the health check being completed), and an invitation to view the results and respond.
e. Add personalisation variables. Include variables such as {{first name}} so the platform prompts you to fill in the customer's name, and consider adding a variable for the vehicle registration or make/model so each message feels specific rather than generic.
f. Set attachments if you plan to send photos. If your health check includes photos of worn brake pads, tyres, or other components, create the template with attachments enabled from the outset, since a template built without attachment support cannot have media added later.
g. Add quick-reply buttons for approval. Quick reply buttons let the customer respond with a simple tap rather than typing a full reply, and they measurably increase response rates compared with open-text prompts. For a vehicle health check, this typically means buttons such as "Approve work," "Call me," or "Not right now."
h. Include a "stop" quick-reply option. Adding a quick-reply button labelled "stop" allows the customer to unsubscribe cleanly, which avoids the message being reported or blocked to Meta.
Once your template is built, it moves into a review process that sits outside your direct control, so plan your rollout timeline around it rather than against it.
After submission, the template shows as "pending" in your platform while Meta reviews it. Approval time varies: it can take anywhere from minutes up to 48 hours, and the platform notifies you by email once it's approved or if there's an issue. Completing Meta Business Suite verification, which involves uploading company documents and confirming ownership of the WhatsApp number, speeds up this process and also enables your dealership's business name to display on outgoing messages.
One practical note worth building into your rollout plan: if you edit a template and it sits in a long pending state, delete it and create a new one rather than continuing to edit, since edits can cause delays that a fresh submission avoids.
With an approved template in place, the next task is making sure your service advisors can send it without friction as part of their daily routine. From the platform, an advisor sends a template by opening the customer's number, selecting the appropriate branch or team inbox, and choosing the approved template from a dropdown before filling in the variable fields and sending. For dealerships running a CRM or dealer management system alongside their WhatsApp platform, the Chrome extension integration allows a phone number to be highlighted directly within the CRM record and sent via WhatsApp without leaving that screen.
If your health check process generates a fair amount of ad hoc, less formal follow-up (a quick "just checking you saw the last message" type of note), the platform's "natural chat" feature lets staff type a free-text message that is automatically wrapped into compliant template format behind the scenes, which reduces the amount of template-selection admin for busy advisors.
A customer tapping "Approve work" is only useful if that response reaches someone who can act on it immediately, so this step is about closing the loop.
Keyword and phrase-based automation can assign a conversation to a specific team the moment a customer replies, in the same way a keyword like "kitchens" can route a chat to a Kitchens team with a tailored automated reply. Applied to a service department, an exact-phrase match on a quick-reply response can route the approval straight to the parts or workshop team, or archive the conversation automatically once the required response has been logged, keeping the shared inbox clear for live enquiries. Conversations can be assigned to a team rather than a named individual, which matters for service departments running shift patterns, since it ensures whichever advisor is on duty picks up the approval rather than it waiting for one specific person to return.
Vehicle health check messages don't stop being sent at 5:30pm, so your customers need to know what happens when a query comes in outside your working hours. Global business hours can be set with branch-level overrides, and a default away message can inform customers when a branch is closed while giving instructions for leaving a message. An "always send" setting ensures the out-of-hours message goes out every time a customer sends a message outside business hours, with a cooldown period (for example, one hour) built in to prevent the customer being sent the same automated reply repeatedly.
Once the flow is live, the final step is reviewing how it performs and adjusting accordingly, rather than treating the initial setup as finished.
Analytics can be filtered by template name and by the user sending messages, letting a service manager see which vehicle health check template variants get the fastest approval responses. Some dealerships already use template-sending volume as part of staff performance reviews, with one example benchmark of around 200 templates sent per month per agent. Reviewing this data over a set period, such as the last 85 days, gives a clear enough sample to spot which wording or button combinations convert best and to retire templates that underperform.
Template stuck in "pending" for longer than 48 hours. Rather than continuing to edit the existing template, delete it and submit a fresh one, since this is a faster path to approval than editing a template already under review.
Approval taking longer than expected across the board. Confirm your Meta Business Suite account is fully verified, including uploaded company documents and confirmed ownership of the WhatsApp number, since verification is what speeds up approval and unlocks full platform capability.
Customer replies not reaching the right advisor. Check that your keyword or phrase-based routing rules use exact-phrase matching correctly and that conversations are assigned to teams rather than defaulting to whoever last replied, particularly across shift changes.
Approval responses cluttering the shared inbox. Set up routing so that conversations are automatically archived once a quick-reply response has been logged and there's nothing further to action, keeping the inbox focused on live enquiries.
A WhatsApp-based vehicle health check approval flow turns a process that traditionally depends on catching a customer mid-phone-call into one they can act on whenever suits them, with photos, pricing, and a one-tap approval sitting in a single thread. Building it properly means getting your team structure right first, constructing a compliant utility template with quick-reply buttons, submitting it for Meta approval with a verified Business Suite account, and then routing approvals straight to the advisor or team who can act on them. Once live, the same analytics that show template performance across other service department workflows apply here too, giving you a clear basis for refining wording and timing as adoption grows.
