Academy › Build › WhatsApp and customers
What the bot never lets go of, even with more hands on deck
By the end, you'll have a written list of the questions that always stay with the bot, no matter what happens with your team, plus the rule for deciding whether something new goes on that list or gets handled directly by a person.
By Yodai · Published on September 6, 2026 · Updated on October 12, 2026
Adding more people to WhatsApp doesn't fix two people answering the same message when nobody knows whose conversation is whose. Before you figure out who answers what, you need to pull out of the mix what should never be divided up in the first place. You've brought someone else onto the business WhatsApp. The first instinct, almost always, is to divide things up: you handle these conversations, she handles those, and the bot answers whatever it can. That's the most expensive mistake at this stage. When a new person joins, the bot doesn't change. You decide which questions stay with it for good, and that list doesn't depend on who's on duty that day.
Today's question isn't who answers what, that comes later. It's simpler, and it comes first: out of everything people ask you on WhatsApp, which part always gets the same answer, no matter who's asking, on a Monday or a Sunday? That part belongs to the bot. The rest belongs to a person.
The rule: if the answer doesn't change, it's the bot's job
Think about your last twenty conversations. Some start with what time do you close on Saturdays? or do you take Venmo? or do you ship nationwide?. Those questions have an answer you already knew before the message arrived, and it would be exactly the same whether you, your partner, or the bot wrote it. That's not a case for human judgment, it just needs the information entered once, correctly, because the bot answers using your business's details.
Others change depending on the day or the customer: it arrived broken, what do we do?, I need something different from what's in the catalog, I got charged twice by mistake. There's no answer to memorize there, someone has to look at the case and decide. That's not something you hand to a bot, or even to the new team member, without someone checking it first.
- Hours, address, and payment methods
- Prices for what's already in the catalog
- Whether you have general availability, not a specific appointment slot
- The terms of a current promotion
- A complaint or a charge that doesn't add up
- A custom order that's not in the catalog
- Any message where the customer asks for a discount
- The first question from someone comparing you to a competitor
Which one do I pick: If you're not sure whether something belongs to the bot, ask yourself if the answer would be exactly the same if the message had arrived three months ago. If yes, it's the bot's. If it depends on checking something or making a decision, it's a person's job, even if you now have someone new with free time to pick it up.
The mistake of using the new hire for what the bot already handled
How it looks in writing
With this list written down, you don't have to decide every time your phone buzzes. Nobody takes away what belongs to the bot, no matter how many new people join the team, as long as your business details, the ones it uses to answer, stay up to date. What's next is deciding, within what isn't the bot's job, which person takes each customer.
- A written list of the questions the bot always answers, no matter who's on duty
- The rule for adding something new to that list: the answer doesn't change based on the day or who's asking
- Complaints, custom orders outside your catalog, and requests for a discount always go to a person, who pauses the bot for that conversation.
In Yodai the WhatsApp bot answers with your prices and your hours, and hands the chat over when someone asks for a person. See how the WhatsApp bot for your business works.
NextWhose customer is it