An Automatic Answer System for Customer Enquiries

The maths of customer enquiries is similar in every business: the large share of incoming questions is the repetition of the same 15–20 questions. The price, the opening hours, the delivery, the address, "is it in stock": every day, every day. The automatic answer system is the project of handing that repetition to the machine and returning the human time to the remaining complex (and valuable) questions. Built correctly, the customer wins too: the question typed at 11 pm gets an instant answer.

This article builds the system in four steps: the question map, the technical tier choice, the bot-human boundary and the quality control.

Step 1: The question map; the system's foundation

Before the technology, the paper work: open the last 100–200 customer messages (the DMs, WhatsApp, the comments) and group the questions. The result usually looks like this: 5–6 questions give half the flow, and 15–20 questions three quarters of it. Write an approved answer for each group: precise, friendly-toned, with the needed links ("the price table: link"). This document (the question-answer base) is the system's heart; the technology merely delivers it. The update rule starts here too: when a question with no answer arrives, it gets added to the base; the customer-facing version of the knowledge base discipline.

Step 2: The technical tier choice

Two rules in the tier choice: the flow volume makes the decision (building AI for a small flow is entertainment, not need) and the tiers get built on top of each other (the AI tier too sits on the template base). The bot guide holds the technical setup details; here the architecture decision is the core.

Step 3: The bot-human boundary; the system's ethics

The failure cause of automatic systems is not technical but a design mistake: the bot hiding what it cannot do. The boundary rules: let it introduce itself (the "I am an automatic assistant" honesty raises the customer's patience), let the exit door always show (the "talk to an operator" option at every step; a doorless bot is the recipe for customer anger), let the handover signals be coded (a complaint tone, repeated misunderstanding, money-and-obligation topics → straight to a human) and let the human side carry an obligation (the reply-time standard for a handed-over conversation; if the bot is fast and the human slow, the system as a whole is slow). The tone matter is part of the boundary too: the automatic reply must not be dry; the voice of your service standards must live in the templates as well.

Step 4: The quality control; after the build

The system went live; now the measuring cycle: the resolution rate (what % of questions get solved without a human; the healthy target at tiers 2–3 is 40–70%), the handover quality (how many of those landing on a human were genuinely complex? if a simple question gets handed over, a base gap exists), the customer reaction (a short "did it help?" poll after the bot conversation) and the unanswered log (the weekly review: the new questions into the base). At the AI tier the extra control: because of the invention risk, the free answers must be built only from approved content, and the correct behaviour at "I don't know" (the handover) must be coded. That monthly half-hour review keeps the system alive; an unmaintained bot turns into a museum of stale answers within six months.

Sources and further reading

Where to verify the source

The official source for the platform capabilities:

• WhatsApp Business: the reply tools

Continuing the topic

This line's neighbouring articles:

• The WhatsApp bot setup
• The service standards
• The knowledge base
• The agent level
• Other articles on this topic

Tonight's work needs no technology: open the last 100 messages, group the questions, write one answer per group. Tomorrow move those answers into the quick-reply templates: the system's first tier is ready and already saving time.