WhatsApp Business API Onboarding: A Step-by-Step Checklist to Go Live in 48 Hours
Most delays in getting a WhatsApp Business API number live don't come from the software — they come from the setup steps happening out of order. Business verification blocked on a mismatched company name, a number that's still active in the regular WhatsApp Business app, templates submitted before the account is verified. None of these are hard problems, but each one adds days if you hit it unprepared.
1. Get your Meta Business Manager in order first
Everything downstream depends on this. Your Business Manager's legal name, address, and website should match your GST registration or incorporation documents exactly — a mismatch here is the single most common cause of a stalled business verification, and it's checked before anything else moves forward.
2. Decide: new number or migrate an existing one
A brand-new number can be provisioned and verified in minutes. Migrating a number already active on WhatsApp Business App or Messenger takes an extra step — the number has to be released from its current app before the Cloud API can claim it, and any existing chat history on that number's old app installation won't transfer automatically. Decide this upfront rather than mid-setup, since switching plans halfway means re-verifying.
3. Verify the number and connect it
Meta verifies the number via an SMS or voice call code during setup. Once verified and connected to your Business Manager, it becomes a WhatsApp Business Account (WABA) that VyaparPing's shared inbox, broadcast scheduler, and chatbot builder all plug into directly — there's no separate "connect the API" step after this.
4. Pre-submit your first templates before you need them
Template approval typically takes minutes to a few hours, but it's not instant, and you can't send a proactive message without one. Submit your order confirmation, appointment reminder, or welcome message templates as soon as the WABA is verified — not the day you plan to launch a campaign — so approval isn't the thing blocking go-live.
5. Invite your team and set routing before the first real conversation
Add every teammate who'll respond to customers to the shared inbox before launch, not after the first message arrives. Decide upfront who handles what — a support queue, a sales queue, or simple round-robin — so the first real customer conversation has somewhere to land instead of surfacing the question live.
What actually takes 48 hours
For a business with its legal documents in order, the realistic path is: Business Manager verification (usually same-day to a couple of days), number connection (minutes), first templates submitted immediately after (approved within hours), and team/routing configured in parallel. VyaparPing's onboarding team handles the Business Manager and WABA setup directly, so most customers are receiving and replying to real customer messages within 48 hours of starting.
Frequently Asked Questions
Yes — the same phone number can be migrated to the Cloud API. Existing chat history stored only in the old app doesn't transfer, but the number itself, and all future conversations, continue on it uninterrupted.
A mismatch between the business name/address on Meta Business Manager and the business's actual legal registration documents — keeping these identical from the start avoids most verification delays.
You need at least one approved template for any proactive (business-initiated) message, but you can receive and reply to customer-initiated messages immediately once the number is verified and connected — templates just need to be submitted early enough to be approved before your first campaign.
Where this applies
The parts of VyaparPing that put this into practice.