Meta Business Agent implementation for WhatsApp
Meta put its AI agent inside WhatsApp. We wire it to your catalog, your calendar and your CRM through the Business Agent Platform, and we make the handoff to a human actually work.
- We verify phone number and vertical eligibility before anything else
- Connectors to your own APIs: orders, inventory, scheduling and CRM
- Escalation to your team with real conversation control
- Agent testing and evaluation before it goes live
Last updated: September 2026
AI Agent · Store
online
How it resolves a real conversation: reads the catalog, checks stock, books, and hands over when it has to.
We are a Meta technology partner
As a Meta Tech Provider we keep the technical and billing relationship directly with Meta, with no reseller in between. That means early access to new platform capabilities and an implementation that does not wait on a middleman's roadmap.
- Direct relationship with Meta, no API reselling
- Built on the Business Agent Platform, not just switched on from the app
- LatAm coverage: Colombia, Mexico, Chile, Peru, Argentina and Uruguay
What Meta Business Agent is
Meta Business Agent is the AI agent Meta built into WhatsApp: it answers questions about your business, recommends products from your catalog, books appointments, qualifies leads and closes sales inside the chat, and hands the conversation to a person when it needs to. Meta opened it to every eligible market on June 3, 2026.
According to Meta, more than one million businesses were already using it across WhatsApp and Messenger at launch.
Source: Meta Newsroom, June 2026.
Full guide: what it is and how it worksNative activation vs. Business Agent Platform
Both routes exist and they are not mutually exclusive. The difference is what the agent can actually do.
Switch modes to see what the agent gains on each route
- Time to go liveMinutes2 to 5 weeks
- Where knowledge comes fromYour website, page and FAQsPlus files, live catalog and internal APIs
- Actions against your systemsNoYes, through connectors and tools
- Handoff to a human agentManual, from the inboxProgrammatic, with conversation control
- Brand voice and prioritiesBasic setupYour own system instructions
- Testing before productionNoTest and evaluation endpoints, plus an allowlist
- Who can do itThe business ownerAn integrator with a Meta app and permissions
Source: Meta Business Agent Platform documentation, 2026.
Why switching it on yourself falls short
Turning the agent on from the app takes ten minutes. What breaks afterwards does not.
Your number may not be eligible
The Meta Business Agent tab only shows up in WhatsApp Manager if the number clears country, verification and trust requirements. When it is missing, the fix is working through eligibility, not tapping harder.
Some verticals are excluded
Meta does not enable the agent for finance, health, government, alcohol, gambling, over-the-counter drugs or matrimony services. Better to know that before designing the project.
No payment method, no delivery
The agent requires an active payment method in the Billing Hub. Without it messages are simply not delivered, and the failure is silent: everything looks fine until nobody receives anything.
One number, one messaging product
A single number cannot run several messaging products at once. Deciding how the agent coexists with your current API or inbox is part of the design, not a footnote.
On its own it cannot read your systems
Without connectors the agent does not know an order status, whether an item is in stock, or what slots your calendar has. It answers nicely and resolves nothing.
Policy limits what it can say
Since January 2026 agents must be task-specific rather than general-purpose, and free-form replies are only allowed inside the customer service window the customer opens.
What we implement, precisely
Every block maps to a real surface of the Business Agent Platform. This is not a layer of ours on top: it is Meta's platform, configured properly.
Surface 01/ 06
Business knowledge
We load business information, FAQs, websites to crawl and files, then clean up whatever the agent answers badly using knowledge usage insights.
Surface 02/ 06
Brand voice and priorities
We write the agent's instructions: tone, what it prioritizes, what it must never say, and how it behaves when it does not have the answer.
Surface 03/ 06
Connectors to your systems
We declare your APIs as connectors with their tools, so the agent can look up orders, stock or availability and take real actions instead of talking about them.
Surface 04/ 06
Webhooks and events
We subscribe the message, standby and handover webhooks, and push events to the agent whenever something changes in your operation.
Surface 05/ 06
Human escalation
We implement conversation control: when your team takes over, when it releases back to the agent, and what context the person sees on arrival.
Surface 06/ 06
Testing and evaluation
Before opening it to everyone we run the test and evaluation endpoints, and launch it restricted to an allowlist of numbers.
Pick a surface to see what we configure in it
How it ends up wired
The agent lives inside WhatsApp. What decides its quality is everything behind it.
WhatsApp, on the Cloud API and the phone number of your WhatsApp Business Account.
Meta Business Agent with its knowledge, its instructions and its declared tools.
Your catalog, orders, scheduling and billing APIs, exposed as tools the agent can call.
Your team, with an inbox and CRM: multi-number, a trail of every conversation and analytics.
The message arrives on WhatsApp, the agent queries your systems and, if needed, hands over to a person.
If you do not have an operations layer yet, ours is part of the same project.
How the project runs
- 1
Eligibility and access
We check the number against the eligibility endpoint, review vertical, business verification and payment method, and set up the Meta app with its permissions.
DeliverableFeasibility report and access checklist
- 2
Agent onboarding
We onboard the agent, accept the terms, subscribe the app to your WhatsApp Business Account and get the webhooks listening.
DeliverableAgent created and webhooks live
- 3
Knowledge and voice
We load the knowledge base and write the instructions. This is where it is decided whether the agent sounds like your brand or like any other bot.
DeliverableKnowledge and instructions in production
- 4
Connectors and integrations
We declare your APIs as agent tools and validate every action end to end against real data.
DeliverableConnectors running against your systems
- 5
Testing, pilot and launch
We evaluate the agent, open it to an allowlist, measure it against real traffic, and only then release it to everyone.
DeliverableMeasured pilot and production rollout plan
Three ways to run AI on WhatsApp
There is no single right answer. There is one that fits how you operate.
Control over answers
- Meta's native agent
- Low
- Business Agent Platform, implemented
- High: your own knowledge and instructions
- Custom or BSP chatbot
- Total, but you build it
Integration with your systems
- Meta's native agent
- None
- Business Agent Platform, implemented
- Connectors to your APIs
- Custom or BSP chatbot
- Whatever you code
Human escalation
- Meta's native agent
- Manual
- Business Agent Platform, implemented
- Programmatic
- Custom or BSP chatbot
- Whatever you code
AI model cost
- Meta's native agent
- Included in Meta's token rate
- Business Agent Platform, implemented
- Included in Meta's token rate
- Custom or BSP chatbot
- Separate: your AI provider
Model maintenance
- Meta's native agent
- Meta's
- Business Agent Platform, implemented
- Meta's
- Custom or BSP chatbot
- Entirely yours
Time to production
- Meta's native agent
- Minutes
- Business Agent Platform, implemented
- 2 to 5 weeks
- Custom or BSP chatbot
- Months
Billing
- Meta's native agent
- Direct with Meta
- Business Agent Platform, implemented
- Direct with Meta
- Custom or BSP chatbot
- Marked up if it goes through a BSP
The native agent and the platform are not mutually exclusive: you can start with the first and grow into the second without rebuilding anything.
Drag the volume and watch the cost
Based on USD 2.00 per million tokens and 20,000 to 25,000 tokens per delivered message.
Estimated monthly cost
$200 – $250
- Per message
- 0.04 – 0.05 USD
- Estimated tokens
- 100 – 125 M
Indicative estimate, not a quote: real consumption depends on message length.
Open the full calculatorWhat it costs to run the agent
Meta bills the agent by tokens as of August 1, 2026, and the rate covers both AI processing and message delivery.
Token price
- Reference
- USD 2.00 per million tokens
Tokens per delivered message
- Reference
- Between 20,000 and 25,000, depending on the message
Approximate cost per message
- Reference
- Between USD 0.04 and 0.05
What the rate includes
- Reference
- AI processing and message delivery, as a single line item
From October 1, 2026
- Reference
- In-window service and utility messages become billable
Figures published by Meta and its partners, current as of September 2026. Platform pricing moves: we review the numbers with you before anything is signed.
Where it performs best
The agent earns its keep when there is a concrete task and a system to query.
Ecommerce and retail
The same questions about sizing, stock, shipping and order status, at every hour.
It queries catalog and orders live, and recommends from your actual inventory.
Appointment-based services
Bookings lost in a back-and-forth of messages.
It checks availability, books, confirms and reschedules without anyone on the team stepping in.
Education
Hundreds of identical questions about requirements, prices and dates every intake.
It answers from the official program information and passes only real candidates to admissions.
Real estate
Unfiltered leads that go cold before the first call.
It qualifies budget, area and timing, books the viewing and hands over a qualified lead.
Travel and hospitality
Availability, rates and conditions asked in several languages.
It answers with current rates and escalates to a person whenever there is an exception.
Verticals Meta does not enable today: finance, health, government, alcohol, gambling, over-the-counter drugs and matrimony services.
Security and governance
An agent that talks to your customers needs explicit limits, not good intentions.
Allowlisted pilot
We start with the agent's audience restricted to a list of numbers, so you measure real traffic without exposing your whole customer base.
Minimum necessary data
We define what the agent may ask for and what stays out of the chat. Sensitive matters are handled by a person or outside WhatsApp.
Traceability
Every conversation is logged with who replied, the agent or a person, and exactly when control changed hands.
Local compliance
Personal data handling aligned with Ley 1581 in Colombia and the LFPDPPP in Mexico, and with Meta's platform terms.
Keep reading
Everything worth knowing before switching the agent on, in detail.
Frequently asked questions
Meta opened it globally on June 3, 2026, with a gradual rollout. In LatAm it is available in Colombia, Mexico, Argentina, Chile, Peru and Uruguay; in Colombia since July 1, 2026. If your country or number is not enabled yet, you can join the waitlist and prepare everything else in the meantime.
Yes. Spanish is among the supported languages, alongside Portuguese and others. Not every language is available yet, so if you operate in several it is worth validating coverage before promising it.
Not necessarily. The agent runs on the WhatsApp Cloud API; what changes is who replies first. The agent handles the conversation while your app stays in standby, ready to take control. What you do have to decide is which messaging product runs on each number.
Yes, if it is eligible. The real constraint is that a single number cannot run several messaging products at once, so coexistence with your current inbox or integration has to be planned before switching it on.
Meta charges USD 2.00 per million tokens as of August 1, 2026. A message consumes between 20,000 and 25,000 tokens, which lands between USD 0.04 and 0.05 per delivered message, delivery included. On top of that there is the one-off implementation cost.
Meta does not enable the agent for finance, health, government, alcohol, gambling, over-the-counter drugs or matrimony services. In those cases the answer is a custom agent on the WhatsApp API, which we also implement.
Whenever you decide. Your app can take thread control on specific events, or simply by sending a message, and release it back to the agent once the case is closed. Every control change arrives by webhook, so it is all on record.
Yes. You load an allowlist of numbers and set the agent's audience to allowlisted only, so just those contacts talk to it. It is the sane way to measure before opening it to your whole base.
Two to five weeks, depending on how many systems need connecting and what state their APIs are in. Eligibility and onboarding take days; the real time goes into integrating and testing.
Yes. The agent can be switched off and conversations go back to your usual operation. That is why we recommend starting with an allowlist: the risk of the pilot stays contained from day one.
That tab only appears if the number is eligible. The first step is querying the eligibility endpoint and reviewing country, vertical, business verification and the payment method in the Billing Hub: with no active payment method, messages are not delivered.
The app gives you an agent that answers from your public business information. The platform lets you load your own knowledge, define its voice, connect it to your systems, control human escalation and evaluate it before it ever talks to a real customer.
Shall we wire it into your WhatsApp?
We start by checking whether your number and vertical are eligible. If they are not, you hear it in the first conversation and nobody wastes their time.
Implement Meta Business Agent
We reply on WhatsApp