WhatsApp for automotive
The full playbook for dealerships — test drives, service reminders, delivery updates and feedback.
Read moreCustomer story · Automotive
Service bays sat under-booked while the call centre missed four in ten inbound calls. Regal Motors moved reminders, bookings and advisor conversations to WhatsApp — and the bays filled.
Executive summary
Regal Motors, a multi-city two-wheeler and car dealership group, replaced reminder calls and SMS blasts with WhatsApp booking flows connected to its dealer management system. Within a quarter, monthly service bookings through the channel grew to five times the phone-era baseline — much of it outside call-centre hours.
5×
increase in monthly service bookings via WhatsApp
68%
of started booking flows completed
41%
of bookings made outside call-centre hours
4 min
median advisor response time in the shared inbox
The challenge
Regal Motors runs two-wheeler and car dealerships across Pune and four neighbouring cities, and service is where the margin lives. The trouble was reach: the call centre that booked those services missed roughly 40% of inbound calls at peak, and the service-due reminders that went out by SMS drew single-digit responses. Customers were not declining a service — they simply never had a usable way to say yes.
The cost compounded quietly. Bays sat under-booked while local garages picked up the lapsed services, advisors spent their first hour each morning working through a dial list, and a customer who wanted to book at 9 pm — after the call centre closed — had nowhere to go.
Before the rollout
Implementation
Week 0
Business verification completed and the group's service number migrated to the WhatsApp Business API, so reminders came from a number customers already recognised.
Week 1
Service-due reminder templates approved, the dealer management system connected over the REST API, and the one-tap slot-picker flow built and tested against live DMS data.
Week 2
Service advisors across all five cities onboarded to the shared inbox, with routing by location and an escalation path for warranty and complaint conversations.
Week 3+
Service-due broadcasts switched on for opted-in customers at 30, 14 and 3 days out, with read rates, flow completion and bookings tracked daily in the dashboard.
Architecture
Dealer management system
Service-due dates & slot writeback
WhatsApp Business API
Verified business number
Broadcast campaigns
Service-due reminders
Chatbots & automation
Slot-picker booking flow
Shared team inbox
Advisors in 5 cities
Integrations touched: DMS via REST API · Booking webhooks · Advisor rosters
Automation
In the conversation
The core flow: a service-due reminder lands, the customer books in three taps, and the slot writes back to the dealer management system.
Your Alto VXi (MH12 AB 4321) is due for its 20,000 km service. Slots are open at Regal Motors Baner this week.
Book a slot
Pick a time that works — a service advisor will confirm pickup options.
Tue 9:30 am
Confirmed — Tuesday, 9:30 am at Regal Motors Baner. Reply PICKUP if you would like us to collect the car from your home.
Before vs after
Monthly service bookings from reminders
Reminder response rate
Median advisor response time
Lower is better
ROI analysis
The arithmetic in this scenario is straightforward: reminders and booking flows run on utility messages, and the recovered work is service revenue on bays that were already staffed and lit.
Monthly cost
Plan + messages
One Growth plan covering all locations, plus Meta's message charges billed per delivered message — your live rate card in the dashboard shows exact prices.
Recovered value
~960 extra services / month
In this scenario the channel adds roughly 960 services a month over the phone-era baseline. At even a modest average invoice, that is a large multiple of the messaging spend.
Payback framing
First week of the month
Framed conservatively, the first few dozen recovered bookings each month cover the channel in this scenario — everything after is margin on bays that used to sit idle.
We stopped measuring the service desk by calls made and started measuring it by bays filled. Reminders, confirmations and reschedules run themselves now — advisors only handle the conversations that need a human.
FAQ
About three weeks from kickoff to live campaigns in this scenario: number migration in week 0, template approval and the booking flow in week 1, advisor onboarding in week 2, and service-due broadcasts from week 3.
Platform plans are listed on /pricing. Meta's message charges are billed per delivered message; your live rate card in the dashboard shows exact prices. The 7-day free trial (Lite plan, no card required) lets you try the basics, but the chatbot booking flow and DMS webhooks shown here are on the Growth plan and above — the full reminder flow runs on a paid Growth plan.
One integration: the dealer management system pushes service-due dates and receives bookings back over the REST API and webhooks. Most groups complete it with one developer in a few days, with InfiQ's onboarding team pairing on the mapping.
Yes. The shared inbox shows the full conversation history, so an advisor can pick up the phone for anything complex — the point is that routine bookings no longer require it.
About this story
This case study is a composite scenario prepared by the InfiQ team to illustrate a typical automotive deployment on the platform. Metrics represent modeled outcomes for this scenario rather than the reported results of a single named customer.
Keep reading
We'll map a Regal-style rollout to your dealership group — service reminders, booking flows and an advisor inbox included. 7-day free trial, no card required.