WhatsApp for automotive service and sales
A purpose-built Automotive module — not a folder of templates. Vehicle ownership records, service history, packaged pricing, estimates approved in chat, and reminders that bring cars back on schedule.
Why automotive ends up on WhatsApp
A workshop loses money in two places: slots that go unfilled because nobody chased last quarter's customers, and jobs that stall because an estimate is sitting unapproved on somebody's phone. Both are communication problems wearing an operations costume.
The usual fix is a service advisor with a personal handset and a good memory. It works at ten cars a day and breaks at thirty — and when that advisor leaves, the vehicle history, the quotes and the relationships leave with them.
Zapelite's Automotive module puts the vehicle at the centre instead of the conversation. Each customer has vehicle records with service history, parts and past visits attached. Estimates are built from packages and pricing rules, sent for approval in the thread, and the approval is recorded. Service-due reminders fire on date rules, so retention stops depending on whether anyone remembered.
A service visit, end to end
This is the flow most workshops start with. Nothing here is bespoke development — it is the module plus the Bot Builder.
- 1
Customer messages "service"
A keyword trigger opens a flow. Existing customers are recognised by phone number, and their vehicles are pulled from their record — so the first question is "which car" with a list, not "please provide your details".
- 2
Vehicle and slot captured in one flow
The flow collects vehicle, complaint and preferred slot in a single interaction rather than five template round-trips, and books against workshop capacity synced from Google Calendar. The booking exists in the system before the customer puts the phone down.
- 3
Estimate priced and sent for approval
Once the vehicle is inspected, the advisor builds an estimate from configured packages and pricing rules and sends it into the same thread. The customer approves in chat, and the approval is stored against the job — so there is no argument later about what was agreed.
- 4
Status updates, then CSAT
Job status updates go out as utility templates as the work progresses, which cuts the "is it ready" calls that consume a service desk. After collection, a one-tap CSAT request lands, and low scores route to a manager as a ticket instead of a review.
- 5
Service-due reminder, months later
A date rule on the vehicle record fires the next service reminder automatically. This is the step that pays for the platform: retention that runs whether or not anyone has time to chase it.
What teams actually run
Everything below ships in the product. See every feature or the integrations catalogue.
Service booking
Customers book slots through flows synced to workshop capacity and calendars.
Vehicle & service history
Per-customer vehicle records with every past job, part and visit on file.
Estimates & approvals
Priced estimates built from packages and pricing rules, approved by the customer in chat.
Service-due reminders
Date-based reminders that bring vehicles back without a single phone call.
Automotive lead scoring
Leads scored on vehicle type and service history, with hot ones routed to sales.
Post-service CSAT
Ratings after every job, with a dashboard for service volume and revenue.
What changes
- Estimate approvals stop being verbal. There is a record of what was quoted, what was approved and when.
- The "is my car ready" call disappears into automated status updates, freeing the service desk for work that earns.
- Retention becomes a system rather than an intention — reminders fire on the vehicle record, not on somebody's memory.
- When a service advisor leaves, the vehicle history and customer relationships stay with the workshop.
Build this first
Start with service-due reminders, not with the booking flow. Reminders run against vehicle records you already have, need no change to how the workshop operates, and produce bookings in the first month — which makes the rest of the rollout easy to justify internally.
Add the booking flow second, once reminders are filling slots, and estimates third. Estimates touch pricing and advisor behaviour, so they are worth doing carefully rather than first. Most workshops reach the full flow within a few weeks, one piece at a time.
Automotive, answered.
Yes. A flow collects vehicle, complaint and preferred slot in one interaction and books against workshop capacity synced from Google Calendar. Returning customers are recognised by phone number, so their vehicles are pulled from their record rather than re-entered.
Yes. Estimates are built from configured packages and pricing rules, sent into the thread, and approved by the customer in chat. The approval is recorded against the job, which is the part that matters when a bill is disputed.
Reminders fire on date rules attached to the vehicle record — last service date, mileage interval or a schedule you define. They go out as utility templates, which is both the correct category and the cheaper one.
Yes. Dealerships typically use the lead-scoring and CRM side more heavily — routing sales enquiries by vehicle interest — while workshops lean on booking, estimates and reminders. Both run on the same module.
It stays. Conversations, vehicle records and job history belong to the workspace, not the agent, and can be reassigned. This is the main reason workshops move off personal handsets.
Other industries
Real Estate
Lead qualification, buyer/renter segmentation, viewing scheduling and deals opened straight from chat.
Logistics
Tracking, delivery scheduling, COD confirmation and failed-delivery recovery, driven from your own systems.
Retail & E-commerce
Native Shopify and WooCommerce sync, cart recovery, pay-by-link and post-purchase review flows.
See it running on your workflow
Book a demo and bring one real scenario from your operation. We will build it in the product rather than describe it on a slide.