Moving from the regular WhatsApp Business app to the WhatsApp Business API gives a business more control over customer communication. You can automate routine replies, let several people manage conversations, run consent-led campaigns and connect WhatsApp to the systems your team already uses.
But many teams get stuck before that work begins. Which number should you use? Do you need business verification? Can you keep an existing number? What should be ready before onboarding?
Understanding the WhatsApp Business API requirements in advance makes setup smoother. This guide covers the practical preparation: business information, phone-number decisions, verification, display names, opt-in and the workflows to plan before go-live.
Meta’s onboarding flow, eligibility checks and verification requirements can vary by account and change over time. Confirm the current requirements in Meta’s business tools and with your provider before making account or number changes.
What is WhatsApp Business API?
The WhatsApp Business API is part of the WhatsApp Business Platform. It provides the infrastructure for businesses to communicate at scale and to connect customer conversations with automation, lead handling, team workflows and business systems.
For example, a website enquiry can receive an appropriate welcome message, be qualified through a guided flow, assigned to a sales owner and followed up only when it makes sense. That is different from relying on one person’s phone for every customer conversation.
The exact setup route varies, but most businesses should prepare the following before onboarding:
- A legitimate business and accurate business details
- An appropriate Meta Business Portfolio
- A long-term phone number with verification access
- A clear business display name
- A working website or supporting business presence
- Supporting documents if business verification is required
- A provider or direct technical setup that fits the workflow
- Customer opt-in, template and team-management plans
1. Prepare accurate business information
Gather your basic business details before starting. This may include your legal business name, address, business email, business phone number and website.
Consistency matters. If the name on your website, documents and Meta business information differs without a clear reason, verification may take extra attention. Use authorised company information rather than temporary personal details for an account the business expects to use long term.
Before you begin, check that your website clearly identifies the business, explains its products or services and provides a way to contact you. This is useful for both onboarding and customer confidence.
2. Create or review your Meta Business Portfolio
A Meta Business Portfolio is where Meta business assets are managed. During onboarding, your organisation may need to select an existing portfolio or create the appropriate business setup.
Review administrator access and make sure the portfolio represents the organisation that will own and operate the WhatsApp assets. Establishing the right ownership early helps avoid confusion as the team, number and workflow grow.
Business verification and phone-number verification are not the same thing. Phone verification confirms that the business can access a number. Business verification, where requested, is Meta’s process for confirming information about the organisation. Keep relevant, matching documents available, but do not assume every account follows the exact same review path.
3. Choose the right WhatsApp phone number
Your phone number is one of the most important setup decisions. Choose a number that:
- Belongs to the business and is available for the long term
- Can be accessed by an authorised team member during verification
- Is recognisable to customers
- Can appear consistently on your website, ads, QR codes and other materials
- Fits the applicable onboarding route
Avoid using a temporary number simply to speed through setup. Once customers know a WhatsApp number, changing it can create unnecessary confusion in campaigns, support journeys and printed material.
Can you use an existing WhatsApp number?
Possibly. Meta may offer migration or coexistence paths depending on how the number currently operates and the onboarding route available to your account. The details can change, so do not delete an existing WhatsApp account or make major number changes before checking.
Tell your provider that retaining the current business number is important. They can review the current options and prerequisites for your particular setup. This conversation should happen before—not halfway through—onboarding.
Confirm access to the number
Choosing a number is not enough; the business needs to receive the applicable verification method during setup. Old office lines, numbers managed by former employees and shared SIMs commonly create avoidable delays.
Before starting, confirm who has access, test the expected verification route where appropriate and make sure an authorised person will be available. This small check can save significant time later.
4. Choose a clear display name
Your display name tells customers which business they are speaking with. It should connect clearly to your brand or customer-facing identity and follow Meta’s applicable naming guidance.
Keep it clean and consistent with your website, social profiles and business documents. A display name is not an advert; avoid unnecessary promotional claims or phrases that make the identity unclear. If your legal company name and public brand differ, prepare evidence that explains the relationship if it is requested.
5. Keep your website ready
Your website can support your business presence during onboarding. At a minimum, a visitor should be able to understand:
- The business name
- What you offer
- How to contact you
- Basic information about the business
Fix placeholder content, broken pages and information that does not match the business you are submitting before starting. After onboarding, the site can also become a reliable WhatsApp lead source: a visitor can tap a WhatsApp CTA, receive an appropriate response and be routed to the right team.
6. Choose a WhatsApp API provider for the work after activation
API access is only the beginning. Before selecting a provider, ask what your team can do after the number is live:
- Can you automate routine responses and provide human handover?
- Can you create and schedule consent-based campaigns?
- Can multiple authorised colleagues manage conversations together?
- Can you track lead ownership and appropriate follow-ups?
- Can WhatsApp connect to your CRM, website, Google Sheets or ecommerce store?
- Can the team review delivery, replies and campaign performance?
The WhatsApp API provider guide has a detailed evaluation checklist. VartaFlow combines API communication with automation, campaigns, follow-ups, shared conversation management, integrations and analytics, so a team can operate the full customer journey instead of just activating a connection.
7. Plan customer opt-in before campaigns
Access to the API is not permission to message every number in a database. Your organisation needs a clear customer opt-in process for the communications it plans to send, and it must honour opt-outs promptly.
You might collect permission through website forms, click-to-WhatsApp ads, QR codes, checkout flows or another appropriate customer touchpoint. Record the source and expected purpose of consent. A relevant, opted-in audience is more valuable than a large list of people who did not expect to hear from you.
Review our WhatsApp marketing best practices before launching campaigns. It covers consent, audience expectations, frequency and response ownership in more depth.
8. Prepare important message templates
Businesses planning to initiate eligible customer conversations should prepare their initial WhatsApp message templates early. Templates may support marketing, order updates, appointment reminders, customer notifications and authentication use cases.
Start with the customer journeys that matter most. For example:
| Journey | Template purpose | What to plan |
|---|---|---|
| New lead follow-up | Confirm interest and offer help | Source, owner and response route |
| Appointment reminder | Remind the customer of a booked time | Accurate variables and rescheduling path |
| Order update | Share a transaction-related status | Order data source and support escalation |
| Re-engagement campaign | Send a relevant, opted-in offer | Segment, opt-out and campaign owner |
Every template should match its actual purpose and Meta’s current requirements. Do not leave every message decision until after onboarding; having a few reviewed customer journeys ready helps the team start responsibly.
9. Decide who will manage conversations
Another key requirement is operational rather than technical: who will own the work after a customer replies?
If sales, marketing and support all use WhatsApp, define their roles before launch. Consider routing rules, response expectations, escalation paths and who can access customer data. A shared WhatsApp team inbox helps multiple authorised colleagues manage the same number with clear ownership and conversation context.
This prevents customer communication from depending on one employee’s personal device. It also gives the business a better way to handle a new enquiry, a campaign response and an existing support issue without losing context.
10. Map the first automation and integrations
Once the setup is complete, build the first useful customer journey rather than trying to automate everything at once. A practical sequence might be:
Customer message → welcome reply → requirement captured → lead assigned → appropriate follow-up → human conversation
Use WhatsApp chatbot automation for predictable first steps, with a visible route to a person for exceptions. Then decide which systems should connect to the workflow: a CRM, website form, Google Sheet or ecommerce store. The integration documentation can help your team plan data ownership, events and failure handling.
WhatsApp Business API onboarding checklist
Use this checklist before beginning:
| Requirement | What to prepare |
|---|---|
| Business details | Correct company name, address, email and contact details |
| Meta setup | Appropriate Business Portfolio and authorised access |
| Website | An active site that accurately represents the business |
| Phone number | A long-term business number with verification access |
| Display name | A clear, consistent business or brand identity |
| Verification | Matching supporting information and documents, where requested |
| Provider | A platform that fits the intended team workflow |
| Opt-in | A clear method for collecting and recording consent |
| Templates | Initial messages for priority customer journeys |
| Team access | Defined conversation owners, roles and escalation paths |
| Automation | One or two high-value journeys to launch first |
| Integrations | The CRM, website, spreadsheet or commerce connections needed |
Common onboarding mistakes to avoid
Most delays come from a few preventable issues:
- Inconsistent business information across documents, website and Meta tools
- Selecting a number without confirming access for verification
- Changing or deleting an existing number before checking retention options
- Treating activation as the end goal instead of planning the first customer response
- Sending campaigns without a clear opt-in and opt-out process
- Giving several teams access without ownership or escalation rules
The final point is especially important. A live API does not automatically produce a good customer experience. Before launch, decide who receives an enquiry, how customers reach a person and how the team records the next action.
Ready to get started?
The requirements become much easier to manage when the business prepares the right information early. Start with accurate details, select the right number, confirm verification access, review your Meta setup and prepare customer opt-in and template plans.
Then think beyond activation. A VartaFlow demo can help you discuss your number, onboarding route, automation, integrations and customer communication workflow before you get started.