Features

Not just status messages. Business follow-up needs reminders too.

“Automated WhatsApp” has been claimed so widely that the phrase no longer tells you anything, so here is the specific version. Automan runs its own WhatsApp server: messages are dispatched from the server through a gateway, not by opening WhatsApp Web and pressing send, and not by handing you a click-to-chat link that still waits on your thumb. And because each message is set off by a real transaction, the recipient is read off that transaction — the customer on that job, that supplier, that technician — rather than pulled from a contact list and blasted. We’re also honest from the start: this gateway is non-official, so Automan ships with real controls and safe-usage guidance, not a “ban-proof” promise.

That distinction sounds like a technicality until you compare two Tuesdays. In the template version of your week, the software drafts a nice message and waits for you; on a busy afternoon nobody opens it, and the customer calls anyway. In the server version, the message left while the technician was still wiping their hands.

Two separate engines: WA Gateway & Reminder System

These are often mistaken for one, but they do two different jobs:

  • WA Gateway — the sending engine. Invoices and status updates leave the moment they change, including a review request when a repair is completed; incoming questions get an automatic reply; stock answers are one tap away; and a message can go to a chosen segment of your customer list at once.
  • Reminder System — the scheduled side: messages that leave because a date arrived, addressed to customers, suppliers, technicians, staff, or a number you type in yourself.

The Gateway reacts to something happening. The Reminder System acts because a date arrived. Almost every “we forgot to chase that” problem in a repair business belongs to the second category, which is why it stands on its own rather than sitting as a checkbox inside the first.

Automan WhatsApp Gateway settings showing Connected status, Auto Responder, Auto Sender, and quick-answer templates Connected gateway: a status message is filled from its own transaction — job number, unit, tracking link — and addressed to the recipient set for that event. (App UI shown in Indonesian.)

What runs automatically, without you touching a phone

  • Invoices & repair status — sent as the status changes, cutting down the “is it ready yet?” traffic that eats a front desk alive.
  • Automatic Google review requests — sent only to customers whose repair was actually completed; cancelled or failed jobs get an apology instead. You raise the reviews worth having and stop inviting the ones you don’t.
  • Autoresponder & quick answers — opening hours, address, “do you work on this model?” answered automatically or with a single tap, so nobody types the same sentence forty times a week.
  • Targeted bulk messaging — a promotion or a genuine notice to one segment of your customer list, rather than a blind broadcast that earns you a row of blocks.

Watch one job move through it. A customer hands over a handset for a battery swap at ten in the morning and gets the digital job sheet on WhatsApp immediately. At one, a technician starts work, the status changes, and the customer is told the unit is in progress. At three it is finished, and “ready for collection” leaves on its own. The next day, after the unit has gone home, the review request follows. Four touchpoints, none of them typed by hand.

The same day in an auto workshop reads differently

Not a matter of tone. What the customer is waiting for genuinely differs, because what they handed over differs.

In a garage, the sentence everyone is waiting for is “your vehicle is ready to collect.” A car owner rarely waits on site — they drop the vehicle off before work and spend the day guessing. When the job status flips to finished, that message goes out by itself. One automatic message usually replaces three phone calls that land precisely when the mechanic is under the car.

After the vehicle leaves, two moments matter, and both are the kind that get lost without something to prompt them:

  • A follow-up a few days after collection. It is anchored to the collection date, so it runs without anyone doing arithmetic: “how are the brakes feeling now?” For a workshop this is the realistic route back to a returning customer — a conversation while the experience is still fresh, not a guess about when they might need something.
  • A reminder before the workmanship warranty runs out. Scheduled a set number of days ahead of the expiry date. A customer who still hears something odd gets the chance to come back while the cover is live, and you avoid arguing about a warranty that lapsed a month ago.

In an electronics repair counter both moments still apply, with the content swapped: status while the unit is on the bench, then a warranty reminder before cover ends. The difference is where the value sits. Handset owners tend to ask repeatedly during the same day, so the mid-repair update earns its keep more than it does in a workshop, where the finish line is the moment that counts.

Reminder System: 26 scheduled reminders

Business follow-up usually fails not from lack of will, but because it’s forgotten. What makes a reminder useful is where it gets its facts: each one starts from something real in your data — a receivable falling due, a supplier payment falling due, a warranty about to expire, a job that has sat too long, stock running low, stock not moving at all, stock gone negative, a customer’s birthday, or the day’s sales and repair summary for the owner. Twenty-six reminder types in all, sent to the targets you choose.

Three settings do the work, and they are worth understanding before you build your first one.

Who receives it. A reminder is not automatically a customer message. The recipient can be the customer on the job, a supplier, the technician who owns the work, the staff member who entered it, a named person, or a plain custom number. That is what turns “reminders” into something an owner uses internally — a stalled-job nudge belongs to the person who can move it, not to the customer waiting on it.

When it fires. Five scheduling shapes cover the realistic cases: a relative number of days before or after an anchor date, an exact date, every day, every month, or every year. Daily suits an operations digest; a relative day suits warranty and post-collection follow-up; monthly and yearly suit obligations that sit on the calendar rather than on a job.

What it says. The text is filled from the transaction it came from, so the job number, the unit and the amount are already in the message. Nobody is chasing a customer with a generic paragraph that could have been sent to anyone.

Set it once and it keeps running. That is the whole point: the system is not more diligent than you are, it is simply never busy on the day it matters.

What Automan will not do — worth knowing before you sign up

Automan does not work out when a vehicle’s next scheduled service falls due. There is no mileage-based reminder and no next-service date the app calculates for you. The odometer reading is captured when a vehicle is booked in — it sits in the intake checklist and stays on the vehicle’s history — but that number sets nothing in motion.

So if your plan is to bring past customers back in, there are two honest routes and you hold the wheel on both: the automatic follow-up after collection, and a targeted campaign to a segment you choose yourself. Mileage reminders are widely advertised in this market. We would rather lose that comparison than sell you a menu item you will go looking for and not find.

Bulk messaging aimed at people who already know you

A customer list usually rots quietly in a database. Those people already found your shop, already handed over something they cared about, and already paid. When the workshop is quiet, they are the most sensible group to talk to — provided the message is relevant and not fired at everyone with a pulse.

Targeted campaigns let you pick the segment that fits the message. Customers who have not been in for a while can be invited back; customers who collected a repair yesterday can be left alone. Paired with the customer acquisition tools, WhatsApp stops being only a channel for incoming questions and starts working on the data you already own.

The aim is not sending more. It is the right message reaching the right person. Campaign results still depend on your offer, your segmentation, and your judgement; Automan supplies the engine and the brakes.

Safe-usage controls — because we’re honest

Because this gateway is non-official, reliability can’t be promised absolutely, and we won’t pretend otherwise. What Automan gives you instead is control:

  • Contact segmentation — send to a defined group rather than spraying every number in the database at once.
  • Natural delays between messages — spacing that resembles a person sending, not a machine emptying a queue.
  • Sending-hour settings — messages leave during hours a customer would consider normal, not at two in the morning.
  • Automatic holding of cold contacts — numbers that have never interacted with you are held back rather than blasted, to protect the standing of your shop’s number.

None of that is decoration. It is the difference between a vendor who hands you an accelerator and one who admits the road has corners. Software willing to name its own limits is software you can more reasonably trust on everything else.

Two different things wear the same name

The first is prepared text. You still open WhatsApp, find the number, paste, and press send — once per customer. On a busy day that work does not happen.

The second is a message dispatched from a server. You do not touch a phone at all. The gap is not a detail: it decides whether the follow-up happens or merely exists as an intention.

With its own server, status from the repair workflow is genuinely sent without you touching it, and a repair tracking link can be dropped into the template so customers check for themselves instead of asking. The customer hears without asking, the follow-up happens without being remembered, and the owner gets back the hours that went into retyping the same four sentences.

The app speaks your trade, not a generic one

The wording your customers see is yours to write, but the wording you work with adapts on its own. Choose a vehicle business type and Technician appears as Mechanic, Repair Item as Vehicle, Item Type as Vehicle Type, and Symptoms as Customer Complaint — across the whole app, including the recipient picker when you build an internal reminder. Choose an electronics type and the same fields read the way a counter reads them.

One boundary to plan around: a single Store App handles one kind of unit — general electronics or vehicles. If you run both a workshop and a phone counter, they run as two Store Apps under one account. See auto repair shop software or phone repair shop software for how each side is set up.

Where this earns its place

  • A busy phone counter stops retyping the same job sheet and the same status forty times a day.
  • Laptop and electronics repair keeps customers informed through jobs that run several days, where silence gets read as bad news.
  • An auto workshop sends “ready to collect” without a mechanic stopping work to answer a phone.
  • A workshop that wants repeat business leans on the post-collection follow-up and the warranty reminder instead of hoping people remember.
  • An owner carrying receivables and supplier obligations uses reminders so the important things stop losing to the urgent ones.

Before you sign up, two honest notes

Automan was built in Indonesia and is priced there: Lite at Rp 0 and Pro at Rp 15,000 per month, with no separate USD list. Support runs in Bahasa Indonesia, and the app interface is Indonesian — your message templates, though, are text you write yourself, so what your customers receive can be in any language you use with them.

WhatsApp is also not a universal assumption. It is the default channel for repair customers across Indonesia and much of Southeast Asia, and far less so in markets where SMS or email still dominate. That makes this feature decisive in some regions and merely nice in others, and you know your own better than we do.

Neither point changes how the sending works. Both change whether we are the right fit, and you deserve to weigh that before you spend an evening on setup.

The cheapest way to find out is to try it

Every day you wait, your shop’s communication depends on who happens to remember and happens to be holding a phone. The Lite plan is free with no card required, so testing costs an evening rather than a budget. Start from the button above, or walk through the repair workflow demo to see how a status change reaches the customer and the tracking link travels with it.

Disclosure: non-official gateway

WhatsApp runs through a non-official gateway, with safe-usage guidance. We say so openly — no "official" or "ban-proof" promises.

FAQ

Is the WhatsApp integration official?
No, and we don't claim it is. Automan uses a non-official WhatsApp gateway. What you get is real: auto-sending, autoresponders, quick answers, targeted bulk messaging, and 26 scheduled reminders with safe-usage guidance. What we won't promise: "ban-proof" or "100% reliable" — no one can promise that honestly.
What's the difference between the WA Gateway and the Reminder System?
The WA Gateway is the sending engine: invoices and status updates leave as they change, incoming questions get an automatic reply, and a message can go to a chosen segment at once. The Reminder System is the scheduled side — a set number of days before or after a date, on an exact date, or every day, month, or year — addressed to the customer on the job, a supplier, a technician, a named person, or a number you type in. They work together but do different jobs.
Can it automatically ask customers for a Google review?
Yes, and it can be smart about it: review requests go only to customers whose repair was completed, while cancelled or failed jobs get a different message (e.g., an apology). This helps maximize positive reviews without inviting negative ones.
Can it remind a vehicle owner when the next service is due, or at a mileage interval?
No, and we would rather say so before you sign up than after. Automan does not store a next-service date and does not calculate mileage intervals, so nothing leaves the system because a service is "due". The odometer reading is captured when a vehicle is booked in, but that number triggers no message. What genuinely runs on its own is different and still useful: a follow-up a few days after the vehicle is collected, and a reminder a set number of days before the workmanship warranty expires. For anything beyond those two, you segment the customer list yourself and send a targeted campaign.
Do the messages still say "repair unit" if I run a garage?
No. The app relabels itself around the business type you choose at setup. On a vehicle business type, Repair Item becomes Vehicle, Technician becomes Mechanic, Item Type becomes Vehicle Type, and Symptoms becomes Customer Complaint. The change applies across the whole app rather than on one screen, so even the recipient picker for internal reminders says Mechanic.
Why is my message to a brand-new number held back?
That is a risk control, not a fault. Messages addressed to contacts that have never interacted with your shop number — cold contacts — are held and scheduled under the rules instead of firing immediately. The point is to protect the standing of the number your customers already know you by, which matters more on a non-official gateway than on an official API.
Is Automan priced and supported in English?
Pricing is in Indonesian Rupiah — Lite at Rp 0 and Pro at Rp 15,000 per month — and there is no separate USD list. Support runs through Indonesian channels, in Bahasa Indonesia, and the app interface is Indonesian. Message templates are yours to write, so customer-facing text can be in any language you like. We would rather you weigh that before setup than discover it afterwards.

Already know the problem?

See the workflow demo that matches it.