Plugin Pros

WhatsApp Business App vs Cloud API: Which One Does Your WordPress Site Need?

Lukas Becker

Comparison of a phone chat app and a shared Cloud API inbox for WordPress.

If you are comparing the WhatsApp Business API vs app for a WordPress site, start here. They can share one phone number. But they do very different jobs.

Many sites already show a WhatsApp icon. A visitor taps it, and WhatsApp opens on their phone. Then the message reaches whoever holds the business handset that day.

That setup can work for a one-person shop. It gets harder when a second person needs the same number. It also falls short if you want the chat inside WordPress, not only on a phone.

This guide is for site owners. It is not a partner setup manual.

Quick answer

Use the WhatsApp Business app and a site button if one person already answers on a phone. Use the Cloud API if your team needs a shared inbox in WordPress, or if you need templates and automations.

  • A chat button only opens WhatsApp. It does not connect the API.
  • Meta does not charge Cloud API rates for ordinary chats in the Business app.
  • One number can stay on the Business app and the API only through Meta’s coexistence flow.

Three things people often mix up

People often treat a button, the phone app, and the API as one product. In fact, they are three layers. So it helps to separate them first.

The click-to-chat button

A click-to-chat button is only a shortcut. It opens WhatsApp with your number already filled in.

It does not connect any API. It also does not copy the chat into WordPress. If you only added a floating button, you still answer in the app on the phone.

The WhatsApp Business app

The WhatsApp Business app is the free app you run on a phone. You can also use it on linked devices, with limits.

You read and type as a person using that account. The app also has greeting messages, away messages, and quick replies. It is built around one business account, and the people who can reach that phone.

The WhatsApp Cloud API

The WhatsApp Cloud API is part of the WhatsApp Business Platform. It is a software connection.

A shared inbox, a help desk, or a WordPress plugin can then send and receive on the business number. The chat no longer has to live only on the phone that registered it. Choose this if the conversation should appear in wp-admin.

When the phone app is still the right choice

Keep the Business app, and keep a button on the site, when all of these are true:

  • One person already answers promptly from a phone.
  • Nobody else needs the same thread.
  • You do not need to store the chat inside WordPress.

In that case, you avoid API setup and webhook upkeep. You also avoid Meta’s platform message charges for ordinary manual chats in the app.

Still, this path can get uncomfortable. For example:

  • A colleague asks for the PIN to “just check one chat.”
  • Nights and weekends depend on whoever has the handset.
  • A lost or replaced phone can take the history with it.

Linked devices can ease a little pressure. However, they still belong to one WhatsApp account. They are not the same as two WordPress users logging into a shared inbox.

When a WordPress site needs the Cloud API

Choose the Cloud API when at least one of these is true:

  • More than one person must reply on the same number.
  • You want a chat record that stays with the site.
  • You need tools the phone app cannot run reliably.

Those tools include approved templates and scripted follow-ups. They also include a webhook that tells WordPress a customer just wrote in.

The API only makes the number usable by software. You still pick an inbox, or you build a handler.

If deliveries never arrive, the number can be registered and the site will still look quiet. That problem has its own walk-through in WhatsApp Cloud API webhook verified but no messages.

WhatsApp Business API vs app: a quick comparison

Use this table as a short decision guide. Then read the cost and number-sharing notes below.

Your questionBusiness app or buttonCloud API
Can one person answer from a phone?Yes. This is the natural fit.Possible, but usually more than you need.
Can a small team share one number?Only through one account and linked devices.Yes, in software both people can open.
Will WordPress store the chat?No. It stays in the app.Yes, if you connect an inbox.
Do I only need a chat button?Yes. A button is enough.No. Use the API when software must read the thread.
Can I send templates or bulk notices?Only with the app’s manual tools.Yes, under Meta’s current rules and pricing.
Can the number stay in the phone app?Yes. That is the default.Only through Meta’s coexistence onboarding.

What you pay, and what you should not guess

The Business app and a site button

Installing the WhatsApp Business app does not start a Cloud API bill. Manual chats you type in that app are not priced like platform messages. Your mobile plan still works in the usual way.

A button plugin on WordPress may be free or paid. Even so, Meta does not treat a link that only opens WhatsApp as API traffic.

Cloud API message charges

Once the number is on the WhatsApp Business Platform, Meta bills per message. It does not bill per conversation. The older conversation model ended on 1 July 2025.

Meta charges when a business-to-user message is delivered. The amount depends on the category and on the customer’s market. The categories are marketing, utility, authentication, and service.

Meta does not charge for messages customers send to you.

Some outbound messages can still be free. For example, Meta currently documents certain utility replies as free.

There is also a 72-hour window. It can start after someone writes from a Click to WhatsApp ad. It can also start after someone writes from a Facebook Page button.

Those exceptions can change, and so can the rates. Blog posts that still promise “1,000 free conversations a month” describe the old model. So look up the live rate for your market, instead of copying a figure from last year:

A plugin or solution partner may also charge for software. That fee is separate from Meta’s message charges.

Category rules are not frozen either. Therefore, check the official pages again when you plan a campaign.

Can the same number stay on the app and the API?

For years, the usual advice was that a number could live in only one place. That advice is still right in some cases. However, it is now incomplete in one official case.

If the number is on regular WhatsApp

Regular WhatsApp is the consumer app, not the Business app. In that case, you typically have to delete the WhatsApp account first. Only then can you register the number on the Business Platform.

That deletion is a real trade-off. The consumer chat history goes with the account.

If the number is already on the Business app

If the number is already in the WhatsApp Business app, Meta now supports a special onboarding path. Partners usually call this coexistence.

After that flow succeeds, the team can keep one-to-one chats in the Business app. The team can also use the Cloud API from software. History can stay in sync.

You need WhatsApp Business app version 2.24.17 or later. The option normally appears during Embedded Signup.

A Tech Provider or Solution Partner usually offers it. It is not a hidden toggle on the phone by itself.

Read the limits before you rely on this:

  • A number used in both places is capped at 20 messages per second.
  • Chats you send from the Business app stay free.
  • Chats you send through the API follow API pricing.
  • The API’s 24-hour customer service window does not start or grow when you type in the app.
  • After the connection, Meta turns off disappearing messages, view-once messages, and live location in one-to-one chats. It also disables broadcast lists.

If you skip coexistence

If you register the number on the Cloud API in the ordinary way, you skip that coexistence flow. Then you generally cannot keep using the number in the WhatsApp Business app.

And if you only wanted a button on the website, you do not need to move the number at all. Do not delete a Business app account just to “free” a line you still want to use in the app. That is the wrong first step when coexistence is available.

Choose a path before you touch the number

If one person already handles WhatsApp on a phone, stay with the app. Also stay if a button on the site is already doing its job.

If the team needs a shared view, a record in WordPress, or platform templates, plan an API connection. Then ask early whether your plugin or partner can run the coexistence flow. Ask this if you still need the phone app on the same line.

Some site owners have already outgrown the button. They want WhatsApp in WordPress, next to the site’s other channels. In that case, a shared inbox can help more than a second widget.

This multi-channel inbox overview describes that approach. Kinetix Messaging is a free WordPress plugin. It can hold WhatsApp together with Messenger, Instagram DM, Telegram, and live chat in wp-admin.

Whatever tool you pick, use a System User access token for the API connection. Then a trial credential will not drop out after the first day.

Frequently asked questions

Can I keep the click-to-chat button after I connect the Cloud API?

Yes. The button still helps a visitor start a chat. The API only changes where your team can read and reply.

Some sites keep both. They use a button on the front end, and an inbox in wp-admin.

Does Meta charge me for using the WhatsApp Business app?

Not with Cloud API message rates. The app is free to install. Meta does not bill ordinary manual chats in the app as platform messages.

Charges start when you send through the WhatsApp Business Platform. Meta then uses the current per-message rate for that category and market.

My number is on regular WhatsApp, not the Business app. Can I just turn on the API?

Usually not. You typically have to free the number first. That means deleting the consumer WhatsApp account on that line.

Coexistence is for the WhatsApp Business app. Therefore, confirm the official migration steps before you wipe an account you still need.

Do I need an in-house developer to use the Cloud API on WordPress?

You need an integration that can talk to Meta and receive webhooks. That can be a plugin or a partner. You do not have to write the API client yourself.

You do need to prepare for setup details, though. Those include tokens, a public HTTPS callback, and Meta’s pricing pages.

Official documentation