WhatsApp AI chatbot development for business
We judge a bot by whether it books the appointment, sends the payment link and knows when to get out of the way, rather than by how fast and perfectly it answers.
What it is
We build on the official WhatsApp Business API, not on an unofficial bridge. That decision costs more at the start and is the reason the number does not get banned later.
The bot is given the business, not a script: prices, availability, what is and is not offered. It answers in the customer’s language, and it hands the conversation to a human the moment it should. A bot that improvises about money is a liability, so ours are built so they cannot.
We learned two things the expensive way, and both are now built in by default. Latency is what gives a bot away: an answer that lands in 400 milliseconds reads as a machine no matter how good the words are. And a bot must never be able to send a message containing an unfilled placeholder to a real customer. That rule is enforced in code rather than left as a note in a prompt.
Seen working
Lawang Estate — a setter and an agent assistant, in testing mode
The developer’s CRM has an AI setter in a two-panel, WhatsApp-style chat, and a second bot answers the sales team’s own questions from a source Legal has reviewed. Both run on the number that already receives real leads, in testing mode: until the owner opens it, the bot only answers the numbers on an allowlist, so testing it needed no new number and no new app.
- prices it can invent
- 0
- handover to a person, with the context
- 1
- bots: one for buyers, one for the team
- 2
How it flows
- STEP 1MessageA lead writes on WhatsApp.
- STEP 2SourceThe bot reads prices and rules from one place.
- STEP 3QualifyIt asks what an agent would ask.
- STEP 4HandoverPasses to a person with the context attached.
- STEP 5CloseThe agent picks up where the bot stopped.
What's included
| # | COMPONENT | WHAT IT MEANS |
|---|---|---|
| 01 | Channel | Official WhatsApp Business API, with the number and templates properly registered. |
| 02 | Knowledge | Your prices, availability and rules in one source, updated without redeploying. |
| 03 | Booking | Writes into a real calendar, not a form the team has to re-enter. |
| 04 | Payments | Sends a live payment link and knows when it has been paid. |
| 05 | Handover | A defined line the bot does not cross, and a clean pass to a human when it reaches it. |
| 06 | Languages | Answers in the language it is written to, including the ones your team speaks. |
| 07 | Visibility | Every conversation readable by you, with what the bot said and why. |
Questions
Will it get our number banned?
Not if it is built on the official Business API with registered templates, which is how we build them. Unofficial bridges are the ones that get numbers banned, and they are cheaper for exactly that reason.
Can it use our existing WhatsApp number?
Usually yes, through the official migration or coexistence path. It is a process with Meta rather than a switch, and how long it takes is up to them, not us.
What stops it inventing a price?
It reads prices from one source and it is not allowed to answer outside it. Where a question touches money it does not have, it hands over to a human.
Can a human take over mid-conversation?
Yes, and that is the point. The bot is there to remove the repetitive 80%, not to stand between you and a customer who is ready to buy.
Does it work in more than one language?
Yes. Ours run in English, Spanish and Bahasa Indonesia depending on the project.
Have something worth building well?
Tell us what you are working on. We usually reply within a day.