How long it takes to get your WhatsApp handled by AI: instantly if it exists, two weeks if it is custom

The short answer, with its two branches

How long it takes to set up AI on your WhatsApp comes down to one question: whether what you need already exists or has to be built.

If what you are asking for is already on the platform, the testing stage starts right away. You configure it, give it context, try it, and it goes live. If your case takes custom development, the typical turnaround is around two weeks.

Almost every business falls into the first branch without knowing it, because they arrive convinced their operation is unique. Sometimes it is. Most of the time what looks unique is a combination of things that already exist.

The order that works

The sequence matters more than the speed, because doing it backwards is what stretches the timeline:

1. Configure the Orbi. Instructions, tone, what it does and what it does not.
2. Give it context. Your price list, your policies, your documents. It answers from those and not from guesswork.
3. Test it in the Sandbox. In a safe chat, before it talks to a real customer.
4. Connect the channel and go live.

There is a variant plenty of businesses use that is worth putting on the table: connect the channel first and start using the inbox without the AI turned on. You get the team, the tags and the assignment in order, and switch automation on when you are ready. It pays off from day one and takes the anxiety out of the change.

The clock we do not control: Meta

Here is what usually catches people off guard. The slow part is rarely the configuration. It is getting the number approved with Meta.

Meta does not publish a guaranteed timeline for business verification, and in practice it stretches or shortens depending on how tidy the paperwork is: tax registration and proof of address matching the legal address. It is the stretch neither your team nor ours controls.

That process runs in parallel with everything else. If you start verification the same day you start configuring, by the time the number is approved you already have the Orbi tested.

If your channel is already running, this clock does not apply to you.

What you need before starting

The list is short:

• The channel ready. WhatsApp Business, and any others you want to add.
• Sign in to the panel and go through onboarding, which activates the free Pro trial.
• Your documents at hand, the business ones for Meta and your operational ones for the Orbi.

That is enough to book a demo running on your own configuration, not on a generic example.

Why it does not pay to stretch this out

There is a concrete reason not to leave this for next quarter, and it is that the cost of the delay is already running.

Harvard Business Review audited 2,241 companies, measuring how long each took to respond to a web-generated lead. 23% never responded, and those that did averaged 42 hours. In a separate study of 1.25 million leads, firms contacting within the hour were nearly seven times as likely to qualify the lead as those trying just an hour later, and more than 60 times as likely as those waiting a day. That clock does not wait for you to finish evaluating vendors. We covered it in how long you take to answer a WhatsApp.

And there is a date on the calendar: from October 1, 2026 Meta starts charging for messages that are free today. Arriving with your operation in order before that date is not the same as arriving after. It is in the 24-hour window.

You do not start alone, and you do not start blind

Two things that lower the risk of going live.

The first is the Sandbox: you test in a safe chat, pick real contacts from your address book to see how it would respond in concrete situations, and add contact notes to simulate special scenarios. You adjust until it works the way you want, without any customer seeing the process.

The second is gradual rollout: you can start with the AI replying only in the conversations you tag, and widen the scope at your own pace. And you can pause the service whenever you want.

On our side, guidance through setup is part of the service, with a discovery call and a live personalized demo.

Key takeaways

• If what you need already exists on the platform, the testing stage starts right away.
• If it takes custom development, the typical turnaround is around two weeks.
• The usual bottleneck is not configuration: it is getting the number verified with Meta, which has no guaranteed timeline and depends on how tidy the paperwork is.
• The order that works is configure, give context, test in the Sandbox, and only then connect the channel.
• You can start by using the inbox with the AI switched off and turn automation on later.
• Gradual rollout and the Sandbox mean going live is not a leap in the dark.