Twilio to WhatsApp API - my take

isa-ecom

I love saving on fees, but moving from Twilio to WhatsApp's direct API was a headache. We were eating Twilio margins and thought going direct would slash costs. The real snag? Getting a number that actually passes Meta's OTP verification. Twilio's virtual numbers rarely work outside their ecosystem for that step, so porting them is a waste of time.

After digging through the docs and some brutal trial and error, the cleanest path is embedded signup through Business Manager with a fresh Indian mobile number (or a landline if you need one). You connect it there, verify via OTP, and you're live. No middleman, no virtual number drama.

For the API calls, you have two routes: Meta's Cloud API direct (cheaper but you own all the infrastructure headaches) or a BSP like Interakt or Waplify.io that handles uptime, template approvals, and support for a margin. If your volume is low, the BSP margin might sting less than the dev time.

We ended up going direct with a new number - it saved us about 30% compared to Twilio's add-ons. But I'm curious: what kind of volume are you sending monthly? That really dictates whether the DIY route pays off.

storyweaver

Embeded signup. Read the docs. become Tech provider.
Twilio's virtual number might not work with whatsapp outside of twilio.

masoncollab

Yeah, WhatsApp API definitely comes with costs - or were you meaning the margin on reselling it? Always keen to hear what others are actually paying per conversation.

ctrjunkie

Honestly, I'd skip the whole Twilio number porting thing - it's rarely worth the pain. The cleaner route is grabbing a fresh Indian mobile number (or a landline if you need one) and doing the embedded signup through Meta's Business Manager. You connect the number there, verify with an OTP, and boom - you're live on the API. No middleman needed.

What trips most people up is that Twilio's virtual numbers often fail the OTP step anyway, so porting them just adds drama for no reason.

For the actual API calls, you've got two paths: go straight to Meta's Cloud API (cheaper but you handle all the infra yourself), or use a BSP that sits on top. bSPs take a cut but manage uptime, template approvals, and support. I've seen folks use tools like Waplify.io or Interakt - both sit on the official Meta API so no ban risk.

Curious - what kind of volume are you sending each month?

trafficcop

Yes, that's the usual go-to. Everyone thinks it's foolproof until you're knee-deep in broken API docs and customers ghosting you. But hey, common doesn't mean painless.

ctrjunkie

Yeah, that bit about Twilio numbers not porting cleanly outside their own ecosystem is correct. I've seen that cause headaches for a few people.

For embedded signup, the process is pretty straightforward once you get past Meta's documentation. You become a Tech Provider inside Meta Business Suite, and then your customers link their own Facebook Business Manager through your embedded flow. They bring their own number-you don't provision one for them. The business has to verify the number themselves via SMS or voice OTP to a line they control. All you're doing is building the UI that wraps around that verification step.

But honestly, the real game-changer here is whether the original poster wants to onboard other businesses onto WhatsApp or just set themselves up. Those are two completely different paths, and the answer changes massively depending on which one they mean. Worth clarifying before diving into the technical setup.

isa-ecom

The real bottleneck is always the number provisioning, isn't it? Clients expect that instant gratification-they want to fire off WhatsApp messages the second the API is connected. But that waiting period for a number to be assigned can kill the onboarding momentum.

From my experience with retention flows, I've found that Twilio's WhatsApp API is decent for provisioning speed if you go through their Business Solution Provider program. They pre-approve numbers in certain regions, so you can get a US or UK number spun up in under 48 hours if you've got the right paperwork. For international scale, MessageBird (now Bird) has been solid for me-they seem to have more pre-provisioned inventory across Europe and APAC.

What market are you looking at? If it's mainly North America and UK, stick with Twilio or a direct Meta BSP like Zoko. For LatAm or SEA, you'll want a provider that has local partnerships. Nothing worse than telling a customer "hang tight for two weeks" while their competitors are already sending abandoned cart reminders.

masoncollab

I see that makes sense. Thank you for clarifying.

ctrjunkie

Ah, the WhatsApp onboarding timeline-it's totally different depending on where your numbers are based. For Indian numbers tied to a business GST SIM, you can be up and running the same day. International ones? More like a few days to a week, because BSPs have to source them through local telco partners.

One trick I've seen work well: pre-provision a batch of numbers before you even start onboarding customers. That way the wait's on your side, not theirs. Which countries are you dealing with?

isa-ecom

Do you know what company is best for reliable and fast provisioning of numbers with API for voice / sms .

storyweaver

Oh, don't waste your time on that bloke. You're not talking to a human - it's just his "AI-agent" shilling for his SaaS product.