Scaling WhatsApp to 1,000 numbers in Meta Portfolio - any shortcuts?

sophiasaas

Running a WhatsApp BSP for a retail client and they've got a wild use case: each salesperson uses a dedicated smartphone with the WhatsApp Business app. for the initial rollout they need exactly 1,000 phone numbers via the coexistence setup inside their verified Meta Business Portfolio.

Default WABA cap is 20 numbers. I've been digging into how to actually get 1,000 approved. From what I've gathered, the support portal is useless - tickets just bounce around. you need a direct Meta sales rep who can approve a custom phone number limit increase tied to the WABA. The coexistence part (linking existing Business app numbers to the API) is done number by number, so the real bottleneck is the limit, not the registration flow itself.

Even getting 50-100 approved took a colleague weeks of back-and-forth. At 1,000, Meta will almost certainly want a business justification doc showing the use case and rollout timeline.

Does your client have an existing Meta rep, or are you going purely through BSP support? keen to hear if anyone's cracked this at scale without pulling teeth.

dailygrind

You need a proper Meta Business Partner (not just a reseller) in your market. Here's the process I'd follow:

Check the official Meta Business Partner directory - filter by "Business Solutions" and your country. Most partners who can provision 1,000+ WABA numbers will be in the "Enterprise" tier.
Ask for their WABA onboarding flow upfront - a serious partner doesn't just hand you a CSV, they run a verification pipeline, check your use case, and handle the 2FA phone verification at scale. If they say "upload a file and we'll figure it out," run.
Test with a small batch first - I'd send 50 numbers through their process and monitor the approval rate in the Business Portfolio's "Phone Numbers" tab. If more than 5% get flagged, the partner doesn't have the right pre-verification relationship with Meta.

We ended up having to switch partners twice before we found one that could actually maintain a 99% success rate on bulk registrations. The tooling matters more than the price.

ctrjunkie

Yeah, 1,000 numbers isn't a standard ticket request. Meta's Business Manager doesn't have a UI flow built for that kind of scale - you're not missing a hidden button or anything.

You'll need to go through a direct Meta sales rep, not the support portal. The support tickets will just bounce you around endlessly. A rep can approve a custom phone number limit increase tied to your WABA. The whole business of linking existing WhatsApp Business app numbers to the API is handled one by one, so the real bottleneck isn't the registration process itself, it's hitting the cap.

Honestly, even getting 50-100 approved took us back-and-forth over a few weeks. At 1,000, expect Meta to ask for a proper business justification document - your use case, rollout timeline, the works.

Does your client already have an existing Meta rep, or are they going purely through BSP support?

chatbox

I've been through this exact headache. virtual numbers are the way to go-no way I'm managing 1,000 physical SIMs. 2Chat works, but here's the process I'd follow:

Grab virtual numbers from 2Chat (or a similar provider) - they're cheap and disposable.
Register each one on the WhatsApp Business app or API using their guide.
Link them into your Meta Business Portfolio via the WABA flow.

One gotcha: make sure each number is unique per business portfolio account to avoid account quality penalties. If you're scaling above a few hundred, consider a dedicated API partner like WATI or Twilio for better management dashboards. The 2Chat tutorial is solid for the basics though.

storyweaver

Oh, you sweet summer child. If you're a BSP, you should already have a Meta handler - find them and gently harass them. If you don't have one, crack open a support ticket and prepare to wait for the heat death of the universe. they're famously useless at handling these through tickets, which is why everyone tells you to hunt down your Meta rep instead.

And if you're not a BSP and you're trying this with some dodgy unofficial library, you wouldn't be asking this question because you'd already know it's a disaster waiting to happen 😂

weekendhustle

honestly, this is one of those things where you're pretty much locked into working with a Meta partner if you need that many numbers 😕. I've looked into it before for a client and there's no real way around it on the self-serve side. might be worth checking if any of the recommended partners have flexible onboarding.

logan-lifecycle

coex has definitely been throwing up some oddities lately - Meta's still ironing out the kinks on their end. I'd advise starting with a much smaller node in the journey, say the initial 20-number limit or maybe 100, and let that segment run through its full lifecycle before even thinking about scaling to 1,000. that way the client can validate the trigger logic and message volume without hitting a system block.

Inside the Meta Business account, the escalation path I've used is: Direct Support > Ask a question > Dev: Account & WABA. They'll want a clear justification tied to how long those numbers have been active and what sort of messaging volume they're carrying - that's the branch condition that usually gets the limit lifted.

coex is fine for routing, but once you've got more than a handful of numbers in play, a central team inbox to monitor conversation states across all those journey nodes becomes essential - keeps the win-back flows clean and the churn triggers visible.

trafficcop

Oh honey, 1,000 numbers? You're not getting through without Meta Direct Support holding your hand. Good luck getting them to actually reply, though.

bigcoffee

meta isn't designed to scale that way. WABA profiles are meant for business representation, not individual agent accounts. You could get away with one or two phone numbers and route conversations server-side to the relevant sales rep - that's the standard architecture.

A few things to consider:

Meta's terms explicitly discourage using WABA for personal numbers. Push for 1,000 and you're asking for compliance flags.
The backend routing approach is proven. it keeps you within policy and makes reporting / attribution much cleaner.
If you genuinely need 1,000 distinct touchpoints, you might be better off looking at a CRM integration that handles the mapping outside of WhatsApp Business API.

what's the actual use case driving the need for that many distinct numbers?

localpack

Idts that it is possible on WhatsApp rn

adcraft

Honestly, registering a thousand WhatsApp numbers in a single Business Portfolio sounds like a solution in search of a problem. Most businesses I've seen pushing that many numbers are either running dodgy broadcast operations or haven't thought through deliverability and warm-up. The official Meta partner route can help with the API setup, sure, but it won't fix the real issue: you probably don't need that many numbers unless you're spamming. Focus on fewer numbers with proper engagement rates instead.

ctrjunkie

oh, that's helpful but yeah, it's not the whole story once you hit 1,000 numbers.

A Meta Business Partner can get you faster escalations and direct support tickets, absolutely. But the limit increase still goes through Meta's own internal review - no partner can guarantee timelines. We sat on our hands for three weeks just to expand by 200 once.

The real trick is the coexistence setup. each number has to be migrated or registered individually, and Meta sometimes flags bulk requests. So batching in groups of 50-100 is way safer than one massive ticket.

A good partner shortens the back-and-forth. doesn't magically remove the process

sophiasaas

Had a client with a rep, and honestly, the multi-portfolio headache is real - each one requires its own separate limit increase request. Really kills the velocity when you're trying to scale WhatsApp numbers efficiently.

dailygrind

Exactly. No bandwidth for bulk verification - scheduling 1,000 numbers is messy. Kudos for starting early.

ctrjunkie

Yeah, threads move fast round here.

the batching advice someone else gave is the real takeaway. throwing in a single ticket for 1,000 numbers is practically asking Meta to flag it. Breaking it into batches of 50-100 over separate tickets, spread over a couple of weeks - that's what I've seen actually get through review smoothly.

something else people overlook: each number in a coexistence migration still needs individual OTP verification on the physical device. With 1,000 numbers, the ops side of coordinating all that device-side verification is honestly tougher than getting the limit increase itself.

has your client got someone lined up to handle that device-level verification at scale?

sophiasaas

Yeah, we ran into this exact bottleneck scaling from a few hundred numbers up to around 2,000. The limit increase requests are a nightmare-each one feels like a lottery. If you can get Meta to grant a large limit up front, do it. We didn't, and the back-and-forth wasted weeks. Just make sure your documentation (business verification, use case) is airtight, because they'll ask for it anyway. Better to over-prepare than to keep hitting the cap mid-campaign.

ctrjunkie

Honestly, if there's any chance this client is going to scale, push for more than 3,000 from the start. Meta makes second and third approvals painful, and you don't want to be stuck in that loop.

The justification you send with the support ticket matters way more than you'd think. One use case per salesperson, a dedicated device, and a retail ops context - that framing's worked better for me than just vague volume requests.

Also, budget 4 to 6 weeks for this. Even clean portfolios with good standing take time on approvals at this scale.

Ask for headroom now. Future you will be grateful.