Two resellers, same week, two completely different starts. I watched it happen last year. The first one — call him the Indore guy, because he’d rather I didn’t name his agency — decided he had to do things properly. He read somewhere that selling a WhatsApp CRM meant getting onto the official WhatsApp Business Platform, so before he signed a single client he set up a Meta Business Portfolio and started a WABA application. Business Verification, document uploads, a display name to clear. He told his first prospect he’d be live in a few days. He wasn’t.
Three weeks later he was still stuck. Meta had bounced his Business Verification once because the address on his registration certificate didn’t match the address on his utility bill — a single line of text, off by a flat number. Then the display name he picked got flagged because it wasn’t an obvious match for his registered company name. Meanwhile, a competitor across town had quietly onboarded four SMB clients in the same three weeks. That competitor wasn’t faster or smarter. He just resold a WhatsApp CRM Chrome extension that needed no Meta application at all. There was nothing to get approved, so there was no queue to wait in.
I’m Rakshit Soni, co-founder of Lion CRM, a WhatsApp CRM Chrome extension built by LotsOfCode Private Limited. I’ve spent about four years building WhatsApp automation tooling, and a big part of that now is helping whitelabel resellers turn a rebranded Lion CRM into a real subscription business. The WABA question lands in my inbox almost weekly — do I need Meta approval to resell this? This guide is the honest answer. We’ll cover what meta waba approval actually is, the real step-by-step process, the document checklist, the seven reasons applications get rejected, how long it genuinely takes, and the route a Chrome-extension reseller takes that skips the entire approval queue. I’ll be balanced — there’s a real section on when the WABA route is still the right call. (If you’d rather watch than read, the LotsOfCode YouTube channel covers reseller operations in video form.) This is written for the Vikram-style reseller — a 35-year-old running a 5-to-50-person agency in India, reselling to SMB clients on a monthly subscription.
TL;DR — the approval queue is optional, and most resellers should skip it
| WABA / official API route | Chrome-extension route (Lion CRM) | |
|---|---|---|
| Meta approval needed | Yes — full application | None |
| Time to launch | Realistically 1–3 weeks | Same day |
| Business Verification | Required, document review | Not required |
| Display-name review | Required, can be rejected | Not applicable |
| Template approval | Every business-initiated template pre-approved by Meta | Not applicable — uses normal WhatsApp |
| Per-message cost | Yes — per-message pricing by category | None |
| Best for | High-volume programmatic notifications, verified badge | SMB conversational sales, agencies, fast launch |
A WABA — a WhatsApp Business Account on the official WhatsApp Business Platform — has to clear Meta’s approval gauntlet before it sends anything: Business Verification, display-name review, template approval, messaging tiers tied to a quality rating, and per-message fees. A Lion CRM reseller never files that application. The product drives the client’s own ordinary WhatsApp through WhatsApp Web, so the rules that apply are WhatsApp’s normal consumer anti-spam behaviour, not an API approval process. There’s still a responsible-messaging discipline — but there’s no Meta queue, and you can launch the day you decide to.
Why Meta WABA approval matters to a WhatsApp CRM reseller
Here’s why this topic is worth a full guide and not a footnote. Almost every new reseller who comes to me has already half-decided that selling a WhatsApp CRM means dealing with Meta directly. They’ve read competitor marketing pages full of phrases like official API and Meta Business Partner, and they’ve quietly concluded that meta waba approval is a box they must tick before they can earn a rupee. That assumption costs them weeks, sometimes money, and occasionally a deal.
So you need a clear picture of what the approval process is, before you can decide whether it applies to you at all. If you pick the official WhatsApp Business Platform route — directly or through a BSP — then meta waba approval is the literal gate between you and your first message. Nothing sends until the WhatsApp Business Account is verified and a display name is cleared. If you pick the Chrome-extension route, that gate doesn’t exist for you. Either way, you can’t make a smart call without understanding the thing you’re choosing to do or skip.
There’s a sales angle too. Your prospects will ask. An SMB owner who’s been pitched by an AiSensy or a Wati reseller has heard the words API approval, and they’ll wonder whether your product needs it. You want to answer that with confidence and accuracy — not bluff. A reseller who can explain, in plain Hindi or English, exactly why their product doesn’t sit behind a Meta approval queue sounds more credible, not less. Knowing this material well is itself a sales asset.
And honestly, this is one of the most misunderstood corners of the whole WhatsApp business world. Half the confusion online comes from people mixing up WhatsApp Business app (the free consumer app), WhatsApp Business Platform (the official API), and WhatsApp Web automation tools (extensions like Lion CRM). Three different things, three different rule sets. Let’s pull them apart.
What a WABA actually is — and what it is not
WABA stands for WhatsApp Business Account. It’s the account object that sits at the centre of the official WhatsApp Business Platform — what most people loosely call the WhatsApp Business API. A WABA is not the green WhatsApp Business app you download from the Play Store. It’s not a phone number by itself. It’s a business entity registered with Meta, linked to a Meta Business Portfolio, that gives a company programmatic, API-level access to send and receive WhatsApp messages at scale.
When you go the WABA route, here’s roughly what’s involved. You need a Meta Business Portfolio — the account formerly and still often called Business Manager. Inside it, you create or connect a WhatsApp Business Account. You attach a phone number to it, and that number has to be one that is not currently active on the regular WhatsApp app — one number, one WABA, and a number can’t live in both places at once. You either build directly on Meta’s Cloud API or, far more commonly, you go through a BSP — a Business Solution Provider like Wati, AiSensy, Interakt or DoubleTick — who wraps the API in a usable dashboard.
Then come the controls that make a WABA a WABA. Business-initiated messages — the ones you send to a customer who hasn’t messaged you in the last 24 hours — must use message templates that Meta pre-approves, category by category. You don’t get unlimited reach on day one; the platform applies messaging limits, or tiers — as of 2026 these step up through bands like 250, 1,000, 10,000 and 100,000 unique customers per 24 hours, and onward to unlimited — and you climb those tiers as your quality rating stays healthy (Meta shows it as green, yellow or red). And there’s a real cost: Meta moved to per-message pricing, billed by message category — marketing, utility, authentication — while service replies inside the 24-hour customer-care window are free. Meta updates these limits and prices regularly, so always check the current WhatsApp Business Platform documentation rather than trusting a number you read in a blog, including this one.
What a WABA is not is just as important for a reseller. It is not a quick toggle. It is not free of Meta’s review. And it is not the only legitimate way to run WhatsApp for a business. The official platform is one architecture — a powerful, programmatic one — but it isn’t the only door. A WhatsApp CRM that works on top of a normal WhatsApp Web session is a completely different architecture, and it doesn’t touch a WABA at all. Hold that thought; it’s the whole pivot of this guide.
The Meta WABA approval process, step by step
If you do choose the official route, here’s the meta waba approval process laid out in the order you’ll actually hit it. I’m describing it accurately as of 2026 — Meta reshuffles these steps periodically, so treat the shape as reliable and verify the fine print against current docs.
Step 1 — Set up a Meta Business Portfolio. Before anything WhatsApp-specific, you need a Meta Business Portfolio (Business Manager). This holds your business identity, your assets, and the people who manage them. A half-finished Business Portfolio is one of the quieter reasons applications stall, so fill it in fully — legal business name, website, business details.
Step 2 — Start Business Verification. This is the heart of the WABA approval process. Meta needs to confirm your business is a real, registered legal entity. You submit your legal business name, registered address, and supporting official documents — a business registration certificate, and often a proof-of-address document such as a recent utility bill. Meta’s review team checks that what you submitted is consistent and genuine. Get this right and the rest is mostly mechanical. Get it wrong — even a mismatched flat number — and you’re resubmitting.
Step 3 — Create the WhatsApp Business Account and attach a number. Inside the verified Business Portfolio, you create the WhatsApp Business Account itself and connect a phone number to it. Reminder, because this trips people: the number must not already be registered on the regular WhatsApp or WhatsApp Business app. If it is, you either migrate it or pick a fresh number. You’ll verify ownership of the number by code, the usual way.
Step 4 — Submit your display name for review. Your WhatsApp Business Account carries a display name — the business name customers see. Meta reviews that name against its display-name guidelines. The name has to genuinely represent your business and follow the rules — no grabbing a generic category word, no impersonation, no mismatch with your verified business identity. Display name approval is a separate review from Business Verification, and it has its own rejection path. This catches a lot of first-timers.
Step 5 — Pick your build path: Cloud API direct or a BSP. You can build on Meta’s Cloud API yourself, which means real developer work, or you go through a BSP who hands you a dashboard. Most resellers and most businesses go BSP, because raw Cloud API integration is an engineering project, not an afternoon.
Step 6 — Create and submit message templates. Any message you start a conversation with — outside the 24-hour service window — has to ride on a template, and every template is submitted to Meta for approval against content and category rules. Templates get rejected too, usually for being too promotional in the wrong category or for sloppy formatting.
Step 7 — Go live inside your tier, and watch your quality rating. Once verified and approved, you start sending — but inside a messaging limit tier. You earn your way up the tiers (250 to 1K to 10K and beyond) by keeping volume and engagement healthy and your quality rating out of the red. Drop into red and your tier — and reach — can fall.
That’s seven distinct stages, and at least three of them — Business Verification, display-name review, template approval — are points where Meta can say no. Which brings us to the paperwork.
The WABA approval document checklist
The single biggest delay in the meta waba approval process is documents — the wrong ones, blurry ones, or ones that don’t agree with each other. So here’s the checklist I’d hand a reseller going the official route. Treat it as indicative; Meta’s exact requirements vary by country and entity type, and they change.
| What you’ll need | Why Meta wants it | Where resellers slip up |
|---|---|---|
| Legal business name (exact) | Must match every document and your display name | Using a trading name instead of the registered name |
| Business registration certificate | Proves you’re a real registered entity | Expired, low-resolution, or wrong file format |
| Proof of registered address | Confirms the business address | Address doesn’t match the registration certificate |
| Utility bill or bank document (recent) | Backs up the address claim | Document older than the accepted window |
| Business website and email | Supports business identity | Website live but with no real business info on it |
| Dedicated phone number | Becomes the WABA number | Number already active on WhatsApp |
| Business category / industry detail | Meta screens for restricted industries | Vague or misleading category selection |
A few rules that save you a resubmission cycle. One: every name and address must match across every document — your registration certificate, your address proof, and the details you type into Business Verification all have to read identically. Meta’s review is, frankly, picky about this, and that pickiness is the number-one cause of a bounced verification.
Two: scan quality matters more than you’d think. A genuine document photographed badly in poor light gets treated like a suspect document. Use clean, full-page, high-resolution scans or PDFs.
Three: your business website should actually look like a business. If Meta’s reviewer clicks through to a parked page or an empty template site, that’s a weak signal. A real homepage with your business name, what you do, and contact details strengthens the whole application.
Honestly? The document-mismatch problem trips up almost everyone the first time. It’s not hard, it’s just fiddly, and one stray character costs you days.
Don’t fancy a document-review queue at all? A whitelabel Lion CRM reseller skips this entire checklist — there’s no Business Verification because there’s no WABA. You can register and start branding your reseller account today at admin.lioncrm.com.
Why Meta WABA approval gets rejected: 7 common reasons
A rejection isn’t the end of the world — you can usually fix the issue and resubmit — but each rejection costs you days, and a string of them can cost you a client who got tired of waiting. Here are the seven reasons I see most often for meta waba approval failing.
1. Document mismatch in Business Verification. The most common one by far. Your business name or address on one document doesn’t exactly match another, or doesn’t match what you typed into the form. Meta’s verification flags it and bounces the application.
2. Low-quality or unaccepted documents. A blurry photo, a cropped page, an expired certificate, or a document type Meta doesn’t accept for your country. The information might be perfectly true — but if the reviewer can’t read it cleanly, it fails.
3. A display name that breaks the guidelines. Display name approval is its own review. If the name doesn’t clearly match your real, verified brand — or it’s a generic category word, or it looks like it’s impersonating another business — it gets rejected even after Business Verification has passed.
4. A prohibited or restricted industry. WhatsApp’s commerce and business policies restrict certain industries outright and limit others. If your business — or your client’s business — falls into a restricted category, the WhatsApp Business Account can be refused regardless of how clean your paperwork is.
5. The phone number is already on WhatsApp. One number, one home. If the number you’re attaching to the WABA is still active on the regular WhatsApp or WhatsApp Business app, the connection fails until you free it up or choose another number.
6. An incomplete Meta Business Portfolio. A Business Portfolio with missing details, no verified business information, or unresolved policy issues drags the whole WhatsApp Business Account application down with it. Meta treats the Portfolio as the foundation; a shaky foundation stalls everything above it.
7. Policy violations. Past or present violations of Meta’s business or commerce policies on any linked asset can block a WABA. Meta looks at your overall standing, not just the one application in front of it.
Notice the pattern. Almost every rejection reason is something a reseller can’t fully control on a client’s behalf — it depends on the client’s paperwork, the client’s industry, the client’s existing number, the client’s Meta history. When you resell the WABA route, you inherit all seven of these failure modes for every client you onboard. That’s a real operational tax, and it’s worth weighing honestly before you commit a business model to it.
How long Meta WABA approval really takes
This is the question every reseller asks, and the honest answer is it depends — but let me give you realistic ranges instead of a marketing fairy tale.
Business Verification, the longest stretch, typically runs from a few days to around two weeks. If your documents are clean and consistent, it can resolve quickly. If anything is off, you get a rejection, you fix it, you resubmit — and the clock restarts. Display name approval is usually faster, often one to two days. Template approvals, once you’re set up, are typically quick — minutes to a day each — though that’s an ongoing cost, not a one-time one, because you submit new templates whenever your messaging needs change.
Stack it end to end and a realistic timeline for meta waba approval is roughly one to three weeks for a smooth run. A rejection or two on Business Verification can push that to a month or beyond. I want to be careful here: these are realistic observed ranges, not promises. Meta updates its processes and review capacity regularly, so the only honest framing is plan for one to three weeks, hope for the shorter end, and don’t promise a client a hard go-live date you can’t control.
Here’s the operational reality for a reseller. That one-to-three-week window isn’t dead time you spend once. If your business model is reselling the WABA route, you re-enter some version of this queue for every client — every new client needs their own verified Business Account, their own display name cleared, their own templates approved. The waiting isn’t a setup cost you pay once. It’s a recurring friction on every single onboarding. For an agency trying to onboard SMB clients quickly and predictably, that’s a structural drag.
The fastest reseller launch skips the queue entirely. If a same-week launch matters more to you than an official badge, the Launch your own WhatsApp CRM SaaS in 7 days guide walks the zero-to-first-client path with no Meta application anywhere in it.
The reseller’s shortcut: when you can skip WABA approval entirely
Now the pivot. Everything above describes one architecture — the official WhatsApp Business Platform, where a WABA is the gate. There’s a second architecture, and it’s the one Lion CRM uses, and it changes the whole calculation for a reseller.
Lion CRM is a WhatsApp CRM Chrome extension. It installs in the user’s browser and runs on top of their own WhatsApp Web session. The user logs into WhatsApp Web the way they always have, with the number they already use, and Lion CRM layers a CRM on top of it — contacts, tags, notes, message templates, bulk sending, a Kanban pipeline, quick replies. Every message goes out from the client’s own existing WhatsApp number, through their own WhatsApp session. Contacts, tags, notes and templates are stored locally on the user’s own device — 100% local data storage. There’s no API. No BSP. No server hosted by Lion CRM or by you, the reseller. (The Lion CRM WhatsApp CRM Chrome extension guide has the full architecture breakdown.)
Sit with what that means for meta waba approval. There is no WABA. So there is nothing to verify, nothing to get approved, no display name to clear, no template to submit to Meta, no messaging tier to climb, no quality rating to defend, no per-message fee to pay. The entire approval gauntlet — Business Verification, display-name review, template approval — simply doesn’t exist on this route, because you never created a WhatsApp Business Account in the first place. You’re not asking Meta for permission to use the API. You’re using ordinary WhatsApp, the same WhatsApp a billion people use, with a CRM bolted onto the browser.
For a reseller, this collapses the launch timeline from one to three weeks of Meta queue, per client down to same day. A client installs your branded extension, logs into their own WhatsApp Web, and they’re running. No application. No waiting room. No rejection risk. Multiply that across an agency onboarding clients month after month and the difference isn’t a convenience — it’s a different business model.
Now let me be straight with you, because overclaiming here would be dishonest and would also get you in trouble. Skipping WABA approval does not mean no rules at all. Because Lion CRM drives a normal WhatsApp number, the rules that apply are WhatsApp’s normal consumer anti-spam and acceptable-use behaviour. Blast a few hundred cold contacts who never opted in, get reported as spam, and that number can be restricted or banned — the same as if a person did it manually. Responsible messaging still matters: warm contacts, opt-ins, sensible sending pace, real conversations. What you skip is the Meta application and approval queue. What you don’t skip is messaging like a decent business. That’s a fair trade, and it’s an honest one. There’s no approval bureaucracy, but there’s still a discipline.
A reseller who understands this can pitch it cleanly to an SMB client: you keep your own number, your data stays on your own device, you’re live today, and there’s no per-message bill. For a small business owner who just wants to sell over WhatsApp without becoming a platform-compliance manager, that’s a genuinely strong story.
WABA route vs Chrome-extension route: an honest comparison for resellers
Let’s put both routes side by side, fairly. Neither is bad. They’re built for different jobs, and a good reseller picks based on which job their clients actually have.
| Factor | WABA / official API route | Chrome-extension route (Lion CRM) |
|---|---|---|
| Meta approval queue | Yes — Business Verification, display name, templates | None |
| Time to first message | Realistically 1–3 weeks per client | Same day |
| Rejection risk | Real — 7 common rejection reasons | None — no application exists |
| Phone number | New dedicated number, not on WhatsApp app | Client’s own existing WhatsApp number |
| Where data lives | On the BSP / Meta side | Locally on the client’s own device |
| Per-message cost | Yes — per-message pricing by category | None |
| Message templates | Pre-approved by Meta, category-bound | Free-form, normal WhatsApp messages |
| Verified green badge | Possible after review | Not available |
| Sending limits | Tiered (250 / 1K / 10K / 100K / unlimited) | Normal WhatsApp behaviour and pacing |
| Best fit | High-volume, programmatic, big-brand sends | SMB conversational sales, agency reselling |
| Reseller onboarding speed | Slow, queue-bound, per client | Fast, repeatable, same-day |
Read that table as a reseller, not as a tech buyer. The WABA route’s strengths — programmatic scale, the verified badge, automated transactional sends — are real, but they’re enterprise strengths. The Chrome-extension route’s strengths — same-day launch, no approval risk, no per-message bill, the client’s own number, local data — are exactly the things an SMB client values and an agency needs to scale onboarding.
For the Vikram-style reseller running an agency that sells to small businesses on monthly subscriptions, the deciding factor is usually onboarding speed and predictability. If every client onboarding means re-entering a one-to-three-week Meta queue with a real chance of rejection, your growth is throttled by Meta’s review team. If onboarding is install, log in, go, you can take on as many clients as your sales can find. That’s why the no-WABA route wins for most agency resellers — not because the API is bad, but because the API’s friction lands squarely on the part of your business you most need to be fast: signing up the next client.
Curious what resellers actually earn on this model? The Whitelabel WhatsApp CRM margins: what resellers actually make guide breaks down the rupee economics tier by tier, so you can see why same-day onboarding compounds into real revenue.
When the WABA route is still the right call
I’m not going to pretend the WABA route is never the answer — it absolutely is, for the right job, and a reseller who knows when to recommend it looks more trustworthy, not less. Here’s when the official WhatsApp Business Platform genuinely beats a Chrome-extension CRM.
Very high-volume, programmatic messaging. If a client needs to fire tens or hundreds of thousands of automated messages a day — order confirmations, OTPs, shipping updates — from a system, the API is built for exactly that. A browser extension running on one WhatsApp Web session isn’t the tool for industrial-scale transactional sends. The WABA’s tiered limits and server-side automation exist for this.
The official verified green badge. Some brands want that green verified-business checkmark next to their name. It comes only through the official platform’s verification. If a client’s brand positioning genuinely needs that signal, the WABA route is the only way to get it.
Big-brand notification programs. A bank, an airline, a large e-commerce platform sending utility and authentication messages to millions of customers needs the reliability, the deliverability infrastructure, and the formal compliance posture the WhatsApp Business Platform provides. That’s an enterprise need, and it’s a legitimate one.
Deep integration into a large automated stack. If the WhatsApp channel has to plug into a sprawling backend — a data warehouse, an enterprise CRM, an event-driven automation pipeline — the API’s webhooks and programmatic surface are the right fit. An extension is a human-in-the-loop tool by design.
Here’s my actual opinion, though, the one hot take of this guide. The WABA route is the right call far less often than competitor marketing implies. The official-API pitch is loud because it sounds impressive and because BSPs earn per-message revenue, so they have every reason to push it. But the typical client a typical agency reseller serves — a 5-person business, a clinic, a coaching institute, a local retailer, a real-estate dealer — does not need programmatic enterprise messaging. They need to have good conversations with leads and customers over WhatsApp and keep those contacts organised. For that client, the API’s verification queue, template approvals, per-message fees and messaging tiers are pure overhead with no matching benefit. The honest rule: recommend the WABA route when a client genuinely has an enterprise-scale, programmatic, badge-or-bust requirement. For everyone else — which is most of the SMB market — the no-approval Chrome-extension route is the better fit, and pretending otherwise just to sound official does your client a disservice.
Try Lion CRM free for 7 days
Before you decide which route to build your reseller business on, see the no-WABA architecture for yourself. The quickest way is to run Lion CRM on your own WhatsApp. Every first-time Chrome Web Store install gets an automatic 7-day free trial — no credit card, no application, no waiting room.
Steps:
- Click the install link → Get Lion CRM on Chrome Web Store
- Click “Add to Chrome” — the extension installs in seconds.
- Open WhatsApp Web in your browser — Lion CRM activates automatically on top of your own session, using your own number.
- Your 7-day free trial starts the moment you log in. No credit card needed, and nothing went to Meta for approval — notice how there was no queue at all.
- Walk through the features — Bulk Messaging, Kanban Board, Message Templates, Quick Reply, Smart Calendar, Webhooks and the rest — and watch how every message rides your own ordinary WhatsApp, with contacts stored locally on your device.
- After 7 days, pick a paid plan — ₹99 (~US$1.20) first-month special, then ₹299/month (~US$3.50), or ₹2,360/year (~US$28, about ₹197/month) — or move straight to the whitelabel reseller plan below.
The point of running it yourself is simple: once you’ve felt how fast install, log in, go is, the one-to-three-week WABA queue stops looking like a normal cost of doing business.
Start your whitelabel WhatsApp CRM SaaS
Once you’ve tested the extension and you want to resell it under your own brand — with no Meta application standing between you and your first client — here’s the reseller flow.
Steps:
- Go to the admin panel → admin.lioncrm.com
- Register your agency account, then log in.
- Choose a plan — Starter (US$150 one-time + US$2.50/user/month), Growth (US$200 one-time + US$2.00/user/month, the popular pick), or Enterprise (US$250 one-time + US$1.00/user/month) — and complete payment. PayPal checkout runs through paypal.com. You’ll land on the reseller dashboard.
- Open the Branding section → fill in your white-label details (brand name, logo, colours, support number, your website URL) → click Save. Your clients see your brand, never Lion CRM or LotsOfCode.
- Click Download Extension to get your own white-label branded build of the Chrome extension.
- Open the Licenses section to generate licenses:
– Paid licenses (each consumes one active-user slot at your tier’s per-user/month fee)
– 7-day free trial licenses (hand these to prospects so they can test your branded extension first) - The Overview section gives you 1 month of free license for your own personal use.
- Add balance once in the Wallet section — it removes per-license payment friction, since each new license draws from the wallet balance.
- Distribute your branded extension to clients. Each client installs it, logs into their own WhatsApp Web, and they’re live — same day, no WABA, no Business Verification, no approval queue anywhere in the flow.
One compliance note: whitelabel partners need a minimum of 30 active user licenses after a 3-month grace period. The full reseller flow is also walked through on the LotsOfCode YouTube channel if you’d rather watch it, and Kuldeep, co-founder, handles partnership and onboarding questions on WhatsApp at +91 74260 34448.
The honest verdict: should a reseller chase WABA approval?
If you scrolled to the bottom, here’s the decision-tree version for different reseller situations.
- Brand new reseller, first SMB clients, want to launch this month. Skip the WABA route. Going through meta waba approval per client will throttle you before you’ve built momentum. Resell the Chrome-extension route, onboard same-day, get revenue moving.
- Agency reselling to small businesses on monthly subscriptions. The no-WABA route, almost every time. Your growth depends on fast, repeatable onboarding, and a Meta queue per client is a structural brake on exactly that. This is the Vikram case, and it’s clear-cut.
- A client genuinely needs enterprise-scale programmatic messaging or the verified badge. Here the WABA route is the right recommendation. Be honest with that client, point them at a BSP, and don’t force a Chrome extension into a job it isn’t built for.
- You’re not sure which your client needs. Ask one question: do they need to have conversations and stay organised, or do they need to fire huge volumes of automated messages from a system? Conversations → Chrome-extension route. Industrial automation → WABA route. Most SMB clients are the first kind.
- Tempted to chase WABA approval just because it sounds official. Don’t. Official is marketing, not a fit assessment. Match the route to the client’s real need. For most of the SMB market, the no-approval route is the better product and the faster business.
The thread through every case: meta waba approval is a real, sometimes necessary process — but it is not a tax every WhatsApp CRM reseller must pay. It applies to one architecture. Choose the architecture that matches your clients, and for most agency resellers serving small businesses, that’s the Chrome-extension route with no approval queue at all.
Frequently asked questions
Q: Do I need a WABA to resell a WhatsApp CRM?
It depends entirely on which CRM architecture you resell. If you resell a product built on the official WhatsApp Business Platform, then yes — that product needs a WhatsApp Business Account, and meta waba approval applies. If you resell a WhatsApp CRM Chrome extension like Lion CRM, then no — the extension runs on the client’s own WhatsApp Web session and ordinary WhatsApp number, so there’s no WABA to create and nothing to get approved. A whitelabel Lion CRM reseller never files a WABA application.
Q: How long does Meta WABA approval take?
Realistically one to three weeks end to end for a smooth run. Business Verification is the longest stretch — a few days to around two weeks — display-name review is usually one to two days, and template approvals are typically quick. A rejection on Business Verification restarts the clock and can push the total past a month. Meta updates its review processes regularly, so treat these as observed ranges, not guarantees, and never promise a client a hard go-live date you can’t control.
Q: Why was my WhatsApp Business API application rejected?
The most common reasons are document mismatches in Business Verification — your business name or address not matching exactly across documents — followed by low-quality or expired documents, a display name that breaks WhatsApp’s display-name guidelines, a prohibited or restricted industry, a phone number already active on WhatsApp, an incomplete Meta Business Portfolio, and existing policy violations on a linked asset. Most rejections are fixable: correct the issue and resubmit. Document consistency is the single biggest thing to get right before you apply.
Q: Can I use WhatsApp for business without API approval?
Yes. The WhatsApp Business API is one way to run WhatsApp for a business, not the only one. A WhatsApp CRM Chrome extension like Lion CRM works on top of normal WhatsApp Web, using the business’s own existing number, with no WABA and no Meta approval. You still have to message responsibly — WhatsApp’s normal consumer anti-spam rules apply, so no blasting cold, un-opted-in contacts — but there’s no API approval process, no Business Verification, and no per-message fee.
Q: What documents do I need for WhatsApp Business verification?
For Business Verification on the official platform you’ll typically need your exact legal business name, a business registration certificate, a proof of registered address (often a recent utility bill or bank document), a business website and email, and a dedicated phone number not already on WhatsApp. Exact requirements vary by country and entity type and Meta changes them, so check the current WhatsApp Business Platform documentation. The golden rule: every name and address must match identically across every document, or the verification gets bounced.
Q: Does Lion CRM need Meta approval?
No. Lion CRM is a Chrome extension that runs on the user’s own WhatsApp Web session, in their own browser, with their own WhatsApp number, and 100% local data storage. There’s no WhatsApp Business API, no BSP partnership, no server hosted by Lion CRM, and no Meta app review involved. A reseller who whitelabels Lion CRM files no WABA application and waits in no approval queue — clients can be onboarded the same day. Responsible messaging is still expected, but the Meta approval bureaucracy simply isn’t part of the picture.
Q: WABA vs WhatsApp Web automation — which is safer for a small agency?
For a small agency reselling to SMB clients, the WhatsApp Web route is usually the safer business choice — not because the API is unsafe, but because the API’s friction lands on your growth. Every WABA client means re-entering Meta’s approval queue with real rejection risk, which throttles onboarding. The Chrome-extension route launches same-day per client. Both routes require responsible messaging to keep numbers healthy. The WABA route is genuinely better only when a client needs enterprise-scale programmatic sending or the verified badge.
Related guides
These Lion CRM articles go deeper into the reseller architecture, economics and launch playbook:
- Lion CRM WhatsApp CRM Chrome extension guide — the canonical reference for the no-WABA architecture this guide is built on.
- Launch your own WhatsApp CRM SaaS in 7 days — the zero-to-first-client playbook, with no Meta application anywhere in it.
- Whitelabel WhatsApp CRM software: founder’s 2026 guide — start here if you’re new to whitelabel reseller economics.
- Whitelabel WhatsApp CRM comparison India 2026: honest guide — the pillar guide every reseller article links back to.
- AiSensy alternatives: whitelabel WhatsApp CRM — how the BSP/API route compares with the Chrome-extension route, vendor by vendor.
- Whitelabel WhatsApp CRM margins: what resellers actually make — the reseller margin economics, tier by tier.
- Whitelabel WhatsApp CRM onboarding checklist for resellers — the Day-1 to Day-30 reseller onboarding playbook.
Written by Rakshit Soni, co-founder at LotsOfCode Private Limited and creator of Lion CRM, with about four years building WhatsApp automation tooling and working directly with whitelabel resellers. If you have a question this guide didn’t answer — about the WABA route, the Chrome-extension route, or the reseller flow — the fastest channel is WhatsApp to Kuldeep, co-founder, at +91 74260 34448.