Skip to content
StriqTech Logo
Back to blog
Chatbots & AI12 min read

How long it takes to implement an AI WhatsApp chatbot (real timeline stage by stage)

With a verified Business Manager, an available number and content ready, a narrow scope usually goes live in 3 to 10 business days. If any key is missing, 3 to 8 weeks.

A narrowly scoped AI WhatsApp chatbot usually goes into production in 3 to 10 business days when the company already has a verified Business Manager, an available number and the response content ready. If any of those three things is missing, the real timeline stretches to 3-8 weeks. Development is not the bottleneck: the flow gets built in 2 to 5 days of work. What stretches the calendar is Meta's verification (1 to 5 business days with the paperwork in order, 2 to 4 weeks if there is a rejection), getting access to the CRM or the calendar, and getting someone on the company side to sit down and write the prices and the policies.

Timeline stage by stage: how long each one takes and who it depends on

These are reference ranges for WhatsApp chatbot implementations for small businesses on Meta Cloud API. The column that matters is not the duration: it is whether the timeline is controlled by the consultancy, the client or Meta.

Adding up the stages that depend only on the consultancy, the technical work is 3 to 8 days. Everything else is paperwork and content.

Meta verification: 1 to 5 business days if the paperwork is right, 2 to 4 weeks if it is not

Business verification is done in Meta Business Suite, under Business settings, inside the Security Center. What you need ready:

The most common rejection has nothing to do with the company's line of business: it is that the legal name entered in the form does not match the one on the tax certificate letter for letter. "Clínica Dental del Sur" is not the same as "Odontología del Sur S.R.L.". Each correction and resubmission cycle costs between 5 and 15 days, and two rejections in a row turn a two-week project into a project of well over a month.

Two things worth separating from the launch timeline:

The WhatsApp number: the decision that delays more projects than it seems

There are three paths, and the one almost everyone picks first is the worst one to start with.

Migrating the number you already use. To connect it to the API you have to delete that account from the WhatsApp app: you lose the history that lives on the phone, the groups and the statuses, and going back requires removing the number from the API and registering it again in the app. Because it is irreversible in the short term, the owner postpones it "until after the end of the month" and the project sits still waiting for a decision that is not technical.

A new line. It costs whatever a prepaid line costs and it is sorted out the same day. The real downside is that customers already have the old number saved: you have to leave an auto-reply on it with the wa.me link to the new one and change it on the website, the email signature and the Instagram bio. Traffic takes 2 to 4 weeks to move over on its own.

A landline number. It is verified by voice call. It works, but someone has to be next to the phone at the exact moment of verification: in practice it adds a day of coordination.

The recommendation: start the pilot with a new line and decide on migrating the historical number once the bot is stable. Deleting the WhatsApp account of the number your revenue currently comes through is the last thing you touch, not the step that blocks registration in Cloud API.

A note on how current this is: Meta's requirements (business verification, number migration, messaging limits and template approval) and the availability of each integration change over time. What this guide describes is useful for planning, but it has to be confirmed for each case at the start of the project.

The knowledge base and the access credentials: this is where most of the time is lost

A WhatsApp bot with RAG answers well about what exists in writing. What you need before building anything:

The shortcut that saves a week: export the chat history from the phone (Settings, Chats, Export chat) for the last 3 to 6 months. That is where the questions customers actually ask come from, not the ones the owner thinks they ask. It is common for between 5 and 8 topics to account for the bulk of the queries, and the rest is a long tail the bot can hand off.

Access credentials have to be requested on day one, not on build day: a HubSpot private app token or a Pipedrive API key, a Google account with write permission on the calendar that will be used (the company's, not the personal one of whoever works the front desk), credentials for Tiendanube, Shopify or Mercado Libre if there is a catalog — Tiendanube and Mercado Libre are the dominant online store and marketplace platforms in LATAM — and the Chatwoot user or the inbox where the human handoff will land. Every credential missing on build day adds between 2 and 4 calendar days, because the back and forth to obtain it is never immediate.

What can go live quickly once the keys are ready (and what cannot)

With the three keys ready, a narrow scope can be operational in a few days. Those days are implementation work, not paperwork, and the proposal sets out stages and timelines, separating our work from the dependencies on the client and on third parties. A first stage like that usually covers:

What does not fit, no matter the budget:

A day-by-day example: dental practice, from signature to pilot in 8 days

An illustrative scenario from the healthcare vertical, built with figures typical of the sector. It does not describe a real client and it is not a StriqTech result: it is here to show how the stages fit together.

Starting point: three chairs, two people at the front desk, between 400 and 600 monthly queries through a single number, a little more than half of them outside business hours. They already had a Business Manager because they ran Instagram campaigns, but no business verification.

Eight calendar days to the pilot, thirty to have it fine-tuned. If the verification had been rejected over the legal name, that would have added 5 to 15 days. If they had insisted on migrating the historical number, roughly as much again. If, instead of exporting the chats, the owner had written the responses "whenever he had time", that is where six-week projects come from.

What turns a 2-week project into a 2-month one

Ordered by how much each one costs, in calendar days:

  1. Content without an assigned owner: 7 to 21 days. The most expensive and the most invisible. "Let the team review it" with no name and no date means the bot has nothing to answer with, and there it sits with the number already registered.
  2. Business verification rejected: 5 to 15 days per cycle.
  3. Access credentials held by third parties: 5 to 15 days. The CRM managed by a former provider, the store token left with the previous agency.
  4. Scope that grows halfway through: 7 to 14 days. "While we're at it, have it issue the invoice too." The expensive part is not building it: it is that it reopens testing of the entire flow and, if new templates are needed, another round of Meta approval.
  5. Approval of the response copy by committee: 5 to 10 days. Four people reviewing how the bot says hello.
  6. Insisting on the number that is already in use: 3 to 10 days of postponed decision.
  7. A system without an API. This is not measured in days. If the data the bot needs lives in closed desktop software, it is not a delay: it is a different project.

When it is better to hold off instead of rushing the launch

Going live as soon as possible is not always the right call. Cases where we recommend not accelerating, or simply not connecting the number yet:

In the first conversation this is part of what we review: if the volume or the state of the content does not justify the project, it is better to say so before putting together a proposal, not after.

How long a project with custom integrations takes (and what can be parallelized)

When the assistant needs process analysis, non-standard integrations with the ERP or the management system, or more complex handoff rules, the project usually runs between 4 and 8 weeks end to end: 1 to 2 weeks of discovery, 2 to 4 of building and 1 to 2 of testing with real users before opening the number to the public. The difference with a narrow scope is not in the engine, which is the same: it is that the process gets defined first and automated afterwards, and that takes people's time, not code time.

One rule applies to any scope: start the business verification with Meta the day you sign, even if you still do not know what the bot is going to answer. It costs nothing, it runs in parallel with everything else and it is the only timeline in the project that cannot be compressed. Projects that fall behind almost never fall behind because of the flow; they fall behind because the paperwork started late.

There is no timeline that fits every case: it depends on which of the three keys you already have, how much needs to be integrated and how much traffic comes in to fine-tune the responses. If you are thinking about a WhatsApp assistant, or about connecting it to your order, inventory or management system, tell us what you need to solve. After a first conversation we will propose the next step; if we move forward, the proposal details scope, deliverables, dependencies and acceptance criteria, with stages and timelines that separate our work from what depends on your team, on Meta and on other providers. Write to us at info@striqtech.com or through our contact page.

Frequently asked questions

How long does Meta take to verify my company so I can use the WhatsApp Business API?

Between 1 and 5 business days when the documentation goes through without objections: a tax registration certificate (ARCA in Argentina, CIF in Spain, RFC in Mexico), a proof of address in the company's name and your own domain with an email address on that domain. If Meta rejects the submission, each correction and resubmission cycle adds between 5 and 15 days. The most frequent cause of rejection is that the legal name entered does not match the one on the tax certificate letter for letter.

Can I use the WhatsApp number I already use with my customers?

Yes, but migrating it to the API means deleting that account from the WhatsApp app. You lose the history that lives on the phone, the groups and the statuses, and going back requires removing the number from the API and registering it again in the app. In practice it is better to start the pilot with a new line, leave an auto-reply on the old number with the wa.me link to the new one, and only migrate the history once the bot is stable.

What delays a WhatsApp chatbot project the most?

It is not the development work, which usually takes 2 to 5 days. What delays projects the most is content without an owner: the current price list, the policies and the real frequently asked questions. When that task is left as a vague team responsibility, it adds between 7 and 21 calendar days. The second factor is access credentials held by third parties: the CRM token managed by a former provider or the online store credentials held by an outside agency.

Can you have a WhatsApp chatbot running in a few days?

For a narrow scope, yes, as long as the three keys are ready before you start: identity verified with Meta, an available number, and the response content plus the access credentials handed over. Those few days are implementation work, not paperwork. They can cover the support flow with RAG, lead qualification, human handoff and the conversation dashboard. They do not cover the official verification with the green check mark, high messaging limits or fine-tuning the tone, which needs between 2 and 3 weeks of real traffic. The actual timeline is set in the proposal for each case, separating the technical work from what depends on the company, on Meta and on other providers.

Is it faster if I use Evolution API instead of Meta's official API?

Yes, considerably: a number gets connected in hours because there is no business verification or template approval in the way. The cost is the risk: you operate on WhatsApp without a contractual relationship with Meta, there is no green check mark, there is no formal support if the number gets blocked, and that block can arrive without warning. It works for validating a use case or for internal volume; not for the main number your revenue comes through.

Want to apply this in your company?

Tell us which process you want to sort out and which systems you use today. We review your inquiry and coordinate the next step.

Let's talk on WhatsApp

You may also like