About the project
Every business has the same 10 questions coming in on WhatsApp every single day. “What are your hours?” “Do you deliver?” “How do I track my order?”
Someone on the team answers them. Manually. Every time.
We built a WhatsApp chatbot connected directly to the official WhatsApp Cloud API — no third-party platforms, no monthly tool fees — that absorbs those repetitive questions and gives the support team their time back.
The setup follows a 6-step flow designed so that any business can configure it themselves, without writing a single line of code.
The 6-step setup
1. Connect Link the WhatsApp Business number to the official Cloud API via webhook. One-time setup, permanent connection.
2. Detect The bot scans conversation history to surface the most repeated questions automatically. No guessing what to automate — the data tells you.
3. Structure Organize the answers into a response tree. Each question maps to a clear, consistent reply. No more “it depends who answers.”
4. Configure Set the triggers — keywords, phrases, intents — without code. If the word “delivery” appears, the bot knows what to say.
5. Test Run real conversation simulations before going live. Catch gaps. Adjust. Make sure the bot handles edge cases before customers hit them.
6. Activate Go live. The bot handles what it knows. Anything outside its scope gets handed off to a human agent instantly — no customer left waiting on a dead end.
Key features
- Native WhatsApp webhook — no paid middleware, no third-party dependency
- Automatic FAQ detection — built from real conversation history, not assumptions
- No-code configuration — any team member can update triggers and responses
- Smart human handoff — the bot steps aside the moment it hits its limit
- Centralized conversation log — full history for audits, training, and continuous improvement
How it’s built
The bot runs on Node.js, connected to the WhatsApp Cloud API via official webhook. The conversation logic follows a state machine — each user message moves the flow forward through a defined path, with fallback rules built in.
No heavy infrastructure. Deployable on any server the client already runs.
Results
| Metric | Value |
|---|---|
| Average response time | Instant (< 1s) |
| Automatic resolution rate | Being tracked |
| Reduction in repeated manual replies | Being tracked |
Data being collected across first client deployments.
