Most Nigerian businesses receive more enquiries on WhatsApp than through any other channel, and most of those enquiries are the same handful of questions. That combination makes automation genuinely attractive.
It also makes it easy to overreach. An assistant that answers the right questions is a real improvement. One that tries to answer everything produces a worse experience than no automation at all, because the customer now has to fight a machine to reach a person.
Where automation clearly works
Questions with one stable answer. Opening hours. Where you are. Whether you deliver to a particular area. What you accept as payment. Whether a service is available. These change rarely, the answer is not situational, and getting it instantly at ten at night is better than waiting until morning.
Acknowledging arrival. A single message confirming the enquiry landed and saying when a person will reply is worth more than most businesses realise. It stops the customer messaging three competitors while waiting.
Collecting the obvious details before a person joins. Which service, which area, roughly what size. Done briefly, this saves the back-and-forth that eats the first ten minutes of every conversation.
Directing to the right person. Existing customer with a support issue versus a new enquiry is a fork worth making automatically.
Status for things with a status. Order dispatched, invoice received, appointment confirmed. Where a real system holds the answer, reading it out is legitimate automation.
Where it fails badly
Anything involving price on a variable job. If your work is quoted rather than listed, an assistant guessing a price creates a number the customer now believes. You either honour it or begin the relationship by retracting it. Publish ranges on your website and have the assistant point at them, but never let it produce a figure for a specific job.
Complaints. Somebody who is already annoyed and gets a cheerful automated reply becomes considerably more annoyed. Complaints should reach a person immediately, and the assistant should recognise the signals and get out of the way.
Anything with consequences if wrong. Medical, legal, regulatory, safety, anything where acting on a wrong answer causes harm. The liability is yours, not the software vendor's.
Negotiation, or any judgement call. Whether to make an exception, extend terms, or accommodate an unusual request is not a rule-following task.
Pretending to be a person. Some businesses give the assistant a human name and let customers believe it. When the customer works it out -- and they do -- the discovery colours everything else. Say plainly that it is an automated reply and that a person is coming.
The rule that keeps you out of trouble
Automate answers you would be happy to see printed on a sign outside your building. Everything situational goes to a person.
If a question cannot be answered the same way for every customer who asks it, it is not a candidate for automation.
The handover is the whole design
Most bad experiences are not caused by a wrong answer. They are caused by no way out.
A customer should be able to reach a person at any point, by saying so in ordinary language, without discovering a keyword. The assistant should offer this itself as soon as it is uncertain, rather than trying a third rephrasing.
When it hands over, it must pass the conversation, not just the customer. Nobody should have to repeat what they already typed.
And the handover has to reach somebody actually there. An assistant that promises a person and delivers silence for two days is worse than an honest out-of-hours message.
Setting expectations honestly
Say what it is. Say when a person is available. If it is nine at night, say the reply comes in the morning, and let the morning reply actually happen.
Customers are tolerant of automation that is upfront about being automation and reliable about what it promises. They are unforgiving of automation that wastes their time pretending.
The prior question
Before any of this: are the enquiries you already receive being answered properly today?
If enquiries currently go unanswered for days, automation will not fix that. It will make the failure faster and more visible. The bottleneck is not the first reply -- it is that nobody is assigned to the conversation afterwards. Solve that with a person and a process first. Then automate the part that is genuinely repetitive.