setscale

WhatsApp Business API for teams: 8 rules before setup

August 13, 2026·16 min read
Man in his early thirties reviewing the WhatsApp setup of a client account with his team, short beard, grey blue chambray shirt, standing in a converted attic office with a sloped wooden ceiling, warm table lamps and a large window at dusk, phone in one hand and a second screen behind him

The WhatsApp Business API for teams gives you a channel, not a shared inbox: several agents can only work the same number through a partner product or an internal build, and the sending quota that governs them is held at business portfolio level rather than per number. Every rule below follows from those two facts. Most teams find that out in month two, because they connect WhatsApp the way they connected email: someone plugs in a number, the messages arrive, and the problems appear three weeks later. A client campaign eats a quota nobody knew was shared. A reply lands nineteen hours late and suddenly costs money. An agent cannot open the inbox because there is no inbox.

This is written for the person who runs several closers or several client accounts and is about to put WhatsApp under that structure: agency owner, head of sales, ops manager. Below are the eight rules of the WhatsApp Business API for teams that are cheaper to settle before setup than after, each one taken from the official platform documentation rather than from vendor marketing. Every figure here is sourced and linked, and the ones that move are flagged as such.

TL;DR

  • The API gives you a channel, not an inbox. Multiple agents means a partner tool or something you build, and that is where the per seat bill starts.
  • Messaging limits are set at the business portfolio level and shared by every business phone number in it, so one client account can consume the capacity of all the others.
  • A new portfolio starts at 250 unique users per 24 hours outside a service window. Getting to 2,000 is a deliberate move, not a wait.
  • A user message opens a 24 hour customer service window. Inside it you write freely, outside it you can only send pre approved templates.
  • Since 1 July 2025, Meta charges per delivered template message, and rates depend on the template category and on the recipient country calling code.

Table of contents

What the WhatsApp Business API for teams actually is

The WhatsApp Business Platform is an interface, not an application. You register a business phone number, you send and receive messages through the Cloud API, and everything a human would recognise as a product (a conversation list, assignment, notes, reporting) is built on top by you or by a partner.

That single fact explains most of the disappointment teams report in month two. They compare it to the WhatsApp Business app, which is a phone application, and expect the same experience with more seats. What they get is a channel with rules, quotas and a billing model attached.

The rules below follow the order in which they hurt. Numbers first, because they are hard to undo. Then the quota that is shared without anyone telling you. Then the clock, the consent, the invoice, the inbox and the quality signal that quietly caps everything else.

Rule 1, pick a number you can dedicate to the platform

A business phone number must be registered before it can send or receive through the Cloud API, and registration takes it away from ordinary use: a registered number can still take calls and SMS, but it can no longer be used with WhatsApp Messenger. A number already in use on WhatsApp has to be deleted from WhatsApp first, and a banned number has to go through the appeal process before anything else.

Eligibility is narrow enough to catch people out. The number must be owned by you, must have a country and area code (short codes are not supported) and must be able to receive a voice call or an SMS. Meta's own table on business phone numbers rates mobile numbers as the standard case for receiving the one time code, and marks fixed line, VoIP, toll free and personal numbers as not recommended for SMS delivery of that code.

For an agency the practical consequence is a procurement decision, not a technical one. If the number belongs to the client, the client can take the channel back on the day the retainer ends, and the message history goes with it. If it belongs to you, you carry a number your client cannot easily replace, which is a commercial position you should choose on purpose rather than discover.

Verdict: decide the ownership of every number before registering it, and never register the personal mobile of a founder or a closer.

Rule 2, remember the messaging limit is shared

This is the rule that surprises multi account teams, and it is stated plainly in the documentation. Messaging limits are the maximum number of unique WhatsApp user phone numbers you can deliver messages to, outside a customer service window, within a moving 24 hour period. They are calculated and set at the business portfolio level, and they are shared by all business phone numbers in that portfolio.

Read the second sentence again with ten client accounts in mind. One number can consume the whole portfolio's capability inside a given period, which means a single client running a promotional push on a Tuesday morning can leave the nine others unable to open conversations that afternoon. Nobody receives an alert saying "client B took your quota".

The messaging limits documentation also notes that the old messaging_limit_tier field has been deprecated in favour of whatsapp_business_manager_messaging_limit, so any internal dashboard built before that change is reading a field that no longer answers. The limit is also visible in WhatsApp Manager under Account tools, then Messaging limits.

The operational answer is boring and effective: publish the daily outbound allowance per client account as an internal rule, book campaign days in a shared calendar, and treat the quota as a resource you allocate rather than a ceiling you hit. The same discipline that keeps ten inboxes from colliding in the multi account playbook applies here, except the collision is invisible until it happens.

Verdict: allocate the portfolio quota per client account in writing, or the loudest client will allocate it for you.

Rule 3, plan the climb from 250 to 2000

A newly created business portfolio has a messaging limit of 250. That is enough to test, and not enough to run a client base. The path upward is documented and deliberate.

Limit How it is reached What Meta checks
250 Default for a new business portfolio Nothing, it is the starting point
2,000 A scaling path: verify your business, have your partner verify it if you were onboarded by one, or deliver 2,000 messages outside service windows to unique users within a moving 30 day period using templates with a high quality rating Message quality is analysed, then the request is approved or denied
10,000 Automatic scaling High quality messages across all numbers and templates, and at least half the current limit used in the last 7 days
100,000 Automatic scaling Same criteria
Unlimited Automatic scaling Same criteria

Two details matter for planning. Once the criteria are met, the limit moves up one level within six hours, so the climb is fast when it is earned. And automatic scaling requires you to have used at least half of your current limit in the last seven days, which means a portfolio that stays cautious stays small.

Business verification is therefore the cheapest of the two scaling paths for most agencies, because the alternative asks you to deliver two thousand messages outside service windows on high quality templates before you have earned the right to send them comfortably. Start the verification file the same week you register the first number, not the week you need the capacity.

Verdict: verify the business early, then keep usage above half the current tier so automatic scaling has something to work with.

Rule 4, build the rota around the 24 hour window

When a user messages you or calls you, a 24 hour timer starts, called a customer service window. While it is open you can send free form messages, and they do not need pre approval. If the user writes again before it expires, the timer resets. When it closes, you can only send pre approved template messages, as the guide on sending messages sets out.

For a sales team that changes the meaning of a slow reply. On email, a late answer is a courtesy problem. Here, a lead who wrote at 9pm on Friday and gets an answer at 10am on Monday has moved into template territory: the free form conversation is over, and the reply now has to fit a format approved in advance. The channel converts your staffing gaps into a different message type.

That is why the window belongs in the rota rather than in the tooling discussion. Our seven rules for a lead response time SLA cover how to write a target that someone can actually be held to, and the same arithmetic applies here with a hard platform boundary at the end of it. If your inbound comes from paid campaigns, the entry conditions are covered in our piece on click to WhatsApp ads.

Verdict: staff the first four hours after a message lands, because the window is a constraint and not a service standard you chose.

Rule 5, collect opt in before the first message

Businesses are required to obtain opt in before messaging people on WhatsApp. Following the November 2024 update of the WhatsApp Business Messaging Policy, the permission can be general rather than WhatsApp specific, as long as local law is respected, and it rests on two conditions: the person gave their mobile number, and they confirmed they want to receive messages or calls from that particular business.

The requirements Meta lists on getting opt in are short and worth quoting in your own client contracts. State clearly that the person is opting in to receive communication. State clearly the name of the business they are opting in to hear from. Comply with applicable law. The method itself is open: SMS, website, an IVR flow, or a paper form signed in person.

For an agency, the word "particular" is the one that costs money. Consent given to your client is consent for your client, not for the agency, and not for the next client on the same portfolio. Keep the proof of consent inside the client account, with a date and a source, so that a complaint can be answered with a record rather than with a memory. The compliance load is the same one that shapes the white label version of the service, where your name is not the one on the message.

Verdict: store consent per client account with date and source, and never move a list between two accounts.

Rule 6, know what a message actually costs

Since 1 July 2025, Meta charges on a per message basis, and only when a template message is delivered. Rates vary with two variables: the category of the template, and the country calling code of the recipient. The pricing documentation is the only place worth reading on this, because it is also where the exceptions live.

Three of those exceptions matter for a setting operation. Non template messages have not been charged since 1 November 2024, and they can only be sent inside an open customer service window. Utility templates sent in response to a user, inside an open window, have not been charged since 1 July 2025. And all messages, templates included, are free for 72 hours inside an open free entry point window.

Put together, the economics reward the same behaviour the rota does. Conversations that a user starts, answered while the window is open, cost nothing to continue. Conversations you start from a cold list are charged per delivered template, in a currency that depends on where the person lives. If you are modelling the cost of a channel against the cost of a team, the three routes and what each really costs lays out the same arithmetic for setting as a whole.

One caveat, because this page moves: Meta has announced pricing updates for service and utility messages landing on 1 August 2026 and 1 October 2026. Re read the pricing page before you commit a margin to a client, rather than trusting a figure copied from a blog, including this one.

Verdict: price inbound and outbound separately, and re read the official pricing page every quarter.

Rule 7, decide who holds the shared inbox

The platform does not ship an inbox. Two agents cannot open the same conversation list unless something sits between them and the API, which is either a partner product or an internal build. This is the line where the WhatsApp Business API for teams stops being a technical subject and becomes a budget.

Partner pricing is published, and it is worth reading in seat terms rather than in plan terms. On the official pricing pages checked on 24 July 2026, Respond.io includes 5 to 10 users depending on the plan and charges roughly 12 to 24 US dollars for each additional seat. GoHighLevel treats WhatsApp as an add on billed 10 US dollars per month per sub account, on top of the subscription. AiSensy, whose pricing page is published in Indian rupees, includes one owner plus five agents and charges 750 rupees per month per additional agent, with Meta template costs on top.

The pattern is more useful than any of the three figures. Seats are the growth variable, sub accounts are the multiplier, and the platform fee is charged separately from the messages. That is exactly the structure that makes tooling budgets drift, which we took apart in detail in the real cost of an all in one platform.

Verdict: model the inbox at your headcount in twelve months, per client account, including message costs, before you sign anything.

Rule 8, watch quality before you chase volume

Quality is the throttle behind every other rule. Meta states that its systems will rate limit a business whose quality is low for a sustained period, and it advises monitoring the quality rating in particular when rolling out a new opt in method. Scaling paths and automatic scaling both depend on templates with a high quality rating.

For a team, quality is not an abstraction, it is the sum of small operational choices: how fast the first reply lands, whether the person expected the message, whether the opt out instruction is honoured, and whether the setter on the late shift is sending the same thing as the setter on the early shift. Those choices belong to a QA loop, and they are the part of the setter and closer model that survives any change of channel.

Check the current limit before every campaign, either in WhatsApp Manager under Account tools, or through the API by requesting the whatsapp_business_manager_messaging_limit field. It takes a minute and it prevents the failure mode where a client campaign silently stops halfway through the list.

Verdict: treat the quality rating as a production metric with an owner, not as a Meta detail.

Where SetScale fits

SetScale is an AI setter for teams and agencies: several client accounts, several closers, reporting per seat, with a white label direction. Nothing above depends on it, which is why the rules are written from the platform documentation and not from our roadmap.

The honest summary is this. The eight rules solve themselves for a single account with one person answering. They become an operating problem when the same quota, the same clock and the same quality rating are shared across ten accounts and three closers, and that is the shape of the problem we are building for. The wider argument sits in the infrastructure view of setting, and the closer side of the same team is covered in keeping closer calendars full.

The product is not open yet, so there is nothing to buy today. If you want to hear when it is, Join the waitlist.

FAQ

Can several agents answer from the same WhatsApp number? Not with the platform alone. The Cloud API sends and receives messages, it does not provide a conversation list, assignment or notes, so a team needs a partner product or an internal build on top of it. That layer is where per seat pricing appears.

Do I need a separate number per client account? Technically you can run several business phone numbers in one business portfolio, and many agencies do. Remember rule 2: the messaging limit is set at portfolio level and shared across those numbers, so separation of numbers is not separation of quota.

Is the WhatsApp Business app enough for a small team? It depends on whether you need programmatic sending. A number registered for the Cloud API can no longer be used with WhatsApp Messenger, so the choice between the app and the API is a fork rather than a step, and it is worth making once rather than twice.

What happens to my messaging limit if one client sends a large campaign? It is consumed. The documentation states explicitly that a single business phone number can use all of the portfolio's messaging capability in a given period, which is why campaign days belong in a shared calendar.

How quickly can we reach the 2,000 tier? As soon as a scaling path is completed and message quality is analysed favourably. Business verification is usually the faster route for an agency, since the alternative requires delivering 2,000 messages outside service windows on high quality templates within a moving 30 day period.

Does answering an inbound message cost anything? Non template messages sent inside an open customer service window have not been charged since 1 November 2024. Outside that window, only pre approved templates can be sent, and delivered templates are charged by category and by recipient country calling code.

Conclusion

The WhatsApp Business API for teams is not a difficult channel, it is a channel with a small number of hard edges that are all documented in advance. Numbers cannot be recycled, the quota belongs to the portfolio rather than to the number, the clock starts with the customer, consent is per business, templates are what you pay for, the inbox is your problem, and quality gates the rest.

Settle those seven points before the first campaign and WhatsApp behaves like a well run channel. Skip them and you discover each one on the day it costs a client relationship. If you are building the version of this that runs across several client accounts and several closers, Join the waitlist.