Ongito has deployed AI chatbot agents for a Tokyo photographer, a California real estate agency and a kominka inn tucked in rural Japan, and the fastest of those three went live in eleven working days. The slowest took closer to six weeks. Both used the same underlying AI chatbot agent, the same WhatsApp Business Platform, and the same basic process. The difference had almost nothing to do with the artificial intelligence and almost everything to do with how quickly the client could hand over content, approve copy and get their WhatsApp Business number verified. That is the real lesson buried inside every AI chatbot deployment timeline.
A straightforward AI chatbot for a small business, using an existing WhatsApp Business number and a handful of FAQs, typically takes two to three weeks from discovery to launch. Add complex CRM integrations, a fresh WhatsApp or LINE account needing approval, or content that doesn’t exist yet, and the realistic range stretches to four to eight weeks.
What Is a Realistic AI Chatbot Deployment Timeline for a Small Business?
Most small business AI chatbot projects run two to six weeks from first call to live launch, broken into four phases: discovery, build, testing, and platform approval and launch. The table below shows the ranges Ongito actually works within, not theoretical best case numbers pulled from a sales deck.
| Phase | Typical Duration | What Determines the Length |
|---|---|---|
| Discovery | 3 to 5 business days | How clear the client is on use cases, whether content already exists |
| Build | 5 to 10 business days | Number of conversation flows, integrations, languages |
| Testing and QA | 3 to 5 business days | Edge cases, staff review, revision rounds |
| Platform approval and launch | 1 to 10 business days | WhatsApp Business Platform or LINE Official Account verification, new versus existing number |
Add these up and a lean project, meaning an existing verified WhatsApp number and FAQs already written, lands around two weeks. A project with a brand new WhatsApp Business Account, a CRM integration and content that needs to be written from scratch can run six to eight weeks, and that is normal, not a red flag. See Ongito’s full range of AI chat agents for how these builds vary by industry.
What Happens During the Discovery Phase?
Discovery maps the actual questions customers ask, not the questions the business owner assumes they ask. In practice this means pulling months of email or DM history, sitting with front line staff for an hour, and picking the messaging channel, WhatsApp for most Western and Latin American markets, LINE for Japan. For Sorede Nacho, a Tokyo based photographer, discovery took three days because the inquiry pattern was simple: availability, pricing, location. For Villa Azalea, a kominka guesthouse, discovery ran closer to five days because inquiries needed to cover multilingual guests, seasonal availability and an explanation of what a kominka actually is.
How Long Does the Chatbot Build Phase Take?
Build typically takes five to ten business days, and this is where conversation flows, the knowledge base and any integrations get built and connected. A chatbot answering FAQs with no CRM connection is a five day build. A chatbot that checks real time calendar availability, pushes leads into a CRM and replies in three languages is closer to ten. Ongito builds these agents to run natively on WhatsApp or LINE rather than bolting a web widget onto a messaging app, because that is where small business customers already are, not where businesses wish they were. Full details on how these builds are scoped live under Ongito’s services page.
How Much Time Should You Budget for Testing?
Budget three to five business days for testing, and do not skip it to hit a launch date. This is where Ongito runs the agent through genuinely odd customer phrasing, checks that it hands off to a human correctly, and has actual staff try to break it. Every chatbot survives its first ten polite test questions and then falls apart the moment someone asks something sideways, like requesting a refund in the middle of a booking question. Testing exists to find that failure before a real customer does.
Why Does Launching on WhatsApp or LINE Take Longer Than a Web Widget?
Launching on WhatsApp or LINE takes longer than a website chat widget because both platforms require business verification before an agent can send messages at scale, and that queue sits outside anyone’s direct control.
How long does WhatsApp chatbot setup approval take?
A WhatsApp chatbot setup requires a verified WhatsApp Business Account and phone number before automated messaging can run at scale. According to Meta’s WhatsApp Business Platform documentation, the platform describes the verification process rather than promising a fixed number of days, and Ongito’s own experience matches that: sometimes review clears in under 48 hours, sometimes it sits for over a week. Meta’s guidance is a bit like a contractor saying the kitchen will be done by Friday, probably true, but bring snacks just in case.
How long does LINE chatbot approval take?
LINE chatbot approval is typically faster for a standard Official Account, though certain message types still need review through the LINE Developers console. Businesses launching in Japan should budget a few extra days here because Ongito’s Tokyo clients often want the account name and greeting message in Japanese, which adds a translation and approval round that English only projects skip.
What Actually Makes a Chatbot Project Run Longer Than Expected?
- Integrations. Connecting to an existing CRM, booking system or payment processor adds real engineering time and extra testing rounds.
- Approval queues. WhatsApp and LINE both require business verification, and that clock runs on the platform’s schedule, not the agency’s.
- Content prep. If FAQs, pricing sheets and policy answers do not exist in writing yet, someone has to write them, and that is usually the client’s bottleneck.
- Stakeholder availability. A chatbot needs sign off from someone who actually knows the business, and slow replies are the single most common delay Ongito sees.
- Multi language requirements. Adding Japanese, Korean or Spanish content means writing and reviewing the same material twice, which roughly doubles content prep.
What Are the Most Common Mistakes That Delay a Chatbot Launch?
Use this as an unofficial AI chatbot launch checklist. The most common mistake is treating discovery as optional and jumping straight to build, which guarantees a rebuild once the client realizes the bot is answering the wrong questions. The second most common mistake is starting WhatsApp or LINE verification late instead of in parallel with the build phase, which turns a one week wait into the reason the whole launch slips. The third is skipping a real testing round with actual staff, because a chatbot only ever tested by the person who built it will pass every test and still confuse the first real customer. Ongito’s own AI agents for business page walks through how these builds are scoped to avoid exactly this.
Frequently Asked Questions
How long does it take to build a chatbot for WhatsApp?
A WhatsApp chatbot for a small business typically takes two to four weeks from discovery to launch, assuming the business already has a WhatsApp Business Account. Projects run longer when the number needs fresh verification or the chatbot needs to connect to an outside CRM or booking system.
Can a small business launch an AI chatbot in one week?
A very simple FAQ only chatbot with an already verified WhatsApp number can launch in about a week, but this is the exception rather than the rule. Most projects need at least two weeks to properly map real customer questions and test the agent before it goes live.
Why does LINE approval take longer for some businesses?
LINE approval usually moves quickly for a standard Official Account, but businesses adding Japanese language content or specific message types often need an extra review round. Ongito builds this time into the schedule up front for any Japan focused client rather than treating it as a surprise.
Does adding a CRM integration always delay the launch?
Yes, connecting a chatbot to an existing CRM or booking system almost always adds three to seven business days because the integration needs its own testing round. It is worth the extra time for most businesses since a chatbot that cannot log a lead automatically creates manual work later.
What is the fastest chatbot deployment Ongito has completed?
The fastest was an eleven business day launch for a client with an already verified WhatsApp number and existing FAQ content ready to go. That speed was possible because discovery and content prep were nearly instant, not because the AI build itself was rushed.
The Real Bottleneck Is Never the AI
The honest answer to any AI chatbot deployment timeline question is that the AI is rarely the bottleneck. Discovery, content prep and platform approval queues decide whether a business launches in two weeks or two months, and businesses that treat those steps seriously launch faster, not slower. Ongito’s own projects, from an eleven day WhatsApp launch to a six week multilingual build, prove the same point every time: a chatbot is only as fast to deploy as the business behind it is ready to be. If a straight answer on your own timeline is what you need, Ongito’s audit is the fastest way to get one.