WhatsApp Business API in Colombia: Pricing and Setup

What is the difference between the WhatsApp Business app and the API?

The app is for answering by hand from a phone; the API connects WhatsApp to your software and to several agents at once.

The WhatsApp Business app is the free app you install on a phone to answer customers by hand: catalog, quick replies, labels. The WhatsApp Business API, which Meta now groups under the WhatsApp Business Platform, is not an app but a connection for software. It lets a CRM, an AI agent or an automation send and receive messages, lets several people answer from the same number, and keeps every conversation on record.

The difference that hits your wallet is billing. The app doesn’t charge per message. The API charges for each message the business delivers, by category, and in exchange does things the app can’t: automatic order notifications, support at scale without depending on one phone, and measurement and integration with your systems.

One thing has changed that many articles haven’t caught up with: you no longer always have to choose. Meta lets you connect a number you already use in the WhatsApp Business app to the API without giving up the app, a feature support channels call coexistence. It has to be set up through an authorized provider, requires app version 2.24.17 or later, and has a fixed throughput of 20 messages per second. Messages sent from the app stay free; messages sent through the API are billed at platform rates.

How much does the WhatsApp Business API cost in Colombia? (per-message rates)

Marketing is the only expensive category; utility, authentication and service cost less than a tenth of a US cent.

In Colombia, the WhatsApp API costs USD 0.0125 (COP 46.02) per marketing message and USD 0.0008 (COP 2.95) per utility, authentication or service message, according to Meta’s rates effective October 1, 2026. Meta only charges when a message is delivered, only for messages the business sends, and based on the recipient’s country code: message a +57 number and Colombia’s rate applies, even if your company is based elsewhere.

Since April 1, 2026 you can be billed in Colombian pesos. Currency is chosen when the messaging account is created and can’t be changed afterwards without a migration process, so it is worth deciding up front. These are the rates we pulled from Meta’s official rate tool on October 26, 2026:

How do you activate it: direct Cloud API or a provider (BSP)?

Going direct means paying only Meta but owning the technical work; a provider charges for its platform and saves you the integration.

There are two ways to activate the WhatsApp API. The first is the direct Cloud API: you create an app in Meta for Developers, link it to your business portfolio, register the number and pay Meta only for messages. The second is through a solution provider, what the market usually calls a BSP: the provider gives you an inbox, templates and support, and charges for its platform on top of Meta’s message fees.

Going direct makes sense if you have someone to build and maintain the integration, or if you are connecting it to a CRM or n8n anyway. A provider makes sense if your team needs an inbox from day one and you don’t want development work. When comparing quotes, always ask them to separate Meta’s fees from the provider’s charge; if they won’t, you don’t know what you are paying for the service.

Whichever route you take, the steps are the same:

• Have a Meta business portfolio (Business Manager) in the company’s name.
• Pick the number: a new one, one migrated from regular WhatsApp, or a WhatsApp Business app number connected through coexistence.
• Set the business display name following Meta’s guidelines; Meta verifies it once the account moves up a messaging limit.
• Add a payment method in Meta’s Billing Hub; without one, Meta stops delivering service messages once the 1,000 free ones run out.
• Verify the business to raise your sending limit: a new account can message 250 unique users a day outside the service window, and verification lifts that to 2,000.
• Create and get your first templates approved before launching any outbound send.

Which templates does Meta approve, and which does it reject?

If a template mixes useful information with an offer, Meta bills it as marketing.

Meta approves templates whose content matches the category you declare, and recategorizes or rejects the ones that don’t. A template is the only way to message a customer who hasn’t written to you in the last 24 hours. Inside that customer service window you can reply freely; outside it, only approved templates are allowed.

To qualify as utility, a template has to meet two conditions: no promotional intent, and it must relate to something specific to the user, such as their order, account or payment, or be critical to them. “Your order 1234 shipped today and arrives Thursday” is utility. “Your order shipped; use code COMEBACK10 on your next purchase” is marketing, because Meta’s guidelines classify any mixed content as marketing. Vague templates, such as a bare “Congratulations!” or one that contains nothing but a variable, are marketing too.

Since April 9, 2025, if you submit a template as utility and Meta decides it is marketing, it gets approved as marketing, at the marketing rate. Meta also periodically reviews approved templates and can change their category with one day’s notice, or with no notice if the account has been warned for misuse. Authentication templates are the strictest: they must use Meta’s template library, include a one-time-code button, and cannot contain links, media or emojis.

In practice, our rule is to keep them apart: one message to inform and, if needed, a separate one to sell. Doing it properly takes more work than mixing them, but in Colombia the difference is USD 0.0008 versus 0.0125 per message.

How do you connect WhatsApp to your CRM?

A WhatsApp CRM is useful when every conversation creates or updates a contact with context, not when it just copies messages.

There are three ways to connect WhatsApp to a CRM: the native connector some CRMs offer, a provider that syncs conversations into the CRM, or a custom integration built on the Cloud API and its webhooks, with a tool like n8n in the middle. All three work; the difference is how much control you have over which data goes where.

What needs designing isn’t the cable but the rules. Which conversation creates a new contact and which updates an existing one. Which label it gets based on the reason for contact. Who it is assigned to and how fast they must respond. And which CRM events trigger a utility template, such as a quote sent or a payment confirmed. A badly designed WhatsApp CRM ends up as a second inbox nobody checks.

One technical detail to review with whoever implements it: Meta’s status webhooks report each message’s category and billing type. Storing that in the CRM tells you what each customer or campaign actually costs, instead of finding out from the invoice at the end of the month.

When does it make sense to add an AI agent to WhatsApp?

Add an agent once repetitive questions are eating hours of your team’s time and your knowledge base is written down.

Adding an AI agent makes sense once the API is running, repetitive messages take up a good part of someone’s day, and the information the agent should use is written down: prices, hours, policies, catalog. Without that, the agent will just give wrong answers quickly. Our article on AI agents for WhatsApp Business covers how to design the script and when to hand off to a person.

Since July 2026 there is a new variable in the math. Meta launched Meta Business Agent, its own agent for the platform, priced at USD 2 per million tokens, which Meta estimates at roughly 4 to 5 US cents per message. The alternative is your own or a third-party agent: you pay the Colombian service message rate, after the 1,000 free ones each month, plus the usage of whichever AI model you choose. Which one comes out ahead depends on volume, how complex the answers are, and how much control you need over data and CRM integrations.

Two caveats. WhatsApp’s terms, updated on January 15, 2026, restrict providers offering general-purpose AI assistants; an agent that answers questions about your own business is a different case, but its scope should be clear. And customers should know they are talking to an assistant: hiding it costs more trust than it saves.