A WhatsApp Business chatbot can be serving real customers in 48 hours if you come to the process with three things ready: an active WhatsApp Business API account verified by Meta, basic documentation of your business (FAQs, pricing, product or service catalogue), and 30 free minutes for the discovery session. At Fluxr, setup costs S/ 349 and includes the complete knowledge base configuration, the custom prompt, the WhatsApp Business API integration and pre-launch testing — with monthly plans at S/ 39 (50 conversations), S/ 149 (3,000), S/ 299 (10,000) and S/ 499 (unlimited), using private self-hosted AI.
The "48 hours" promise is real, but it depends directly on how prepared the company is. Here's exactly what you need ready and what happens in each hour of the process.
What you need before starting
These are the requirements that determine whether the process can be completed in 48 hours or will need extra days:
1. An active, verified WhatsApp Business API account. This is the most frequently underestimated condition. A personal WhatsApp number or even a standard WhatsApp Business account (the free app) isn't enough to integrate an AI chatbot. You need Meta's official API, which requires:
- A phone number dedicated to the API (it can't be the one you use on your mobile).
- A verified Meta Business Suite account.
- An active, verifiable website with your company's information.
- Meta's review process, which takes 3 to 7 business days.
If you don't have the API active when the process starts, those 3-7 days add to the 48 hours. It's the most important thing to get moving early.
2. Basic documentation of your business. The chatbot answers from the information you give it. To configure a useful knowledge base from day one, you need at minimum:
- A list of products or services with prices (or price ranges if they vary).
- The 10-20 questions your customers ask most often.
- Opening hours and promised response times.
- Returns, shipping or warranty policy, where applicable.
- The tone of communication you want the chatbot to use (formal, warm, technical).
You don't need a perfect, formatted document: a spreadsheet or even plain-text notes are enough for discovery.
3. Clarity on the human escalation flow. Define when the chatbot should hand the conversation to a human agent and to which channel (support WhatsApp, email, ticketing system). Fluxr's chatbot transfers with the full conversation context included.
The 48-hour timeline, step by step
| Stage | Duration | What happens | Who does it |
|---|---|---|---|
| Discovery | 30 minutes | Mapping use cases, reviewing documentation, defining tone and escalation flows | You + Fluxr team |
| Knowledge base configuration | 4-6 hours | Building the base from your information, categorising FAQs, defining answers by intent | Fluxr team |
| Prompt and flow development | 4-6 hours | Custom prompt engineering, welcome flow, handling unrecognised intents, handover to a human | Fluxr team |
| WhatsApp Business API integration | 2-4 hours | Technical connection to your API number, webhook configuration and message delivery testing | Fluxr team |
| Internal testing | 4-8 hours | The Fluxr team simulates real conversations across your most frequent use cases | Fluxr team |
| Validation session with you | 1 hour | Live testing with real conversations, final adjustments based on your feedback | You + Fluxr team |
| Production activation | 30 minutes | The chatbot goes live on your WhatsApp Business API number | Fluxr team |
Total: 16-26 hours of actual work. The process can be completed within 48 business hours from the start of discovery.
What to prepare so nothing gets delayed
Experience across sectors shows delays almost always come from the same source: documentation isn't ready at the moment of discovery.
Pre-setup preparation list:
- Confirm the WhatsApp Business API account is active and the number can receive messages.
- Have the 15 most frequent questions written out with their ideal answers.
- List every product or service with its price or price range.
- Decide the name the chatbot will use (it can be your brand name or something like "[Company] Assistant").
- Choose the tone: formal/corporate, friendly/casual, technical/specialist.
- Define the hours when human agents will be available to receive transfers.
- Have the company's technical contact on hand in case there are questions about CRM or other integrations.
With this list complete at discovery, the Fluxr team can move at full speed without pausing to request more information.
The most common mistakes when launching a WhatsApp chatbot
Mistake 1: launching with an incomplete knowledge base
A chatbot answers exactly as well as the information you gave it. If you launch with incomplete FAQs, the chatbot will give generic or incorrect answers in the first days of operation, creating a poor first impression that's hard to reverse. Better to wait a couple of days to document properly than to launch fast on half-complete information.
Mistake 2: not having proactive message templates approved
If you plan to use the chatbot to send notifications, reminders or confirmations (messages your company initiates, not the customer), you need templates approved by Meta in advance. The approval process can take several days. Without approved templates, the chatbot can only reply when the customer writes first.
Mistake 3: not defining the escalation flow from the start
"What happens when the chatbot doesn't know the answer?" is a question to settle before launch, not on the day it happens. A good escalation flow defines which situations trigger a handover, with what message and to which channel. Without it, the cases the chatbot doesn't handle well go unresolved.
Mistake 4: not testing with real cases before going live
The Fluxr team's internal tests cover the documented scenarios. But real customers always ask unexpected things. The validation session with you — where you test the chatbot pretending to be a real customer with edge-case questions — is the best opportunity to spot and fix answers before launch.
Mistake 5: expecting the chatbot to resolve 100% of cases
The goal of a well-implemented chatbot isn't to replace human support entirely but to resolve 90% of repetitive enquiries so the human team can focus on cases needing judgement and empathy. Setting that expectation correctly internally prevents frustration when the first transferred cases arrive.
When buying now doesn't make sense
Honestly:
- If you don't have the WhatsApp Business API account active, the real process can take 10-14 days because of Meta's verification time. Start verification first, then buy the chatbot.
- If your support team is in peak season with every agent saturated, the chatbot's initial testing and tuning period can be hard to manage. Wait for a period of lower operational pressure to launch with proper attention.
- If you have no business documentation ready at all, spend a week writing your FAQs and catalogue first. The chatbot is only as good as the information it receives.
None of these is a definitive "no" — they're simply conditions worth resolving first so the 48 hours are real and the launch succeeds.
See the chatbot in action before deciding
The live chat demo at fluxr.pro/text-agents lets you talk to the agent right now, with no signup. It's the most direct way to judge answer quality, speed and tone before committing to setup.
You can also review the case studies to see how companies across sectors deployed their chatbots and what results they achieved.
Next steps
- See the live chat demo — talk to the agent now, no signup and no card.
- Compare the full plans — chatbot, voice and automations with every detail.
- Ready to start, or have questions? Message us on WhatsApp and we'll arrange discovery the same day.
Fluxr Pro builds WhatsApp Business chatbots with private AI and 48-hour production for businesses worldwide — native support in English, español and português.