waplyGuide
Meta Business and WABA verification for Kommo
Meta Business verification proves your business portfolio belongs to a legitimate legal entity — it is separate from creating a WABA, approving a display name, or getting an Official Business Account. Soft-word: you can often create and use a WhatsApp Business Account before verification finishes, but verification (and related Meta readiness) commonly matters when you migrate numbers, add more lines, or scale messaging. Follow Meta Business Help for the live steps — Waply does not run Meta’s review or guarantee approval.
For new businesses, agencies, and Kommo admins, Meta Business and WABA readiness is the usual bottleneck before a clean Cloud API connection or a migration. This guide is a practical checklist: what to prepare, what must match, which permissions matter, and how to read pending states — without inventing Meta rejection codes or review timelines.
Free 3-day trial with everything in Voice AI.
Who this is for
Use this guide if Meta Business verification, WABA status, or asset permissions are blocking your Kommo WhatsApp setup with Waply on official Cloud API.
- New businesses connecting WhatsApp Cloud API to Kommo for the first time.
- Agencies preparing client Meta portfolios, documents, and admin access before go-live.
- Kommo admins migrating from another provider or stuck on pending / rejected verification states.
What “verification” means (Business vs WABA vs display name)
Teams often use “verification” for several Meta steps. Soft-word the labels — Meta UI names change — and treat these as different processes:
Related Meta steps (soft-word — confirm labels in Meta Business Suite / WhatsApp Manager)
| Step | What it roughly is | Why it matters for Kommo / Waply |
|---|---|---|
| Meta Business verification | Confirms the business portfolio belongs to a registered legal business and that you can represent it | Often needed for migration paths, more phone numbers, and certain WhatsApp Platform features |
| WABA (WhatsApp Business Account) | The WhatsApp account under your portfolio that owns numbers, templates, and messaging | Required to send/receive on Cloud API; can often exist before business verification completes |
| Display name approval | Meta review of the name customers see on WhatsApp | Separate from business verification; soft-word timing — check WhatsApp Manager |
| Official Business Account (OBA) | Separate eligibility path (includes a verified portfolio among other Meta criteria) | Not required to start messaging in Kommo with Waply; soft-word and read Meta OBA docs if you need the badge |
Soft-word: Meta Business verification is different from Meta Verified for businesses and does not grant a verified badge by itself. Always recheck Meta Business Help for the current flow.
When verification usually becomes the bottleneck
You do not always need a fully verified portfolio on day one — soft-word and confirm live Meta/Kommo docs for your case. Verification commonly becomes critical when you:
- Migrate a number into Kommo / Waply from another Cloud API host: Kommo documents prerequisites such as a verified Meta Business, an approved WABA, a valid payment method on the existing WABA, and two-step verification disabled on the number when Meta’s migrate path requires it.
- Need more than the starting phone-number capacity: Kommo cites Meta that unverified portfolios can start with up to about 2 numbers; once the business is verified or you reach a messaging limit on the order of ~2,000, that number capacity can increase (soft-word — confirm live).
- Scale business-initiated messaging: Meta messaging limits and quality rating interact with verification and portfolio health — see the limits & quality guide.
- Hit pending Meta verification or missing asset permissions while connecting in Waply: the number may not become ready until Meta/portfolio access is fixed.
Checklist before you submit or migrate
Complete this list before you start verification in Meta Security Center or begin a number migration. Soft-word every Meta click path — menus move; the Help Center is the source of truth.
- Confirm you (or the client) have Admin / full-control access on the correct Meta Business portfolio and a personal Facebook login that can open Business Suite.
- Fill Business Info so legal business name, address, phone, and website match the legal entity exactly (including suffixes such as Ltd / Limited).
- Prepare official documents that show the legal name and either the official mailing address or the business phone — soft-word accepted types; Meta Help lists current document categories.
- Make sure the business website loads over HTTPS and reflects the business identity (soft-word: Meta may reject sites that fail to load, are not HTTPS, or lead to broken links).
- For migrations: confirm WABA approved status, a valid payment method on the existing WABA, and that two-step verification can be disabled on the number if Meta’s path requires it.
- Align agency vs client ownership: install and verify under the accounts that should own the assets long term; do not leave critical assets only on a temporary agency login.
- Only then start or resume verification in Meta Business Suite Security Center and follow on-screen prompts — never invent a custom document pack that Meta did not ask for.
Pending states and common blockers (soft-word)
When setup stalls, read the Meta UI status first. Soft-word: do not treat forum lists as Meta’s official rejection taxonomy, and never assume a fixed review SLA.
- Ineligible for verification / cannot start: complete Business Info, confirm portfolio eligibility in Security Center, and follow Meta Help — soft-word; eligibility rules are Meta’s.
- Verification pending / in review: wait for Meta’s result in Business Suite; Waply cannot accelerate Meta’s review. Soft-word — no promised number of days.
- Rejected: open Meta’s explanation in Security Center. Meta Help cites themes such as false or misleading information, claiming a business you are not authorized to represent, attempting to circumvent review, or a website that fails to load / is not HTTPS / has broken links. Fix the underlying mismatch, then resubmit only when Meta allows it.
- Operational checks teams often make (soft-word, not invented Meta codes): legal name or address does not exactly match the document; uploads are cropped, blurry, or the wrong document type; personal tax returns or marketing materials instead of official business records.
- Missing asset permissions: the Facebook user connecting Waply lacks Admin access to the portfolio, WABA, or phone number asset.
- Payment method missing on the WABA during migration: Kommo/Meta flows can fail until Billing is valid on the existing WhatsApp account.
- Two-step verification still on during migrate: disable it in WhatsApp Manager when Meta’s migration path requires it (re-enable afterward per Meta guidance).
- Coexistence vs new WABA confusion: coexistence can keep messaging on the Business app + Cloud API; WhatsApp calls are not supported on coexistence (Meta). Verification still follows Meta’s business rules either way.
Soft-word caveat: Meta’s exact UI labels, document lists, and review outcomes change. Prefer Meta Business Help links over third-party checklists when they disagree.
How Waply fits (official API — Meta reviews verification)
Waply is an independent product in Kommo on Meta’s official Cloud API: messaging, human WhatsApp calls on eligible platform-only numbers, call intelligence, and text/voice AI on third-party models (not Kommo native AI credits). Waply does not sell grey QR sessions and does not perform or guarantee Meta Business verification.
Waply plans (USD, waply.online/pricing)
| Plan | Monthly | WhatsApp-relevant inclusions |
|---|---|---|
| Basic | USD 18 | Official-API messaging; human WhatsApp calls and recordings (90-day retention) |
| AI 24/7 | USD 39 | Everything in Basic + text AI agents, call intelligence allowances, 365-day retention |
| Voice AI | USD 89 | Everything in AI 24/7 + Voice AI agents on WhatsApp calls (managed/BYOK minutes) |
- Free 3-day trial includes everything in Voice AI.
- Pending Meta verification or missing permissions can keep a number from becoming ready — soft-word; fix Meta/portfolio access first.
- Coexistence numbers: messaging can work; WhatsApp calls do not (Meta restriction).
- Meta conversation/message charges are separate from the Waply subscription.
Frequently asked questions
Do I need Meta Business verification before I can use WhatsApp in Kommo?
Soft-word: you can often create a WABA and start on Cloud API before business verification finishes. Verification commonly becomes required for migration paths, higher phone-number capacity, and some platform features. Confirm live Meta and Kommo docs for your case.
Is Meta Business verification the same as WABA verification or a blue badge?
No. Business verification confirms the portfolio’s legal business. A WABA is the WhatsApp account under that portfolio. Display name approval and Official Business Account are separate. Soft-word: business verification is also different from Meta Verified for businesses.
Which documents does Meta accept?
Soft-word: Meta asks for official documents that validate your legal business name and your official mailing address or business phone. Accepted categories are listed in Meta Business Help and can change — do not rely on a blog’s fixed list.
Why was my Meta Business verification rejected?
Read Meta’s reason in Security Center. Meta Help cites themes such as false or misleading information, unauthorized claims on a business, circumventing review systems, or website problems (fails to load, not HTTPS, broken links). Soft-word: fix mismatches and resubmit only when Meta allows — Waply cannot override Meta’s decision.
How long does Meta Business verification take?
Soft-word: Meta does not publish a fixed SLA that Waply can promise. Watch status in Meta Business Suite and respond if Meta asks for more information. Never treat a blog’s “X days” as a guarantee.
What does Kommo require to migrate a number from another provider?
Kommo documents that automatic migration typically needs a verified Meta Business, an approved WABA, a valid payment method on the existing WABA, and two-step verification disabled on the phone number when required. Confirm the current Kommo support checklist before you disconnect the old host.
Can Waply verify my Meta Business for me?
No. Waply connects Kommo to official Cloud API and surfaces connection state. Meta reviews business verification. Pending Meta verification or missing asset permissions must be resolved in Meta / correct admin access.
What does Waply cost and is there a trial?
Basic is USD 18/month, AI 24/7 is USD 39/month, Voice AI is USD 89/month. The free 3-day trial includes everything in Voice AI. Meta and BYOK charges are separate when applicable.
Clear the Meta checklist, then connect on official Cloud API
Match legal data to official documents, fix permissions and payment readiness, and follow Meta Business Help for live verification steps — soft-word every timeline and rejection guess. Then connect WhatsApp in Kommo with Waply on official Cloud API. Try everything in Voice AI free for 3 days when you are ready.
Free 3-day trial with everything in Voice AI.