We recently discovered that the native integration between Hubspot and WhatsApp Business API has a fixed pricing model, in which we need to previously by a pack of templates, and those templates expire each month, wether they're used or not. There are specific months were we use templates much more, big seasonalities, so we need to use WhatsApp with a pay-as-you-go princing model, it is more interesting for us.
We're searching for tools that provide an integration between Hubspot's HelpDesk and WhatsApp API, so we can create conversations within tickets and use WhatsApp templates in a pay-as-you-go model. It seems that is possible to connect WhatsApp's API directly into Hubspot's HelpDesk through custom channels integrations, but it seems to require a lot of development.
Dou you guys have any app indications for this use case? Some app integration that could fulfill this need. We found infobip, Sinch and Mitto, but we're trying to look for other alternatives as well.
We already support a pay-as-you-go model for WhatsApp messages, so you won’t have the issue of template packs expiring. The only fixed component is the monthly tool cost, you can see the available plans here.
Hi @Gabriel_Silva , this is a very real pain point and you’re not alone, especially with seasonal spikes. You’ve already identified the core issue correctly: HubSpot’s native WhatsApp integration is built around pre-purchased template bundles, which makes it a poor fit when usage is uneven month to month.
The recommendation from Abhinav around Vira is solid. In practice, tools like Vira, Infobip, or Sinch work because they sit on top of Meta’s actual WhatsApp pay-as-you-go pricing, then surface conversations inside HubSpot’s Help Desk using the Conversations API. That’s the key difference versus HubSpot’s native WhatsApp channel. You keep HubSpot tickets, routing, and SLAs, but you’re no longer locked into expiring template packs. In 2025, this “external provider + Help Desk surface” pattern is what most high-volume or seasonal teams end up with.
On the custom channel route, your instinct is right too. HubSpot does support custom channels for the Help Desk, but it’s not lightweight. You’d need to handle inbound webhooks from WhatsApp, map messages to conversations, manage ticket creation and associations, and send outbound replies through Meta’s API.
One practical thing I’d double-check as you evaluate apps is how they handle outbound template initiation from an existing ticket, not just inbound replies. Some tools show messages in Help Desk but still force agents to jump into the vendor UI to start a WhatsApp conversation, which breaks the workflow. Vira explicitly supports this inside the CRM card, which is a big reason it comes up often in these discussions.
Hope this helps clarify the tradeoffs a bit.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
Hi, this is a very common issue teams run into with the native HubSpot–WhatsApp setup, especially when seasonality is involved. You’re right to question the fixed template-pack model-it’s not ideal if your WhatsApp usage spikes only during certain months.
Here’s how I’d break this down based on similar implementations I’ve seen.
1) Clarifying the core requirement
From your message, your needs are very clear:
WhatsApp Business API (official, compliant)
Pay-as-you-go pricing for templates/messages (Meta conversation-based billing)
Ability to create and manage WhatsApp conversations inside HubSpot Help Desk / tickets
Minimal custom development effort
The challenge is that HubSpot’s native WhatsApp integration is intentionally limited, both in pricing flexibility and extensibility.
2) Why direct API → HubSpot custom channel is painful
Technically, yes — you can connect WhatsApp API directly to HubSpot via custom channels, but in practice this means:
Building webhook handlers for inbound/outbound messages
Managing template approvals and Meta billing yourself
Handling conversation threading, agent assignment, and ticket sync logic
Ongoing maintenance when HubSpot or Meta APIs change
Unless you have a strong internal engineering team, this usually becomes expensive and fragile over time.
3) Using a middleware platform is the practical approach
Most teams solve this by using a WhatsApp API provider + HubSpot integration layer that:
Uses Meta’s pay-as-you-go conversation pricing
Syncs WhatsApp conversations directly into HubSpot tickets
Avoids template “packs” that expire unused
You already mentioned Infobip, Sinch, and Mitto - those are solid enterprise-grade options, especially if you’re messaging at very high volumes.
4) Another alternative worth evaluating
You may also want to look at RateUp as an alternative, particularly if:
You want pay-as-you-go WhatsApp API pricing (no expiring template bundles)
Your primary use case is support + engagement inside HubSpot
You want quicker setup without heavy custom development
RateUp works as a WhatsApp Business API layer and supports:
Two-way WhatsApp conversations mapped to CRM/helpdesk workflows
Template usage billed per Meta conversation (not pre-purchased packs)
Ticket-style conversation management that can be synced into HubSpot via integration or middleware
Seasonal scaling without financial waste
It’s especially useful if your WhatsApp usage is uneven across the year, which seems to be your exact scenario.
5) How I’d shortlist tools
When evaluating alternatives, I’d strongly suggest checking:
Meta billing model (conversation-based vs template bundles)
Conversation-to-ticket mapping inside HubSpot
How template approvals and reuse are handled
Whether inbound customer-initiated conversations are supported without templates
SLA and support quality during peak seasons
If WhatsApp is becoming a core support channel for you, avoiding fixed template packs is the right call. A middleware platform that supports true pay-as-you-go Meta billing and integrates cleanly with HubSpot will save both cost and engineering effort long term.
Hope this helps - happy to share more details if you want to compare implementations or trade-offs between these options.
Hi @Gabriel_Silva , this is a very real pain point and you’re not alone, especially with seasonal spikes. You’ve already identified the core issue correctly: HubSpot’s native WhatsApp integration is built around pre-purchased template bundles, which makes it a poor fit when usage is uneven month to month.
The recommendation from Abhinav around Vira is solid. In practice, tools like Vira, Infobip, or Sinch work because they sit on top of Meta’s actual WhatsApp pay-as-you-go pricing, then surface conversations inside HubSpot’s Help Desk using the Conversations API. That’s the key difference versus HubSpot’s native WhatsApp channel. You keep HubSpot tickets, routing, and SLAs, but you’re no longer locked into expiring template packs. In 2025, this “external provider + Help Desk surface” pattern is what most high-volume or seasonal teams end up with.
On the custom channel route, your instinct is right too. HubSpot does support custom channels for the Help Desk, but it’s not lightweight. You’d need to handle inbound webhooks from WhatsApp, map messages to conversations, manage ticket creation and associations, and send outbound replies through Meta’s API.
One practical thing I’d double-check as you evaluate apps is how they handle outbound template initiation from an existing ticket, not just inbound replies. Some tools show messages in Help Desk but still force agents to jump into the vendor UI to start a WhatsApp conversation, which breaks the workflow. Vira explicitly supports this inside the CRM card, which is a big reason it comes up often in these discussions.
Hope this helps clarify the tradeoffs a bit.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
I am less familiar with WhatsApp<>HubSpot use cases. So I have shared this article with Abhinav Sahai, a WhatsApp/HubSpot integration specialist, so he can weigh in and help you choose the right solution.
Hi @abhinavsahai, this sounds a lot like the conversation we had at INBOUND in SanFrancisco. Can you please help @Gabriel_Silva with a WhatsApp template pay-as-you-go model to handle big seasonal variation? thanks Pete.
We already support a pay-as-you-go model for WhatsApp messages, so you won’t have the issue of template packs expiring. The only fixed component is the monthly tool cost, you can see the available plans here.
Thank you so much for sharing this integration with the HubSpot Community, it's wonderful to see your contribution!
I believe the integration you're referring to in the HubSpot Marketplace is "Vira: WhatsApp Integration." If that's not the correct one, please let me know.
Thanks again, and wishing you a fantastic day! Bérangère
Loop Marketing is a new four-stage approach that combines AI efficiency and human authenticity to drive growth.