WhatsApp Business Platform Onboarding for Sellers

WhatsApp is how customers in the US, EU, Middle East and Latin America prefer to reach out. Plenty of shoppers would rather send “is this still in stock?” on WhatsApp than fill out a website contact form. But between deciding to launch WhatsApp and customers actually finding you there sits business verification, number setup, and template approval — enough friction that some teams stall halfway through. This walks through the process in the order you actually do it.

First, know the difference: WhatsApp Business App vs. Business Platform

The most common mix-up before onboarding is confusing two completely different paths:

If you plan to route WhatsApp messages into AI support and unify them with your website widget, email, Instagram and other channels, you need the Business Platform (API), not the phone app. Everything below assumes this path.

Step 1: Set up a verified Meta business identity

Before you can request API access, you need a verified Meta business identity:

1. Register a Meta Business Manager account with your company name, address and website.
2. Submit business verification: typically a business registration document or equivalent, your company website, and a way to prove domain ownership (a DNS record or an uploaded verification file).
3. Verification can take anywhere from a few days to two weeks. A common delay for cross-border sellers is a business name on the application that does not exactly match the registration document, or a website with no clear matching contact information — keep your company name, address and contact details visible in the site footer.

Step 2: Request a number and API access

Once your business identity is verified, move on to the number:

• New number: request a number in the Meta dashboard dedicated to the WhatsApp Business API. It cannot also be registered on the personal app or Business App.
• Migrating an existing number: if customers already know a number you have been using on the Business App, you can migrate it to the API. After migration the old app on your phone stops working, but the number and chat history customers see stay the same.
• The number needs to receive an SMS or voice verification code — many overseas sellers use a business-registered international number or a cloud communications number to complete this.

At the end of this step you have a WhatsApp business number you can call through the API — but you cannot send messages freely yet. Templates come next.

Step 3: Get message templates approved and learn “who speaks first”

WhatsApp has strict rules about who can start a conversation, and understanding this rule saves a lot of downstream trouble:

• Customer-initiated: once a customer messages you first, you can reply with anything for the next 24 hours — no template required.
• Business-initiated (shipping notifications, payment reminders, sale announcements): you must use a pre-approved message template from Meta. Free-form text is not allowed.
• Meta reviews every submitted template. Templates that read as marketing get stricter scrutiny; purely transactional notices (order confirmations, shipping updates) tend to clear faster.

Practical tip: prepare a handful of core templates in advance — order confirmation, shipping notification, common-question routing — and submit them for review before you need them urgently. Approval usually takes hours to a couple of days.

Step 4: Connect WhatsApp to your AI support workspace

With the number and templates ready, connect WhatsApp to your support system. For YundaDesk, this typically means:

1. Add WhatsApp as a channel in the workspace, authorize your Meta account, and select the business number.
2. Sync your existing product docs and policy files into the knowledge base — AI support on WhatsApp shares the same knowledge base as every other channel, so there is no separate content to maintain for this one channel.
3. Set the AI-to-human boundary for this channel: which questions AI answers directly (tracking, sizing, standard policy), and which always go to a human (refunds, complaints).
4. Confirm every channel feeds the same customer profile — if a customer already asked this question over email or the website widget, both AI and agents see the full history without asking the customer to repeat themselves.

Once connected, WhatsApp conversations show up alongside the website widget, Instagram, Messenger and every other channel in one shared workspace. AI answers first, and hands off to a human the moment it cannot answer or the customer asks — agents never need to switch between separate dashboards for each channel.

How billing actually works: the 24-hour window and AI credit are separate

Two layers of billing are easy to conflate here:

• On Meta’s side: billing runs by conversation, measured in a 24-hour session window. Messages exchanged within a window incur no extra charge; going past it requires a new session or a template message to open a fresh window.
• On YundaDesk’s side: your plan includes AI credit, and AI handling WhatsApp conversations draws from that same pool. Adding WhatsApp as another channel does not trigger a separate per-conversation or per-resolution charge — your bill stays predictable instead of spiking because inquiry volume jumped during a sale.

These two layers are independent: Meta bills its session windows regardless of what support system you use; YundaDesk bills for AI handling and workspace usage. For the full billing model, see our pricing page.

Common pitfalls to check before launch

Run through this before going live to avoid the mistakes most teams make:

• The company name used for business verification matches your registration documents and website exactly
• No agent is still replying manually via the phone app on that number before migration — migrating mid-conversation interrupts service
• At least order confirmation and shipping update templates are prepared and submitted for approval
• The knowledge base covers WhatsApp’s most frequent topics (shipping, returns policy, sizing)
• High-risk actions (refunds, compensation) are set to always hand off to a human — AI never executes them automatically
• AI responses have been tested in the actual languages customers use, not just English

For more on managing channels and building out the knowledge base, see omnichannel inbox explained and how the knowledge base feeds AI.

The WhatsApp onboarding process looks like a lot of steps, but none of them is technically hard on its own. What actually determines your timeline is waiting on Meta — business verification and template review. Plan for that lead time up front, and the technical integration ends up being the fastest part. Get the number, templates and knowledge base solid, and WhatsApp settles in as quietly as any other channel, with AI catching the first response every time.