Freshdesk WhatsApp Integration: Plans, Costs and the 20% Markup
Freshdesk supports WhatsApp on Growth, Pro and Enterprise, and Freshworks publishes a 20% markup on the Meta bill. Here is what the channel does, what it lacks, and why October 2026 moves the cost.
Short answer: yes, Freshdesk integrates with WhatsApp natively, on the Growth, Pro and Enterprise plans. The detail that matters most for budgeting is one almost no comparison article mentions: Freshworks publishes a flat 20% markup on top of whatever Meta bills you for messages. Of the three big helpdesks, it is the only one that puts its margin in writing.
That transparency is genuinely useful, and it also makes the arithmetic easy to get wrong in one specific way. Freshdesk's markup is applied to a Meta bill that changes on October 1, 2026. Below is how the channel actually works, what the published limitations are, and where the cost lands after that date.
How the Freshdesk WhatsApp integration works
WhatsApp is a native channel in Freshdesk, not a marketplace app you bolt on. You add it from Admin, Channels, WhatsApp, then authenticate through Meta Business Manager, verify the phone number by SMS or call, and grant Freshworks the permissions it needs. Once connected, inbound WhatsApp messages arrive as Freshdesk tickets and follow your normal routing and SLA rules.
Two setup facts are worth knowing before you start. You can connect up to 50 WhatsApp numbers per account, though trial accounts are limited to one, so a multi-brand or multi-region team is not going to hit a ceiling. And you are not locked out if your number already lives somewhere else: Freshdesk supports connecting a number currently associated with another provider, migrating it without changing your WhatsApp account settings. That path needs extra verification through Freshworks support rather than being fully self-serve.
Templates are the one thing you do not manage inside Freshdesk. They are created, submitted for approval, edited and deleted in Meta Business Manager, and Freshdesk links out to it. That is the same arrangement Intercom uses, and it trips up teams who expect a template builder in the helpdesk UI. Any message you send outside the 24 hour customer service window has to use one of those approved templates.
What the Freshdesk WhatsApp integration costs
There are two layers, and conflating them is how budgets go wrong.
The first layer is your Freshdesk subscription. WhatsApp is available on Growth, Pro and Enterprise for both Freshdesk and Freshdesk Omni. It is not on the entry tier.
The second layer is messaging, and this is where the 20% figure lives. Freshworks states plainly that it applies a 20% markup to the total WhatsApp cost billed from Meta. So if Meta charges you $500 in a month for delivered templates, Freshdesk bills $600. Neither Zendesk nor Intercom publishes an equivalent number, which makes Freshdesk the easiest of the three to model in a spreadsheet before you commit.
Freshdesk's own pricing documentation is also current, which is rarer than it should be. It correctly describes Meta's per-message model effective July 1, 2025: template messages are charged only when delivered, rates vary by template category and the recipient's country calling code, and all non-template messages are free. Plenty of third-party guides still describe the retired conversation-based model with its first 1,000 conversations free. If you read that anywhere, you are reading something written before mid-2025.
The October 2026 change that moves this number
Here is the part to plan around. Freshdesk's documentation currently states, accurately, that utility templates delivered inside an open customer service window are free. That stops being true on October 1, 2026.
From that date, two things change on Meta's side. Utility templates delivered inside an open customer service window lose their free status. And service messages, meaning any non-template reply you send inside an open 24 hour window, whether typed by a human agent or generated by your own AI, become chargeable at the utility and authentication rate, with no volume tier attached.
For a support team, that is the expensive combination. Support traffic is overwhelmingly conversational replies inside open windows, which is exactly the category that is free today and will not be in October. Then Freshworks adds 20% on top of the larger number. A desk running mostly reactive support could see its WhatsApp line grow substantially without sending a single extra message, and the markup scales with it rather than staying flat.
Meta has committed to publishing final service-message rates by September 1, 2026, so the precise figure is not knowable yet. What is knowable is the direction. If you are modelling a 2027 support budget on today's invoice, you are modelling the wrong baseline. Our WhatsApp pricing changes hub tracks each dated change as it lands. Markups like this are also easy to lose sight of once they are folded into a single monthly SaaS invoice, which is the same visibility problem that makes tracking software spend against actual usage worth doing across the rest of the stack.
Freshdesk vs Zendesk vs Intercom for WhatsApp
All three put WhatsApp behind a paid tier, but the commercial relationship underneath differs in ways that matter if you already have a WhatsApp Business Account.
| Freshdesk | Zendesk | Intercom | |
|---|---|---|---|
| Plans with WhatsApp | Growth, Pro, Enterprise | Support Team and above, plus add-ons | Essential, Advanced, Expert |
| Is the vendor your provider | Yes, Freshworks bills you for Meta costs | Yes, Zendesk is a BSP via Sunshine Conversations | No, you bring your own WABA |
| Published messaging markup | 20% on the Meta bill | Not published | Not published |
| Bring an existing number | Yes, migration supported with extra verification | Number hosting sold as an add-on | Yes, your WABA stays in your Business Manager |
| Where templates are authored | Meta Business Manager | Meta side | WhatsApp Manager |
The practical read: Freshdesk is the most predictable to budget because the markup is public. Intercom gives you the most ownership because the WhatsApp Business Account stays yours, though it comes with a permanent currency trap, since a WABA must be set to USD and Meta never allows the currency to change afterwards. Zendesk sits in between and publishes no flat price at all.
What the Freshdesk WhatsApp channel does not support
Freshworks documents its gaps, which is more than most vendors do. The published limitations:
- Agents cannot send GIFs to users.
- Stickers are not supported.
- WhatsApp tickets cannot be merged with other tickets, which is awkward if a customer opens by email and follows up on WhatsApp.
- Contacts identified only by a WhatsApp username, rather than a phone number, cannot receive proactive messages or authentication templates.
That third one is the operationally annoying one. Merging duplicate tickets is routine in a busy queue, and a channel that opts out of it means WhatsApp conversations stay slightly apart from the rest of the customer's history.
Is Freshdesk a good fit for bulk WhatsApp campaigns?
It is a support desk, and it is built around inbound conversations that become tickets. If your goal is outbound campaigns to a list, a helpdesk is the wrong shape of tool regardless of which of the three you pick. Template approval, list management, per-recipient delivery reporting and messaging tier pacing are campaign problems, not ticketing problems, and that is the job a dedicated WhatsApp bulk messaging platform exists to do.
The common setup is both: a helpdesk owning the inbound queue, and a separate campaign tool owning outbound sends on the same or a second number. Our WhatsApp customer service platform guide covers how those two halves fit together.
One more thing worth knowing if you are arriving from US SMS. WhatsApp sits entirely outside the A2P 10DLC system, so there is no brand or campaign to register with The Campaign Registry and no carrier surcharge per message. What replaces it is Meta's own approval regime. We cover the comparison in detail on our 10DLC registration and WhatsApp page.
Does Freshdesk support WhatsApp?
Yes. WhatsApp is a native channel on Freshdesk Growth, Pro and Enterprise, and on Freshdesk Omni at the same tiers. Inbound messages become tickets that follow your existing routing, assignment and SLA rules, and agents reply from the same console they use for email and chat. You connect it through Meta Business Manager during setup.
How much does Freshdesk charge for WhatsApp?
Freshworks applies a 20% markup to the total WhatsApp cost billed from Meta, on top of your Freshdesk plan. Meta charges per delivered template, priced by template category and the recipient's country. Non-template messages are free today, though that changes on October 1, 2026 when service messages become chargeable at the utility rate.
Can I move my existing WhatsApp number to Freshdesk?
Yes. Freshdesk supports connecting a number already associated with another provider, migrating it without changing your WhatsApp account settings, though it requires additional verification through Freshworks support rather than the self-serve flow. Migrating a registered number between providers generally carries over your display name, quality rating and messaging limit tier, but not your chat history. Our guide to switching WhatsApp Business API provider covers the prerequisites, including the two-factor requirement that catches most teams out.
Where do I create WhatsApp templates in Freshdesk?
In Meta Business Manager, not in Freshdesk. Freshdesk links out to it, and Meta has to review and approve each template before you can use it to message someone outside the open 24 hour customer service window. Approval times vary by category, and rejections are common on first submission when the template reads as promotional but was filed as utility.
The bottom line
Freshdesk is a reasonable WhatsApp helpdesk and an unusually honest one about what it charges. The 20% markup is the number to build your model on, the Growth plan is the floor, and the documented gaps around ticket merging and stickers are small enough to live with for most teams.
The thing to actually diarize is October 1, 2026. Today's invoice is calculated against a Meta bill where conversational replies and in-window utility templates are free. After that date they are not, and a percentage markup grows with the base it is applied to. Check your ratio of in-window replies to outbound templates now, while the comparison is still cheap to make.