How to automate WhatsApp support without annoying your customers

First, sort your last 50 messages

Before touching any tool, scroll your business WhatsApp and tally your last 50 inbound messages. In almost every service business they fall into five buckets:

1. The repeat questions — "are you open Sunday?", "how much is X?", "where do I park?" Usually a third to half of everything.
2. Booking traffic — new bookings, reschedules, cancellations, "anything earlier?"
3. Status checks — "is my order ready?", "did my payment go through?", "when will you arrive?"
4. Money conversations — quotes, refunds, disputes, complaints.
5. The genuinely weird — the 5% no system predicts.

Your tally is your automation roadmap. Buckets 1–3 are automatable today and are probably 80% of your volume. Bucket 4 needs rules. Bucket 5 stays human forever, and that's fine.

Bucket 1–2: automate fully, but ground it

The difference between a helpful assistant and an embarrassing one is a single word: grounding. The AI must answer from your business facts — your price list, your hours, your cancellation policy — and say "I'll check with the team" when the answer isn't in them. An AI that improvises a price or invents a policy costs you more than slow replies ever did.

Practically, that means before switching anything on, you write down:

• Services and prices — the real ones, including the awkward "from $X, depends on length" cases, phrased how you'd phrase them.
• Hours, address, parking, access notes.
• Policies: cancellation window, deposits, refunds, late arrivals.
• The five questions you're sickest of answering — and your exact best answer to each.

That one-page document does more for answer quality than any setting. In MAVRK it becomes the assistant's knowledge; bookings additionally check your live calendar so offered slots are real.

Bucket 3: automate the lookup, not the promise

Status questions are safe to automate when the assistant can look at the actual record — the booking, the order, the job. What you must not automate is optimism: an assistant that answers "it'll be ready by 3" without checking is writing cheques your afternoon has to cash. If the system can't see the record, the honest automated answer is "let me get someone to check — you'll hear back shortly", plus an alert to you.

Bucket 4: money gets rules, not vibes

Write three explicit rules and give them to the assistant verbatim. For example:

• Discounts: quote list prices only; never negotiate; offer to pass the request to the owner.
• Refunds: under $50 and within policy → process and notify me. Anything else → escalate with the full conversation attached.
• Complaints: acknowledge, apologise once, escalate immediately. Never argue, never explain policy at an angry customer.

The exact thresholds matter less than their existence. An assistant with rules is predictable; predictable is trustworthy enough to leave alone on a Saturday.

The handoff is where automation lives or dies

Three properties make a handoff feel good instead of infuriating:

1. Instant on request. "Can I talk to someone?" is always honoured, first time, no "are you sure?".
2. Context travels. You get the whole conversation, not a notification. The customer never re-explains.
3. The gap is covered. If you can't reply for an hour, the assistant says so honestly — "Priya will get back to you within the hour" — instead of leaving silence.

Measure it with two numbers

After two weeks, look at exactly two things: median time-to-first-answer(was minutes-to-hours, should be seconds for buckets 1–3) and how many conversations ended without you touching them. If the second number isn't at least half, your grounding document has gaps — read the transcripts, find the questions it fumbled, add the answers. Ten minutes of editing a week compounds fast.

What this looks like end to end

Tuesday, 9:40pm: "hey do you have anything for a cut tomorrow??" The assistant checks the calendar — 11:30 or 4:15 — offers both, books 4:15, sends a confirmation, and adds a note to your morning summary. Wednesday, 8am: you read about it with your coffee. That message used to be a lost booking or a 10pm reply from your couch. Now it's neither.