Fair points, but I'd push back a little on the "happy to take requests" approach for a support tool. In my experience, scaling WhatsApp API for support means you've got to nail the deliverability side first - otherwise you're just burning through sender reputation before you even get to the support queue. Setting up proper webhook validation, handling rate limits properly, and avoiding template rejections for business-initiated messages is where most teams fall flat.
We spent a good chunk of time with a few providers during our own evaluation, and the biggest thing nobody talks about is how much the underlying carrier filtering varies by region. You can have a flawless setup but still face poor inboxing on certain mobile networks. That's where testing with real traffic and monitoring delivery logs becomes non-negotiable.
Anyway, glad to hear Waplify is working for you. Every setup has its quirks - just make sure your team has a fallback (like SMS or email) for when the API's gatekeeper decides to be temperamental.
