Meta Business Manager

Why it matters for the WhatsApp Business API

On the WhatsApp Business API, almost every meaningful action traces back to Business Manager. Business Verification here is what lifts your daily messaging limits and lets you apply for a green tick (official business account). Your message templates are submitted, reviewed, and approved against the WABA that lives inside this console, so a mis-structured Business Manager can mean rejected templates or a display name that won't clear. Billing and payment methods for WhatsApp are attached at this level too — and since Meta bills per delivered message by category (marketing, utility, authentication) rather than per conversation, having a clean, verified Business Manager keeps that spend transparent and your account in good standing. Most importantly, the identifiers that make your WhatsApp presence portable — your WABA and your BSUID (Business-Scoped User ID) — are anchored to your Business Manager, so owning it is what guarantees you keep control of your numbers and history if you ever change providers.

How it works: the ownership and access model

Business Manager separates ownership from access, and understanding that split is the key to setting up correctly. Your company creates and owns the Business Manager. Inside it, you add human team members with roles (admin or employee) and you create system users — non-human accounts that hold the access tokens the API uses. When you connect a provider such as InfiQ, you don't hand over your login; instead you grant partner access or share specific assets with InfiQ's Business Manager through Meta's partner-sharing flow. This lets InfiQ manage your WABA, submit templates, and run messaging while your company retains ultimate ownership of the account, the numbers, and the BSUID. Roles and shares can be adjusted or revoked at any time from the Business Settings screen, which is exactly why the ownership structure should be deliberate from day one.

• Create the Business Manager under your company, not a personal or agency account
• Complete Meta Business Verification to unlock limits and the green tick path
• Add colleagues as admins/employees and create system users for API tokens
• Share your WABA with InfiQ via partner access rather than sharing credentials

Common mistakes to avoid

The most damaging mistake is letting an agency, freelancer, or provider create the Business Manager under their own account instead of yours. When that happens, your WABA, numbers, templates, and BSUID sit inside someone else's console — and reclaiming them can require formal Meta support tickets and, sometimes, cannot be fully recovered. Other frequent pitfalls: skipping or delaying business verification (which caps your messaging limits and blocks the green tick), sharing personal passwords instead of using proper roles and partner access, creating duplicate Business Managers for the same legal entity (which fragments assets and confuses verification), and using an individual's personal profile as the sole admin so access is lost when that person leaves. A clean, verified, company-owned Business Manager with system users and partner sharing avoids nearly all of these problems.

• Never let a provider own the Business Manager on your behalf — you own it, they get access
• Verify the business early rather than after you hit limits
• Use roles, system users, and partner sharing instead of shared logins
• Keep one Business Manager per legal entity to avoid fragmented assets and verification