/Guide · 5 min read

What a WhatsApp chatbot should and should not handle

Let a chatbot answer the repetitive questions, collect details and handle simple requests. Hand over to a person when the customer is ready to buy, is upset, or asks something unusual. A bot that will not let go of the conversation loses sales.

WhatsApp5 min read · Updated 2026-10-20

Published · Updated · By the Cogineo team

Start with the questions you answer ten times a day

Open your chat history and list the questions that keep coming back: opening hours, price ranges, delivery areas, order status. Those are your first bot answers. They save your team time and give customers an instant reply, even at night.

Collect details without an interrogation

A bot is good at gathering the facts a salesperson needs: name, what the customer is after, budget range, preferred time. Ask one thing at a time, keep it short, and skip anything you do not truly need.

Know when to hand over

Decide the handover moments in advance and make them easy to trigger: the customer asks for a person, mentions a complaint, asks about price negotiation, or the bot does not understand twice in a row. When it happens, pass over the whole conversation so the customer never has to repeat themselves.

Where Gemini AI helps

A simple menu bot is limited to the paths you built. An AI assistant built on Google's Gemini can understand free-form questions and answer from your own product and policy information. It still needs limits on what it may answer and a clear handover, because AI can get things wrong.

Write the way a person would

Short sentences, your own tone, no jargon. If your shop is friendly, the bot should be too. Say it is an automated assistant, and let people reach a human easily.

Read real chats every week

The best improvements come from real conversations. Look for places where customers got stuck or asked something the bot missed, and fix those first.

A worked example: a clinic enquiry line

Take a dental clinic that receives messages at all hours. Many are the same: where are you, what are your timings, do you take my insurance, how much is a check-up. The receptionist spends most of the morning copying the same answers.

A well-built bot answers those instantly, then asks for the patient's name, the reason for the visit and a preferred time. It does not diagnose, quote a treatment plan or promise an outcome. When someone describes pain, mentions a child, or asks something medical, it passes the chat to a person with everything collected so far.

The receptionist then starts the day with a list of ready-to-book enquiries instead of a pile of unanswered greetings. Healthcare is sensitive, so we work with clinics such as Jupiter Clinics on what the bot may say and what it must leave to staff.

Tasks that suit automation and tasks that do not

A rough sorting exercise saves a lot of regret. Write down every type of message you receive, then place each in a column.

TaskBot or personReason
Opening hours, location, delivery areasBotSame answer every time
Order status lookupBot, with a link to a personData comes from your system
Collecting name, need and timingBotSaves the first minutes of every lead
Price negotiationPersonNeeds judgement and flexibility
Complaints and refundsPersonTone and trust matter most
Medical, legal or financial advicePersonErrors carry real risk

Mistakes that make bots annoying

Most failed bots share a few habits. Run through this list against your own flow, or against the bots of businesses you buy from, and you will spot them quickly.

  • A long menu of options before the customer can say what they want.
  • No visible way to reach a person.
  • Answers that repeat the question back without adding information.
  • Asking for details the team already has, such as a phone number on WhatsApp itself.
  • Sending long blocks of text instead of two short messages.
  • Out-of-hours messages that promise a reply "soon" without saying when the team is back.
  • Never reviewing the chats, so the same gap stays open for months.

Languages and tone across regions

Customers in the UAE, Qatar and India often switch between English, Arabic, Malayalam or Hindi inside one chat, and some type in English letters for a local language. Decide which languages you will support, and say so clearly in the first message.

If the bot cannot handle a language, route the customer to a person who can rather than letting it guess. Test with real messages from your own chat history, including spelling mistakes and voice notes, since customers do not write the way a script expects.

Finally, remember the platform rules. Messages that start a conversation outside the customer's recent activity use approved templates, and the provider sets the charges. Check the current rules and pricing with your provider when planning volumes.

Frequently asked questions

No. It takes the repetitive work off them so they spend time with customers who are ready to talk.

Usually not, when it answers quickly and a person is easy to reach. They mind when they feel trapped.

It can collect the details and send a payment or booking link, and in some setups confirm the booking itself. Decide how much to hand to the bot based on how much a mistake would cost you.

Look at how many chats it resolves without a person, how often customers ask for a human, and how many leads reach your team with complete details. Read a sample of conversations every week as well as the numbers.

Sources and further reading

Need help with WhatsApp CRM?

A shared WhatsApp inbox, lead capture and automatic follow-ups.

Have a project in mind?