Skip to content
Meta Business PartnerGlossary term

WhatsApp Business Account (WABA)

A WhatsApp Business Account (WABA) is the Meta-owned container that groups everything you run on the WhatsApp Business API: your registered business phone numbers, your approved message templates, your messaging limits and your per-number quality rating. It is not the WhatsApp Business app you install on a phone, and it is not your Meta Business Manager either — the WABA lives inside a Business Manager, the way a project sits inside an organisation. For any Indian business scaling WhatsApp beyond the free app, the WABA is the single most important asset to understand, because who owns it decides who controls your numbers, your message history and your freedom to switch providers later.

Numbers, templates, quality rating, messaging limits
What it holds
Your Meta Business Manager
Lives inside
WABA ID (a numeric Meta ID)
Identifier
Multiple business numbers can share one WABA
Numbers per WABA
Should be your Business Manager, not the provider's
Ownership

In one line

A WABA is the Meta container that holds your WhatsApp API numbers, templates, messaging limits and quality rating. It should sit inside a Business Manager you own — not your provider's — so you keep control of your numbers and can change BSPs without rebuilding everything.

What a WABA actually contains

Picture the WABA as a folder Meta keeps for your business messaging. Inside it live the objects that make the WhatsApp Business API work day to day: one or more registered phone numbers, each with its own display name, Phone Number ID and independent quality rating; the library of message templates you have submitted for approval; your current messaging tier and per-number send limits; and the analytics Meta records against those numbers. Crucially, a single WABA can hold several business numbers — a retailer might keep one number for marketing broadcasts and another for order and support notifications, both under the same account. The WABA is identified by a numeric WABA ID that your BSP and Meta's APIs use to reference the whole container.

  • Registered phone numbers, each with a Phone Number ID and display name
  • Approved and pending message templates (marketing, utility, authentication)
  • Quality rating and messaging tier per number
  • Messaging limits and account-level analytics

Why WABA ownership is the decision that matters most

The single biggest mistake Indian businesses make is letting a provider create the WABA inside the provider's own Business Manager and merely granting the business 'access'. It feels faster at signup, but it quietly hands over ownership of your numbers, your approved templates and your accumulated quality history. If you later want to move to a different BSP, negotiate pricing, or simply audit who can send from your brand's number, you are dependent on that provider's goodwill. When the WABA sits inside a Business Manager you own, you hold the asset and grant your BSP partner access to operate it — a relationship you can revoke or reassign. InfiQ onboards clients this way by design: the WABA is created in your Business Manager, so you always retain the keys.

  • Owning the WABA means you control which BSP can send from your numbers
  • Templates and quality history stay with you when you switch providers
  • You can add, remove or audit user and system-user access at any time

How a WABA fits with Business Manager, the BSP and your number

It helps to see the hierarchy. At the top is your Meta Business Manager — the umbrella account for your business assets. Inside it lives one WABA (sometimes more for larger organisations). Inside the WABA sit your phone numbers. A Business Solution Provider (BSP) — a company like InfiQ that Meta has approved to provision WhatsApp API access — connects to your WABA to send and receive messages on your behalf and to bill you for usage. Business verification of the parent Business Manager, plus display-name review for each number, is what unlocks higher messaging limits and the option to apply for the green tick. Getting this chain set up correctly during onboarding is what prevents the painful re-work later.

  • Meta Business Manager → WABA → phone numbers
  • A BSP connects to the WABA to send, receive and bill
  • Business verification and display-name review gate your messaging limits

Billing, quality and the WABA in 2025 onward

Your WABA is where Meta tracks the signals that govern deliverability and cost. Since 1 July 2025 Meta bills per delivered message by category — marketing, utility or authentication — rather than per 24-hour conversation, so the volume and mix of templates you send from a WABA directly shapes your monthly spend. The free 24-hour service window still lets you reply to a customer without a template charge, but it is a customer-care window, not a billing unit. Meanwhile each number's quality rating and any Meta template rejections accrue against your WABA and can throttle how much you send. InfiQ layers transparent ₹ pricing (ex-GST) on top of this, with per-category rates visible up front so the numbers on your invoice map to what you actually sent.

Common WABA mistakes to avoid

Most WABA problems trace back to a handful of avoidable errors made at setup. Fixing them early costs minutes; fixing them after you have thousands of contacts and dozens of live templates can mean number migration and lost history.

  • Letting the WABA be created in the provider's Business Manager instead of your own
  • Confusing the WABA with the WhatsApp Business app — the app cannot use the API at scale
  • Skipping business verification, then hitting low messaging limits during a campaign
  • Reusing a number already active on the consumer WhatsApp or Business app without proper migration
  • Ignoring per-number quality rating until a drop triggers rate limits

See InfiQ pricing

Talk to InfiQ

See how this works on InfiQ

Tell us your use-case — we’ll show it running in a sandbox, usually within a working day.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

Is a WABA the same as the WhatsApp Business app?+
No. The WhatsApp Business app is a free mobile app for very small businesses run from a single phone. A WABA is a Meta account object used with the WhatsApp Business API, designed for automation, multiple agents, templates and higher volumes. They are separate products, and a number cannot be actively used on both at the same time without migration.
Can one WABA have multiple phone numbers?+
Yes. A single WABA can hold several registered business numbers, each with its own display name, Phone Number ID and quality rating. Many businesses keep one number for marketing broadcasts and another for transactional or support notifications inside the same WABA.
Who should own my WABA — me or my provider?+
You should. The WABA should sit inside a Meta Business Manager your business owns, with your BSP granted access to operate it. That way you keep control of your numbers, templates and quality history and can change providers without rebuilding everything. InfiQ sets clients up this way by default.
What is the difference between a WABA and a WABA ID?+
The WABA is the account container itself; the WABA ID is the numeric identifier Meta assigns to it. APIs, your BSP and Meta's dashboards use the WABA ID to reference the account when sending messages, managing templates or pulling analytics.
Does my WABA affect how much I pay for messages?+
Indirectly, yes. Meta bills per delivered message by category — marketing, utility or authentication — since 1 July 2025, and every message you send flows through your WABA's numbers. The volume and mix of templates you send, plus each number's messaging limits, determine your usage and therefore your bill.
Can I move my WABA to a different BSP later?+
If you own the WABA inside your own Business Manager, yes — you can grant a new BSP access and revoke the old one, keeping your numbers, templates and history. If the WABA sits in a provider's Business Manager, moving is far harder and may require migrating numbers, which is exactly why ownership matters at setup.
Do I need business verification for my WABA?+
You need to verify the parent Meta Business Manager to unlock higher messaging limits and to apply for the green tick. Each phone number also goes through a display-name review. Unverified accounts can start sending but are capped at lower tiers, which can cause problems during a large campaign.
What happens to my templates and quality rating if I switch providers?+
They stay attached to the WABA. As long as the WABA is in a Business Manager you own, your approved templates and per-number quality history travel with you when you connect a new BSP — nothing is re-approved from scratch.