There are two kinds of WhatsApp messages a shop can send. The first makes customers grateful: “Your phone is ready for pickup” — or, at a workshop, “your car is done, collect it any time after four.” The second makes customers block the shop’s number: the same promo, to everyone, three times a week.
Both often get called “WA blasts” — yet they’re worlds apart. This article is about building the first kind and avoiding the second.
One difference: born from data, or from a contact list
A useful message always has a specific reason for a specific recipient: their invoice coming due, their repair finished, their warranty about to expire. Reasons like that can only be known from transaction records — never from a contact list.
That’s why good reminders aren’t a “mass message” feature; they’re a side effect of correct bookkeeping. A shop with tidy receivables can chase exactly the right person, for the right amount, at the right time. A shop whose receivables live in memory can only choose between not chasing at all, or chasing everyone and looking chaotic.
There’s a second difference nobody mentions, and it decides whether your reminders actually run: how the message leaves. A “reminder” that is really just a ready-made link still needs a human to open WhatsApp Web, find the contact, and press send — one at a time, and it stops the day that human is busy, off, or simply forgets. Automan sends from the server through a gateway: you set it up once, and the reminder still goes out on a day when nobody in the shop opens WhatsApp at all.
The reminders that matter most for a repair shop
Four reminder families earn their keep fastest:
1. Due receivables. Repairs picked up with a deposit, credit sales — every receivable has a date. A reminder that leaves on the morning of the due date collects politely and consistently, before the debt ages into “too awkward to chase now.” The routine around it lives in the morning receivables tip.
2. The shop’s own obligations. The reverse direction matters just as much: supplier bills coming due. A shop that pays on time earns bargaining power — and a reminder makes “on time” independent of anyone’s memory.
3. Repair status updates. Unit received, cost needs approval, unit ready for pickup — sent automatically as the status changes. The rare reminder the recipient is actually waiting for.
4. Post-pickup follow-up. A reminder that goes out days or weeks after a job closes — asking how the repair held up, and opening the door to the next one. For a workshop this is the sensible way to earn a return visit, because it starts from a real transaction: this vehicle, worked on that date.
Three things you decide on every reminder
This is where “automatic WhatsApp” stops being a phrase and starts having contents. Each reminder is built from three choices:
- What wakes it up. Not a date in a calendar — a transaction: a warranty about to expire, a customer invoice falling due, a job stuck too long at the same status, a supplier bill coming due, a customer’s birthday, stock running low, dead, or negative.
- When it leaves. A number of days before the date, a number of days after it, an exact date, every day, every month, or every year.
- Who receives it. Seven options: the customer on the transaction, the supplier, the technician who did the work, the staff member involved, the one who recorded it, a specific named person, or a number you type in yourself.
That combination is what makes one message feel personal while running unattended: the recipient is picked by the system out of a transaction, not picked by you out of a contact list. And because the recipient is born from a transaction, misfires barely happen — no transaction, no message.
Worth being straight about the limit. Automan does not work out when the next scheduled service falls due — there is no next-service date and no interval the app calculates. The odometer is recorded when a vehicle comes in, but it is not what wakes the message up. What you get is the three choices above — and for a workshop, the two that earn their keep are the follow-up a few days after collection and the nudge before the repair warranty runs out.
Anti-spam rules that protect your number
Because WhatsApp isn’t an official broadcast channel, how you use it determines your number’s lifespan. The safe principles:
- Relevant per recipient — the message names something that belongs to them (invoice, unit, date), not a generic announcement.
- An exit exists — whoever asks to stop is honored. One spam report costs more than a hundred delivered messages.
- Humane hours — working mornings and afternoons, never midnight; for mass sends, follow the timing tips.
- Reasonable, gradual volume — a number that suddenly fires hundreds of messages behaves like a spammer in WhatsApp’s eyes; don’t be that number.
- Cold contacts are different — people who’ve never transacted aren’t reminder targets; if contacted at all, it’s under far tighter restrictions.
One honest note: gateways like this aren’t WhatsApp’s official business API — nobody can promise “ban-proof.” What can be done is the safe usage pattern above, which is why safe-usage guidance is part of the feature itself, not a footnote.
Where to start
The realistic order: tidy the transaction records first (dated receivables, disciplined repair statuses), connect the WhatsApp Gateway, then switch on reminders starting with the safest and most-awaited kind — repair status updates. Receivable reminders follow once the team is comfortable.
The best message a shop can send is one that makes the recipient feel looked after, not shot at. And messages like that always begin with correct records — see how Automan assembles them in WhatsApp for repair shops.