WhatsApp Business API for auto repair workshops: setup, rules and real costs

The app is fine until these start happening to an auto repair workshop:

• Service reminder calls go to voicemail. Your service team calls for upcoming service due. Most go to voicemail, no callback. WhatsApp messages get near-universal read.
• Customers call for service status updates constantly. "Is my car ready?" — you get this 20 times a day. WhatsApp job card updates end these calls completely.
• Previous service customers don't return. Customer had great service. 6 months later, needs next service. Didn't remember you. Went to the nearest garage.

The app cannot send on a trigger, share one number across staff, or read your records. The API can. And customers keep asking the same things: customers ask for a service slot, an estimate for a repair, whether their car is ready, and whether pickup and drop is available.

• A verified Meta Business account in the auto repair workshop's legal name, backed by a registration, GST or utility document.
• A number not active on the WhatsApp app — your current one works once it is removed from the app.
• A display name matching the business, and a website or public page Meta can check.
• Opt-in from every customer you message first. Vehicle check-in is the moment — customers want updates about their car anyway.

Most workshops already use WhatsApp — on the service advisor's own phone. It works until the advisor is on leave, changes jobs, or has forty chats open and cannot tell which "is it done?" belongs to which car. The API moves those chats onto the workshop's number and into a shared inbox, where any advisor can pick up any customer and see the job card beside the conversation. The customer keeps messaging the same number; the workshop stops depending on one person's phone.

1. Connect the number through Meta's embedded signup inside Reputoo, and submit business verification — you can start sending within Meta's starting limit while it is reviewed.
2. Get your first templates approved for the 3 routine messages listed below; anything outside a customer's 24-hour reply window must be a template.
3. Wire the triggers to your records. What to connect: A workshop job-card system; each job card has the customer, the vehicle and the status updates need.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A workshop doing 20 jobs a day with five updates each sends about 3,000 utility messages a month — roughly ₹345 in Meta fees on the July 1, 2026 India rate card, before GST. The service-due reminders are the ones to budget carefully: at ₹0.8631 each, reminding 1,000 past customers costs ₹863.

Meta charges per delivered template message, and the price depends on the category. For auto repair workshops, the day-to-day messages sort like this:

• Service due reminder sent automatically — utility
• Job card updates during service — utility
• Upsell approvals via WhatsApp mid-service — marketing
• Next service reminder set — utility

Timing matters as much as category. Estimate approvals as soon as the inspection is done, status updates during the job, and service-due reminders by date or mileage.

A service reply answers a customer who wrote first; from 1 October 2026 Meta charges those at the utility rate. Utility messages (confirmations, reminders, status updates) cost a fraction of marketing messages, so keep them strictly transactional — a discount line inside a reminder makes Meta classify the whole template as marketing.

Meta list rates, July 1, 2026. India in INR, plus 18% GST.

The most expensive hour in a workshop is the one where a car sits on the lift while an advisor tries to reach the owner about a worn brake pad. WhatsApp fixes this in a way SMS never could, because the estimate can carry evidence.

1. The technician photographs the part — the pad thickness, the leaking seal, the cracked belt — or takes a ten-second video of the noise.
2. The advisor sends the estimate as a template: the part, the labour, the total, the photo, and two buttons: [Approve] [Call me first].
3. An approval is recorded against the job card with the time, so there is no later dispute about what was agreed.
4. "Call me first" drops the job into the advisor's call list — the owner who wants to talk gets a call, everyone else just taps.

Keep the approval message to one decision. An estimate listing six optional items with one button each confuses more than it saves; group the must-do work and the can-wait work, and ask about each group once.

Many workshops collect and return cars. The messages that make this smooth are small: the driver's name and number when the pickup is scheduled, a photo of the car and odometer at collection, and the same at return. They protect the workshop as much as the customer — a scratch "that wasn't there before" is settled by the timestamped photo in the chat, not by an argument at the gate.

A WhatsApp thread with the estimate, the approval, the photos of the old part and the final bill is a better warranty record than a paper file. When a customer comes back in four months saying the new part failed, the advisor can scroll to the day it was fitted and see exactly what was approved and charged. Make it a rule that every approved estimate and every final bill goes through the chat, even for customers who also get a printed copy.

Meta rates every number on how customers react. For auto repair workshops, the risk is usually messaging the whole contact list about something only some of them asked for. Send reminders only to people with a booking or order, promotions only to people who opted in to them, and never use a bulk-sender tool on the ordinary app — that is the route to a banned number. The full list of what Meta checks is in our WhatsApp Business API guide.

The ready message is the natural place for the invoice and a payment link, so the customer can pay before arriving and the handover takes two minutes instead of fifteen. Itemise the bill the same way as the approved estimate, so the customer can match them line by line; any difference should already have its own approval in the chat. For fleet and corporate customers who pay on account, send the bill without a link and let accounts handle it.

1. Week 1: move the workshop's number to the API, get the booking, check-in, estimate and ready templates approved.
2. Week 2: advisors send every estimate by WhatsApp with photos, and log approvals from the buttons.
3. Week 3: add progress and ready messages with the payment link; count how many status calls stop.
4. Week 4: start service-due reminders to past customers who opted in, from the oldest due dates first.

• Every job card has the customer's number and the vehicle registration.
• Technicians know how to attach photos to an estimate.
• The estimate template has approve and call-me buttons, and approvals are logged.
• Utility templates carry no offers; service offers go in separate marketing templates.
• One advisor owns the inbox during working hours; calls requested by customers are returned the same hour.

Groups with more than one workshop usually run one WhatsApp number per branch, each with its own display name, under one business account. Customers keep the branch they use; head office sees all conversations. If you use a single number instead, route by the customer's chosen branch at booking, and make sure the job card carries the branch so the right advisors see the chat.

Meta reviews every template, and workshops tend to trip on the same things. Keep variables for the parts that change — the customer's name, the registration number, the job card, the amount — and write the rest in plain words. Avoid all-capital warnings, avoid placeholder text that could read as anything ("{{1}}" alone as a whole message), and never put a discount into the check-in or ready template. A clear template is approved in minutes; a vague one gets rejected and holds up the rollout.