Framework for WhatsApp API in two-sided marketplaces

noahcontent

Building a marketplace called Tarea and WhatsApp is central to the pro experience. I'm treating WhatsApp as the primary notification channel alongside email and SMS - think booking confirmations, new messages, quote approvals. The goal is also to let pros send marketing broadcasts, similar to email/SMS campaigns.

I'm putting together a framework but hitting some gaps. Here's where I need community input:

Channel viability: WhatsApp's read rate is high, but are there hidden costs or friction for the pros themselves? Any UX gotchas?
Template classification: Utility vs marketing - utility notifications are cheap and deliver well, but marketing templates have a 50-60% delivery rate and need separate approval. How do you classify borderline use-cases like a booking reminder with a promo upsell?
Multi-tenant architecture: Each pro should own their number, opt-in list, and reputation - not pool them under a shared number. This isolates spam signals. But what about account structure: individual WABAs per pro vs a single WABA with multiple numbers? The wrong call early can haunt you.
Broadcast infrastructure: If pros provide their own lists, but send through the platform's number, the spam analysis hits that shared number. That's a risk. How have others handled broadcast isolation?
Templates and opt-in: Opt-in is non-negotiable. Meta expects it. But what's the best flow for getting opt-in for both utility and marketing? And template approval can take 24-72 hours - that delay needs to be in the launch timeline.

For tooling, I've looked at Interakt, WATI, and Waplify.io. But geography changes the recommendation - my pros are based in India and the UK. Any BSP suggestions for those regions?

Would love frameworks, war stories, or even a template of what you wish you'd known before diving in.

adcraft

This is exactly the kind of advice that sounds fine on paper but falls apart when you try to scale it.

I've actually run WhatsApp integrations for a mid-size marketplace, and the template approval process is a joke. One rep tells you it's fine, then two weeks later another one blocks it because of a minor wording change. The 24-hour window is even worse for multi-tenant setups because you end up racing against the clock to squeeze in every update before the door shuts.

And the opt-in requirements? Sure, they're important, but expecting each business on the platform to manage their own account and get proper consent is a logistics nightmare. most merchants can barely keep their email lists clean.

Frankly, I'd argue that starting with transactional first is the wrong move if your goal is retention. Notifications don't drive loyalty-marketing can, but WhatsApp is a terrible channel for that at scale. you're better off using a push notification or an in-app message that doesn't come with a ticking clock and a quality rating.

People hype WhatsApp because response rates are high, but the compliance headache kills any upside when you're running more than a handful of accounts. Maybe it works for a single business. For a marketplace? Hell no.

miaaffiliate

Yeah, WhatsApp's read rate absolutely crushes email-no debate there. If you're pushing notifications for high-ticket offers or CPA funnel follow-ups, it's the only channel that actually cuts through the noise.

Biggest headache is template classification. Marketing templates can tank at around 50-60% delivery depending on how fresh your number is. You need to get those templates tagged as utility wherever possible or the margins get shredded by low deliverability.

Multiple business broadcasts are doable, but the real question is whose number is driving the broadcast and where the opt-in list came from. If a business hands you their list but you're blasting from your own number, that spam analysis hits your reputation hard. Not worth burning a clean number on someone else's list.

Only hard requirement: capture every "Stop" reply and remove them immediately. One missed opt-out and you'll get flagged, and that'll cost you way more than any revenue from that segment. Keep it clean or don't bother.

ctrjunkie

Multi-tenant WhatsApp setups are definitely achievable, but honestly? the account structure decision is the kind of thing that'll sneak up and bite you months down the line if you don't nail it early.

from everything I've seen talking to folks building marketplace-style platforms, the cleanest route is giving each pro their own WABA (WhatsApp Business Account) linked to your platform. they keep ownership of the number, the reputation, the opt-in list. you're just orchestrating via API. That way spam signals stay isolated per business - not pooled across your whole platform and putting everyone at risk.

For transactional stuff like booking confirmations, run those as utility templates. cheaper, way better delivery rates. marketing broadcasts need separate template approval and a proper opt-in flow. don't skip that opt-in - Meta takes it seriously, and your deliverability will tank if you cut corners.

The quiet one nobody warns you about: template approvals can take 24 to 72 hours. build that delay into your launch timeline. It's brutal.

for tooling, I've heard good things about Interakt, WATI, and Waplify.io - worth testing a few before settling on your BSP layer.

also curious - what geography are your pros in? that can shift which BSP works best

ethan-pr

I use Qordinate.ai to boost my productivity on whatsapp

ctrjunkie

Oh, the number ownership thing is such a hidden trap. So many people building multi-tenant setups just grab one shared number and slap it across all their business accounts. Then one spammy client tanks the reputation for everyone on that number - it's brutal.

The cleaner way is giving each business its own WABA and its own number. More work upfront, I know, but keeps that spam signal isolated. No shared misery.

And yeah, the Stop replies point cannot be overstated. Seen teams ignore it early on, then within weeks Meta quietly throttles delivery. It's not a maybe - it happens.

One thing I'd add: utility templates getting reclassified as marketing by Meta mid-campaign is way more common than people expect. Always worth building a review step before launching new templates, because that catch can cost you days of approvals.

dusting

Starting in the Caribbean, then South America - that changes the WhatsApp integration landscape. How are you adapting?

miaaffiliate

Yeah, that's the thing. every BSP I know has moved to the Cloud API, so you're looking at Meta's embedded sign-up and their approval on every brand and template. no chance of BSP approval at scale anymore.

ctrjunkie

people don't always realise how much the Caribbean and LatAm change the BSP shortlist. most business solution providers are optimised for India or Europe, but for LatAm you really want a provider with local payment options and a support team who actually gets the region. twilio and 360dialog have decent coverage down there. From what I've heard, 360dialog is a solid pick for multi-tenant setups because of how they handle WABA onboarding at scale.

The bigger headache for a Caribbean launch is phone number verification - it can get messy when pros are using numbers across different country codes. make sure your onboarding has some flexibility built in for that.

What carrier spread are you expecting across your pro base?