Academy › Build › WhatsApp and customers
Turn on the bot today, then fine-tune it with your first real week
By the end, you'll have your WhatsApp bot answering everyone, with the handoff to a person tested, and you'll know what criteria to use to fine-tune it with the real conversations from the first seven days.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
Your WhatsApp bot is ready and tested with the oddball questions your customers actually ask, but it's still not answering anyone. And that's when the doubt kicks in, the one that stops almost everybody right before flipping the switch: do I turn it on now, or wait until it's perfect?
There's no polished version before a real customer speaks up. Even the best-prepared setup has a gap that only shows up when someone writes a sentence you never imagined: a customer asking about a party of twenty when your info only covers tables for two, or someone writing "is this still available?" three weeks after the last conversation. That's not a flaw in your work. It's the only way that gap gets found. The question that matters isn't when it'll be perfect, but what needs to be ready to turn it on today, and what standard you'll use to fix it during the first real week without undoing what's already working. Waiting one more week to polish it on paper doesn't add anything: it just delays the moment you start seeing the mistakes that actually matter, the ones a customer makes, not you.
The bare minimum to turn it on today
To turn on the bot, it doesn't need to cover every question you can think of. It needs three pieces, and once all three are ready and tested, it can start answering.
First, know clearly what the bot decides and what you decide: if the bookings it takes stay pending until you confirm them, someone has to check them every day. Second, the handoff to a person: the customer should know someone will get back to them, so they're not left waiting for a reply that won't come on its own, and you should get the alert. Third, the link to book or pay should arrive with the exact name of what the customer asked for. If your bot answers using your business info, all of that depends on your services, prices, and hours being complete and written correctly there. If those three pieces are in place and you've tested them with your own tricky questions, turn it on today. Whatever's missing gets fixed through real customer conversations, never by guessing ahead of time.
- 1Review your business info
If your bot answers using it, check one by one that every service has its exact name and price, and that the hours are current: whatever isn't there, the bot can't say. And note where each piece of info lives (services, prices, hours, terms), so you know what to update when a fix comes up. - 2Test the handoff
Text it asking to speak with a person, and confirm that it stops answering, that the customer knows someone's going to reach out, and that you get the alert, before assuming it works. If the alert comes by email and you live on your phone, turn on push notifications for that email on your phone before you turn anything on. - 3Test it yourself
From your own number, text the three or four oddest questions you can think of, the same ones you already tested, before an actual customer asks them. - 4Turn it on for everyone
Switch it on for anyone who texts the number, don't leave it off waiting for a perfect moment that's never going to come.
The first week, you read every word
For the first seven days, spend ten minutes a day reading the full conversations, not just glancing at how many there were. That number says nothing about whether the bot is working or not.
Look for three specific things. Where the bot didn't understand and the customer had to repeat the same question in different words, like typing "how much does it cost" and then "what's the price" because the bot missed the first one. Where the customer ended up asking for a person for something the bot could have answered, because a detail was missing or written wrong. And where the customer stalled before booking or paying because they weren't sure what they were buying: that almost always means that service's description is missing something.
Those three points are your fix list for the week. An odd conversation that doesn't fit any of the three goes on a separate note, on paper or in your phone, and you wait to see if it happens again. Read the conversations straight through, top to bottom, not skimming for the word that went wrong: what you miss when you skim is exactly what you need to see to make a good call.
- You change the info as soon as you see the first mistake
- You react to each conversation on its own
- It's easy to lose track of whether the issue keeps happening or was a one-off
- You set aside one fixed day to read through the conversations that piled up
- You only fix what showed up three times or more
- Info changes based on patterns, not one-off cases
Which one to pick: Go with the weekly batch unless the issue is blocking a payment or a booking: fix that one the same day, because every hour it goes unfixed is a sale going cold.
That wraps up the course: the bot up and running, the handoff to a person tested, and fine-tuned with real conversations, not guesses. From here on, the work isn't redoing everything every time something fails. It's reading for ten minutes a day and only touching the detail the pattern points to.
- The bot has your services, prices, hours, and terms complete, and the handoff to a person is tested
- It's turned on for all customers, not just for your tests
- You've set aside ten minutes a day during the first week to read the full conversations
- You know what to fix: what fails three times, not what fails once
- The bot is up and running, from greeting to payment
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. In the first three days, a customer writes, "Do you have room for a party of twenty?" and the bot doesn't know how to answer, so the customer ends up asking to talk to you directly. Do you change the bot's info right away?
Not yet. You note it down and only fix it if two other different customers ask the same thing that week: one isolated case doesn't tell you whether it's a pattern or just an odd question that won't come up again.
You add what's included to that service's description in your weekly batch, because the same issue failed three times: that's a pattern affecting everyone who asks about that session, not one customer's exception.
You add what's included to that service's description during your weekly review, because the same issue failed three times: that's a pattern affecting everyone who asks about that session, not one customer's exception.
3. A customer asks to talk to a person to close a purchase, and it takes four hours to respond because no one saw the alert. Do you wait for your weekly review to look into it?
No. This is holding up a payment, so you fix it the same day: every hour without a reply is a sale going cold, and this kind of issue can't wait for your set review day.
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.
NextThe math you should do before paying for a single click