WhatsApp Business API setup used to mean weeks of waiting on Meta's direct approval process. Embedded Signup, Meta's newer onboarding flow, has cut that down to minutes when you go through a Business Solution Provider.
Create an account with a platform like OneClickMsg — this gets you the dashboard, template manager, and everything else you'll actually use day to day, since Meta itself doesn't offer a client-facing dashboard for API access.
Click "Connect WhatsApp," log in with your business Facebook account, and either select an existing WhatsApp Business Account or create a new one. Meta walks you through choosing the phone number you want to use for messaging — this is the number your customers will see and reply to.
Meta sends a verification code to the number by SMS or call. Enter it, and your number is registered on the Cloud API. From this point, the number is dedicated to API use — it won't function inside the regular WhatsApp consumer app anymore.
Before you can send outbound messages, you need at least one approved template. WhatsApp requires pre-approved templates for any message you initiate outside a 24-hour customer-initiated conversation window — free-text replies only work once a customer has messaged you first. Submit something simple to start — a welcome message or an order confirmation template works well — and approval typically comes back within minutes to a few hours.
Once your template is approved, you can send to any number that's opted in — via the dashboard's manual send, a bulk CSV upload, or a broadcast campaign to a saved group or tag.
The most common holdup is trying to use a number that's still active on the regular WhatsApp app or Business App — it needs to be freed up first, either by deleting the account on that number or migrating it properly through Meta's own flow. Two-step verification left on from a previous WhatsApp setup on that number is the other common snag, since it requires knowing the existing PIN or turning it off in Meta Business Manager before the number can be registered fresh.
Rejections are usually about category mismatch (marketing content submitted as a "utility" template) or vague, generic wording that doesn't clearly state what the message is for. Keep the wording specific and match the category to what the message actually does, and most first submissions clear review without issue.
Once you're connected, the natural next steps are usually: import your existing contact list (with tags if you want to segment later), set up one chatbot flow for common questions, and configure your business hours so automated replies and appointment-booking Flows reflect when you're actually open.
It's tempting to submit a marketing-heavy template first, but a plain utility message — an order confirmation or a simple welcome note with no promotional language — tends to clear review fastest, since it's unambiguous about its category and purpose. Save more promotional templates for once you've got a feel for the approval process.
Most businesses spend their first week doing three things: importing an existing contact list, sending a small test broadcast to confirm delivery works end to end, and setting up one keyword-based auto-reply for their most common question. None of this requires waiting on Meta again — the setup process itself is the only part with an external dependency.
If you're already on WhatsApp Business API through a different platform, moving providers doesn't mean starting over with Meta — your WhatsApp Business Account and phone number can typically be migrated to a new provider without losing your number's message history or quality rating, though the exact steps vary depending on your current provider's offboarding process.
Q: Can I use my existing personal WhatsApp number? A: Only if you're willing to free it from the regular app first — API and the consumer app can't run on the same number simultaneously.
Q: How long does template approval take? A: Usually minutes to a few hours, though it can occasionally take longer during high review volume — there's no guaranteed SLA from Meta.
Q: Do I need a developer for any of this? A: No — Embedded Signup, template submission, and everyday sending are all handled through the dashboard. A developer is only needed if you're building a custom integration via the REST API.