WhatsApp Auto Sender, Auto Responder, and Quick Reply

Level Advanced Role Owner/Admin, Front Desk Module CRM, Reminder System About 25 minutes
Updated

Automan WhatsApp Gateway settings for Auto Responder, Auto Sender, and quick-answer templates Configure incoming-message patterns, automatic status templates, dynamic transaction fields, triggers, recipients, and quick answers on one page. (App UI shown in Indonesian.)

Once the shop’s number is connected, these three features are what make WhatsApp work for you: Auto Sender updates customers unprompted, Auto Responder answers incoming chats while you’re busy, and Quick Reply lets the front desk reply in two keystrokes (the ”/” key).

One stance we hold honestly from the start: these automatic features ship with safe-usage tooling (dynamic delays, sending hours, human-like patterns) — but no system can guarantee a number immune to blocking. Your usage discipline remains the key.

Before you start

  • The WA Gateway is connected and shows Connected (see the connecting-WhatsApp tutorial).

Steps

  1. Meet the three features and their roles

    Auto Sender = automatic outgoing messages when something happens (e.g. a repair status changes). Auto Responder = automatic replies to incoming chats. Quick Reply = fast-reply templates called manually while serving a chat. All three are managed from Settings → WA Gateway.

    The three advanced WhatsApp features: Auto Sender, Auto Responder, Quick Reply
    Three different roles, one management home: WA Gateway.
  2. Start from the built-in Auto Sender templates

    Automan ships ready-to-use Auto Sender templates. Adjust as needed via the pencil (edit) icon in the Message Templates table — faster than writing from zero.

    The Auto Sender message-template table with the pencil edit icon
    Start from the built-in templates — edit as needed.
  3. Create/configure a template: name, transaction type, trigger

    Each template has: a Name, a Transaction Type (Repair for jobs, Sell for sales, Buy for purchases), and a Trigger Type — for example Status: the message sends automatically when a repair enters a given status (e.g. "done, ready for pickup").

    The template form with Name, Transaction Type Repair Sell Buy, and Status trigger
    The Status trigger: messages run themselves on status changes.
  4. Personalize the message with masking variables

    Use masking variables (customer name, receipt number, the tracking link like %URLTRACK%) so every message feels personal — not a stiff broadcast. Personal messages get read more and are safer.

    Message content with name and tracking-link masking variables
    Masking makes every message feel personal.
  5. Enable the Auto Responder in moderation

    Set automatic replies for incoming chats — a greeting and basics (opening hours, how to check status). Don't overdo it: a chatty responder feels like a bot.

    Auto Responder settings for incoming chats
    A greeting + the basics is enough — no chatty bots.
  6. Use Quick Reply with the "/" key

    When replying to chats in Tools → WhatsApp (or from the WA icon in Repairs → List), type "/" in the message box to surface Quick Reply templates. Mind the scope: General-scope templates work in every method; other scopes fit their context with different masking.

    Typing a slash surfacing Quick Reply templates in the chat box
    Type "/" → templates appear; General scope = all-purpose.
  7. Obey the safe-usage rules

    Use long, varied delays (set the Lowest Delay and Highest Delay with a sensible gap), send only in active hours, and use the Skip Hours feature with discipline. Avoid rapid-fire messages and generic context-free blasts.

    The Lowest Delay, Highest Delay, and Skip Hours settings
    Long varied delays + active hours = the discipline that protects the number.
  8. Understand what the system does — and its limits

    Automan imitates human patterns (opening the chat, reading, typing status, then sending), applies dynamic delays per your settings, and provides masking. But this reduces risk, never removes it — how you use it still decides the number's health.

    Illustration of the human-like sending pattern: open chat, read, typing, send
    The system helps reduce risk — never a guarantee of immunity.

What you end up with

Status notifications sent automatically with personal wording, incoming chats answered consistently, the front desk replying in two keystrokes with "/" templates — all with usage patterns that protect the number's health.

If something goes wrong

A template doesn't send on a status change

Check in order: the connection shows Connected, the template is active with the right Transaction Type (Repair/Sell/Buy), and its Status trigger matches a status the shop actually uses.

Quick Reply templates don't appear when typing "/"

Check the template's scope — specially scoped templates only appear in their context. For all-purpose templates, use the General scope.

Afraid the number gets blocked

Follow the discipline in step 7: long varied delays, active hours only, personal messages. The system helps imitate human patterns, but nothing can guarantee immunity from blocking — we choose to be honest about this.