WhatsApp has come a long way since it was introduced back in 2009.
What started as a personal chat app is now one of the most-used business messaging channels globally, and the numbers certainly support this.
Today, more than 200 million businesses actively use WhatsApp Business each month and around 175 million people message a business account every day.
For enterprise and government organisations, this means not being on WhatsApp in some capacity is almost certainly missing a trick.
So, for those keen to start messaging customers, citizens, patients — or even employees — via WhatsApp, the first step requires setting up a WhatsApp business account.
This process may sound simple, but early decisions like choosing the right account type, preparing the right number and meeting compliance requirements, can determine future success and scalability.
This guide will walk you through both setup paths (app and API) with organisations of all different shapes and sizes in mind.
App or API – Which Is Best for Your Business?
Before getting into the practical setup steps, there’s one decision that shapes everything that follows: do you go with the WhatsApp Business app, or the WhatsApp Business API?
The app is free, quick to download and works well for smaller teams running a pilot, handling a low volume of customer conversations, or testing the channel before committing to a wider rollout.
The API plays a different role. It’s more suited to organisations that need multiple agents working from a shared inbox, integration with a CRM or service desk, automation and chatbots, and a clear audit trail of every message sent and received.
This is as much a governance and architecture decision as a technical one, which is why getting it wrong tends to be expensive.
Choosing the app when your rollout actually needs the API often means rebuilding the setup further down the line, migrating numbers, re-verifying with Meta, and explaining to the business why the project has slipped.
The table below breaks down the practical differences between the two, so the right call can be made before any setup screens are touched.
WhatsApp Business App vs API Comparison
| Feature | WhatsApp Business App | WhatsApp Business API | Enterprise relevance |
|---|---|---|---|
| Setup process | Downloaded from the App Store or Google Play, registered with a business phone number | Provisioned through a Meta-authorised Business Solution Provider (BSP) or directly via Meta’s Cloud API, with a verified Meta Business Account and WhatsApp Business Account (WABA) required | Determines whether IT, security and procurement are involved from day one |
| Setup timeline | Live within minutes | Typically several days to a few weeks, depending on Meta Business Verification and BSP onboarding | Needs to be built into project planning, not treated as a quick deployment |
| Number of users supported | Up to 5 devices (1 primary phone plus 4 linked), or up to 10 with a Meta Verified subscription | Unlimited agents working from a shared inbox | The single biggest ceiling for any team beyond a handful of people |
| CRM and system integrations | Not supported | Native integration with CRMs, service desks, ticketing systems and internal platforms via REST API and webhooks | Essential for any organisation routing WhatsApp into existing customer or case management workflows |
| Automation capability | Basic automation only, limited to greeting messages, away messages and quick replies | Full chatbot, AI agent, message template and workflow automation | Decides whether WhatsApp can scale beyond manually typed responses |
| Audit trail and compliance | No audit trail, no message logging, no role-based access | Full conversation history, role-based access, opt-in management and message template approval workflow | Critical for regulated sectors and any organisation with internal data governance requirements |
| Verification path | Optional Meta Verified subscription for the blue tick badge | Eligible for the official green tick (Official Business Account) once on the API with a verified business profile | Affects brand trust and how customers perceive inbound messages |
| Ideal for | Sole traders, small teams and pilot deployments | Mid-sized to large enterprises and government organisations running customer messaging at scale | Sets the expectation of who each path is actually built for |
| Key restriction | Manual operation, no API access, no integrations | Requires a BSP relationship or direct Cloud API development resource | Helps frame the trade-off between speed-to-launch and long-term scalability |
WhatsApp Business App
The WhatsApp Business app is the entry-level option, downloaded straight from the App Store or Google Play and tied to a single business phone number.
It’s free, quick to register and useful for sole traders, small teams or organisations testing the channel before committing to a wider rollout.
The app does come with built-in features for setting up a WhatsApp Business profile, adding a catalogue, and using greeting messages, away messages and quick replies.
Where it tends to hit a ceiling is volume and access. Up to 5 devices can be linked (10 with a Meta Verified subscription), and there’s no way to integrate with a CRM, log conversations centrally, or give multiple agents proper role-based access.
For most enterprise and government rollouts, the app works as a useful proof of concept rather than the long-term home for customer messaging.
WhatsApp Business API
The WhatsApp Business API is the path built for scale.
Rather than a downloadable app, it’s provisioned through a Business Solution Provider (BSP) or directly via Meta’s Cloud API, and connects WhatsApp into the systems an organisation already runs on, including CRMs, service desks, ticketing platforms and chatbot frameworks.
A shared team inbox can support an unlimited number of agents, conversations are logged end-to-end, and message templates go through Meta’s formal approval process before being sent at volume.
Setup takes longer. Meta Business Verification, BSP onboarding and template approvals typically run from a few days to a few weeks, depending on how prepared the business documentation is.
For organisations with compliance obligations, multi-team rollouts or any plans to automate, the API is realistically the only viable starting point.
Prerequisites Before You Begin
Most setup delays don’t happen during setup, they happen because something wasn’t ready before it started.
Three things need to be in place before going down either the app or the API path.
- A dedicated phone number
- Business documentation
- A Meta Business Manager account
For organisations in regulated sectors, the documentation step is usually where things stall. Legal, compliance and procurement teams tend to need a heads-up well before the application goes in, not after Meta has come back asking for more information.
The table below covers which number types are supported, and which aren’t.
Supported and Unsupported Phone Numbers for WhatsApp Business
| Number type | Supported | Verification method | Notes |
|---|---|---|---|
| Mobile number | Yes | SMS or voice call | Most common option, must be dedicated to WhatsApp Business and not already linked to a personal WhatsApp account |
| Landline (fixed) | Yes | Voice call only | A practical option for organisations with established fixed office lines that prefer not to introduce a new mobile number |
| VoIP number | Not supported | N/A | Numbers from VoIP providers cannot reliably receive WhatsApp’s verification code and are not accepted |
| Toll-free number | Not supported | N/A | Not eligible for WhatsApp Business verification, regardless of region |
| Number already on personal WhatsApp | Not without action | SMS or voice call once released | The number must first be deleted from the personal WhatsApp account, or ported through Meta’s number migration process |
Phone Number Requirements
The phone number used for WhatsApp Business needs to be dedicated to the account, meaning it can’t already be active on a personal WhatsApp account at the time of registration.
It also needs to be able to receive WhatsApp’s verification code, either by SMS or voice call.
Mobile numbers are the most common choice, but landlines are also supported through the voice call option, which can suit organisations that prefer to use an established fixed office line rather than introduce a new mobile.
VoIP and toll-free numbers aren’t accepted for verification.
Business Documentation and Meta Business Manager
A verified Meta Business Manager account is required for the API path. It acts as the central hub for managing WhatsApp Business Accounts, payment methods, message templates and user permissions across an organisation.
Before submitting for verification, it’s worth having the registered business name, business address, official website and any relevant trading or tax registration details ready to go.
Meta’s review process checks this information against publicly verifiable sources, so any mismatch between the business name on the application and what appears on the website or official registries tends to slow things down.
How to Set Up a WhatsApp Business Account Using the App
The app path is the more straightforward of the two, designed to get a business up and running on WhatsApp in minutes.
- Download the WhatsApp Business app from the App Store or Google Play.
- Enter the dedicated business phone number and select the verification method, either SMS or voice call.
- Receive and enter the six-digit code to confirm ownership of the number.
- Build out the business profile, including business name, category, description, address, website and hours.
- Configure messaging tools, such as the greeting message, away message and quick replies, before going live with customers.
Standard carrier charges may apply when receiving the verification code, depending on the mobile or landline provider being used.
The whole process generally takes less than 15 minutes, assuming the number is ready and not already linked to a personal WhatsApp account.
How to Set Up WhatsApp Business API for Enterprise Rollout
The API path involves more steps, more stakeholders and more lead time, but it’s the route that supports a serious customer messaging operation.
- Select a Business Solution Provider (BSP). The BSP acts as the technical intermediary between the organisation and Meta, handling API access, infrastructure and ongoing support. Choosing one with enterprise SLAs and the right regional footprint matters, particularly for organisations operating across multiple markets.
- Connect a Meta Business Manager account. The BSP will link this to a WhatsApp Business Account (WABA) and request API access through Meta.
- Submit for Meta Business Verification. This is where the registered business name, address, website and documentation come into play, and where most delays happen if anything’s inconsistent.
- Configure the API. Once approved, the BSP supports the technical integration, message template setup and connection into existing systems, including any CRM, service desk or chatbot platform already in use.
Timelines vary from a few days to a few weeks depending on Meta’s review and how prepared the documentation is, so it’s worth building this into project planning rather than treating it as a quick deployment.
For a closer look at the platform itself, see Soprano’s guide to using WhatsApp for business communication.
Compliance Considerations for Regulated Industries
For organisations in finance, healthcare, government, logistics and similar sectors, compliance is usually the deciding factor in how WhatsApp Business gets deployed, and which path makes sense.
Three areas tend to come up in internal reviews.
- Opt-in and consent. Every customer or citizen receiving a business-initiated message on WhatsApp needs to have given clear opt-in, and that consent has to be captured, stored and easy to evidence if regulators ask.
- Data residency and retention. Where conversation data is stored, how long it’s kept and who has access to it are common sticking points for legal and security teams, particularly in sectors with sector-specific rules around customer data handling.
- Audit trails. A full, exportable record of who sent what, when, and to whom, is usually a baseline requirement for any regulated rollout, and only the API path supports it.
The app, on its own, rarely meets the threshold for a regulated environment. It can work as an internal pilot, but the API is generally the only viable path for production use in sectors where messaging needs to stand up to audit.
| Example — Healthcare Organisation Moving from App to API |
|
A regional healthcare provider with a small communications team initially set up the WhatsApp Business app using a dedicated landline, verified via call, to handle inbound patient queries. As volume grew and compliance requirements around message logging and opt-in consent became a priority, the provider engaged a BSP to migrate to the WhatsApp Business API, enabling CRM integration, automated triage workflows and a full audit trail for regulatory reporting. |
FAQs
What Is the Difference Between the WhatsApp Business App and the WhatsApp Business API?
The WhatsApp Business app is a standalone mobile tool, free to download and best suited to sole traders, small teams or pilot deployments.
The WhatsApp Business API is built for scale, supporting multiple agents working from a shared inbox, CRM and system integrations, automation, and a full audit trail of every conversation.
Can Australian Businesses Use a Landline Number for WhatsApp Business?
Yes. Landline numbers are supported for WhatsApp Business verification through the voice call option, with the six-digit verification code delivered directly to the fixed line rather than by SMS, which suits organisations using established office numbers.
How Long Does WhatsApp Business API Approval Take?
Approval generally takes anywhere from a few days to a few weeks, depending on how quickly Meta’s Business Verification process moves and how complete the submitted documentation is.
Working with a Business Solution Provider that handles the BSP-side onboarding in parallel can help shorten the overall timeline.
What Compliance Requirements Apply to WhatsApp Business in Regulated Industries?
Regulated sectors like healthcare, finance and government need to think through opt-in and consent management, message retention, data residency, and the ability to produce a full audit trail of customer conversations.
The app doesn’t typically meet these requirements, which is why most regulated organisations deploy WhatsApp Business through the API.
Do I Need a Meta Business Manager Account to Set Up WhatsApp Business?
A Meta Business Manager account is required for the API path but isn’t strictly needed for the standalone app.
For the API, the account must be verified by Meta before access is granted, which is why it’s worth setting up and verifying it early in the process.
How Do I Get the WhatsApp Green Tick for My Business Account?
The green tick is a verification badge granted by Meta to authentic, notable businesses, and it signals to customers that the account they’re messaging is legitimate.
Eligibility requires a complete business profile and an active WhatsApp Business API account. For a full breakdown, see Soprano’s WhatsApp green tick verification guide.
Getting Started With WhatsApp Business
Most enterprise and government rollouts start the same way, with a team that knows WhatsApp needs to be part of the customer mix but isn’t quite sure how to set it up properly the first time.
Soprano works with organisations as a Meta Business Solution Provider, supporting WABA setup, Meta Business Verification, CRM integration, template approvals and ongoing platform support.
If a WhatsApp Business rollout is on your roadmap, get in touch with us for help on mapping out the right path for your organisation.
