The practical choice depends on who performs the work. A team answering directly can use the app. Software-triggered workflows need the Platform API.

## What is the WhatsApp Business app for?

The [WhatsApp Business app](https://business.whatsapp.com/products/business-app) is built around direct conversation handling on a supported device. It suits a small team that can answer customers from the app. It does not require application-controlled delivery events.

Use it for a business profile, manual replies, simple customer conversations and a human workflow that fits the app's device model.

## What is the WhatsApp Business Platform API for?

The [WhatsApp Business Platform](https://business.whatsapp.com/products/business-platform) connects WhatsApp to software. Your application or provider can submit messages, receive webhooks, manage templates and route conversations into an inbox or helpdesk.

An API integration also makes you responsible for credential storage, retries, delivery-state handling, customer permission and policy-compliant templates. A successful API response still does not prove delivery.

## Which workflow belongs on each surface?

| Need                                      | Better fit   | Why                                                   |
| ----------------------------------------- | ------------ | ----------------------------------------------------- |
| A person answers from one device          | Business app | The conversation stays in the app workflow            |
| A form triggers an order update           | Platform API | Software can send a template and store the message ID |
| A team needs an existing inbox            | Platform API | Webhooks can route inbound and delivery events        |
| A small team tests demand manually        | Business app | No integration project is needed first                |
| A service needs retries and audit history | Platform API | Your application can own state and recovery           |

The choice is about operating model, not only message volume. A small business can need the API if software must perform the work. A larger team can still use the app for a narrow manual queue.

## What should I check before moving to the API?

Confirm the business portfolio, WhatsApp Business Account, number ownership and provider connection path. [Embedded Signup](/explained/whatsapp/how-does-whatsapp-embedded-signup-work) can connect those assets. The flow does not prove that verification and sending are complete.

Keep the same policy obligations after the move. You still need [WhatsApp opt-in](/explained/whatsapp/what-is-whatsapp-opt-in), approved templates outside the [24-hour service window](/explained/whatsapp/what-is-the-24-hour-customer-service-window) and a recovery plan for failed or rejected sends.

## How do I choose an API provider?

Compare account ownership, Embedded Signup support, template operations, delivery events, message costs and migration terms. Keep Meta's published pricing separate from the provider's own fees.

1. Use the app when people answer directly from a supported device.
2. Use the Platform API when software must send, receive or measure messages.
3. If you choose the API, compare providers with [the provider checklist](/explained/whatsapp/how-do-i-choose-a-whatsapp-business-api-provider) and confirm number and account ownership before switching.

## Related resources

- [WhatsApp](/products/whatsapp) (product)
- [Sending WhatsApp messages](/docs/guides/whatsapp/sending-whatsapp) (docs)
- [Connecting WhatsApp to Bird: from buying a number to a live channel](/learn/whatsapp/connecting-whatsapp-to-bird) (video)
- [WhatsApp message builder](/tools/whatsapp-message-builder) (tool)

[Get an implementation brief](/learn/workspace?topic=whatsapp)