WhatsApp Business App vs API: Key Differences and When to Switch

Most businesses start on WhatsApp the same way: someone installs the WhatsApp Business app on a phone, adds the logo and business hours, and starts replying. That works until three people need to answer the same number and someone asks why you can't send a reminder to a lead who messaged last week.

That's when the question comes up: stay on the app or move to Meta's official API? This article covers what each one does, what Meta requires on the API (the 24-hour window, message templates, per-message pricing, verification and messaging limits) and when switching makes sense.

If you're still building your sales process on WhatsApp, start with the complete guide to selling on WhatsApp and come back here for the technical side.

Three routes, not two

In practice, a business can use WhatsApp in three ways:

1. The WhatsApp Business app, installed on a phone. Meta describes it as the option for small businesses to communicate with customers from a single device: free, with limited customization and integrations.
2. The WhatsApp Business Platform, which everyone calls "the API." According to Meta, it enables medium and large businesses to chat with customers at scale. It includes the Cloud API, hosted by Meta.
3. A QR code connection to a CRM, where the platform links to the WhatsApp on your phone as another device. It isn't an official Meta product, but plenty of teams use it to bring WhatsApp into their sales pipeline before moving to the API.

The rules of one don't apply to the others. The 24-hour window, for example, is an API rule.

What the WhatsApp Business app does well

The app does more than people expect. On its features page, Meta lists:

• A catalog of products and services you can share in chats.
• Labels to organize and filter conversations.
• Quick replies for messages you send often.
• An away message for after hours and a greeting message for new contacts.
• A business profile with description, hours, address and website.
• Linked devices: with a Meta Verified subscription, Meta says you can link up to 10 devices and agents to the account.

For one or two people handling chats, that's enough. What's missing is a sales pipeline, customer records with history, reporting, and automation beyond the away message.

What the WhatsApp Business Platform (Cloud API) is

The Platform has no chat screen of its own. It's a technical connection that software (a CRM, for example) uses to send and receive messages. Meta offers two ways to get started: through a partner, if you don't want to manage the API yourself, or a direct integration, if you have developers.

What you get:

• Multiple agents working the same number from the software of your choice.
• Integration with the rest of your stack: CRM, calendar, billing, AI agents.
• Proactive messaging (confirmations, reminders, campaigns) through approved templates.
• A verified profile and the option to apply for the official business account badge.

In return, you take on opt-in rules, message templates, messaging limits and a per-message cost.

The 24-hour customer service window

This is the rule that trips up most newcomers to the API. When a customer messages you, a 24-hour customer service window opens. Inside it you can reply with regular messages (text, images, files), and Meta says these non-template messages are free and can only be sent within an open window. Each new message from the customer resets the clock.

Once the window closes, the only way to reach that person again is an approved template. Meta's documentation is explicit: templates are the only type of message that can be sent outside a customer service window.

There's a useful exception if you run ads. When a customer arrives from a Click to WhatsApp ad or a Facebook Page call-to-action button, a free entry point window opens, and Meta says it stays open for 72 hours, during which messages aren't charged.

Message templates and the three categories

A template is a message with a fixed structure and variable fields (name, date, order number) that Meta reviews before you can use it. Review happens automatically when you create or edit a template, and only templates with approved status can be sent. Meta also gives each template a quality rating based on usage and customer feedback; a paused or disabled template can no longer be sent.

Every template has to fall into one of three categories:

The category affects the price, and Meta checks it: if you label a promotional-sounding template as utility, it can be recategorized as marketing. Keep utility templates free of discounts, "don't miss out" and calls to buy.

Before you send anything, Meta requires opt-in: people must know they're agreeing to receive messages, and from which business. Meta also expects your opt-in to comply with the laws that apply to you. For copy ideas, see our WhatsApp sales message templates.

How Meta charges for the API: per message

Since July 1, 2025, Meta charges per message rather than per conversation. In short:

• You only pay when a template is delivered.
• The price depends on the category and the recipient's country.
• Marketing templates are charged (except inside a free entry point window).
• Utility templates sent while the customer service window is open are free.
• Regular replies inside the 24-hour window aren't charged.
• Utility and authentication have volume tiers: the more you send in a month, the lower the unit rate.

We don't list prices here because they change and vary by market. Check Meta's official pricing page, which has rate cards by currency and market.

Hypothetical example: if your clinic sends 300 reminders a month to patients who haven't messaged in the last 24 hours, that's 300 billable utility templates. If the patient wrote the day before, the reminder isn't charged.

Verification, display name and messaging limits

When you register a number on the API, you must provide a display name, which Meta reviews against its naming guidelines.

Next come messaging limits. They cap how many unique numbers you can message outside a customer service window in a rolling 24-hour period, and they apply to the whole business portfolio, not to each number. According to the messaging limits documentation:

• A new portfolio starts with a limit of 250.
• To reach 2,000 there are three paths: verify your business, have the partner that onboarded you verify it, or deliver 2,000 messages outside the window to unique numbers within 30 days using high-quality templates.
• After that, the limit scales automatically (10,000, 100,000, unlimited) if quality is high and you've used at least half your limit in the last 7 days.

The blue official business account badge is a separate step. Meta requires, among other things, a verified business, at least 30 days on the platform, two-step verification turned on and an approved display name. Meta doesn't grant this status to WhatsApp Business app numbers.

App, QR code or API: comparison table

QR code connection in a CRM vs the official API

In Elooo CRM, the QR code connection is included in every plan. You scan the code with your phone, just like WhatsApp Web, and conversations land in the multichannel inbox, tied to the contact and the deal in your pipeline. We don't charge anything per message on this connection.

What to know before you pick this route:

• It depends on the phone. If the device runs out of battery, loses internet, or the WhatsApp session is logged out, the connection drops until it's back.
• It isn't an official Meta product. Meta may restrict numbers that break its rules, especially bulk messages to people who didn't ask for them.
• It's built for conversations, not for blasting campaigns to large lists.

The official WhatsApp API is part of the Enterprise plan, and we handle the setup: account, number, display name, templates and the CRM connection. API messages follow Meta's rate card and are billed separately from the plan price. Compare plans under plans and pricing.

When to switch: a practical checklist

Ask yourself these questions. If you answer "yes" to two or more, it's time to move off the app.

• Do several people need to answer the same number at the same time?
• Are you losing context because chats aren't tied to a customer record or a deal?
• Do you want to automate replies, routing or follow-ups, or connect an AI agent?
• Do you need to send confirmations and reminders to people who haven't messaged in the last 24 hours?
• Is WhatsApp business-critical, so it can't depend on a phone being on?
• Do you need reports on response time and conversion by rep?

If only the first three are "yes," a CRM with a QR code connection usually does the job. If proactive messaging, reliability and scale matter more, the API is the way to go.

Common mistakes when switching

• Migrating without a plan for the number. Moving a number to the API changes how it works in the app. Meta's coexistence mode keeps the app and Cloud API on the same number, but turns off some app features, such as creating new broadcast lists. Confirm with your provider first.
• Writing utility templates that read like marketing. They get recategorized and billed as marketing.
• Skipping opt-in. Importing an old list and firing off templates is the fastest way to tank your quality rating and stall your limits.
• Using the QR code connection for bulk sends. It's for conversations, not cold lists.

The choice isn't permanent. A common path is to start on the app, move to a CRM with a QR code connection as the team grows, and go to the API once volume justifies it.

Tags: #whatsapp business #whatsapp api #cloud api #message templates #crm

Share