Features

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

Most apps stop at “send the repair status to the customer.” Automan goes further — and what sets it apart is that Automan runs its own WhatsApp server, rather than just preparing templates you still have to open and send one by one. 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.

Two separate engines: WA Gateway & Reminder System

These are often mistaken for one, but they’re two modules with different roles:

  • WA Gateway — the sending engine. Auto-sender (invoices and status delivered the moment they change, including an automatic review request when a repair is completed), autoresponder (auto-reply to incoming patterns), quick answers (masked one-tap replies), and targeted bulk messaging.
  • Reminder System — a separate module for time-scheduled messages to flexible targets: customers, suppliers, technicians, staff, or custom numbers.

Automan WhatsApp Gateway panel sending invoices and repair status automatically WA Gateway: invoices and status sent on their own the moment they change — not a template you click.

What can run automatically

  • Invoices & repair status — sent as the status changes, cutting down “is it ready yet?” messages.
  • Automatic Google review requests — sent smartly only to customers whose repair was completed; cancelled or failed jobs get an apology instead. Positive reviews rise, complaints are softened.
  • Autoresponder & quick answers — repeat questions answered automatically or with one tap.
  • Targeted bulk messaging — promos or important news to a specific customer segment, not a blind broadcast.

Reminder System: 26 scheduled reminders

Business follow-up usually fails not from lack of will, but because it’s forgotten. The Reminder System schedules it for you: due receivables, expiring warranties, stalled repair statuses, low stock, daily owner reports, customer birthdays, and win-back for lapsed customers. Twenty-six reminder types in all, sent to the targets you choose.

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, natural delays between messages, sending-hour settings, and automatic holding of cold contacts (numbers that have never interacted) to protect your shop number’s health.

Why this is far from “just templates”

Many apps claim “automatic WhatsApp” when they only mean preparing text you still copy and send by hand. The difference is clear: with its own server, status from the repair workflow is genuinely sent without you touching it. That’s what makes follow-up actually happen — instead of good intentions that get forgotten.

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: auto-sender (invoices and status as they change), autoresponder, quick answers, and bulk messaging. The Reminder System is a separate module that sends time-scheduled messages to flexible targets — customers, suppliers, technicians, or custom numbers. They work together but play different roles.
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.

Already know the problem?

See the workflow demo that matches it.