How to Integrate Freshdesk with WhatsApp

First, the important dependency

Unlike most Freshdesk integrations, you won't find WhatsApp by browsing the Marketplace and clicking Install. WhatsApp is a native messaging channel built into Freshworks' platform — the same messaging layer that powers Freshchat. On a plan that supports it, the channel simply appears under Admin → Channels → WhatsApp, and conversations flow in as tickets in your normal Freshdesk inbox.

That distinction matters for two reasons. First, availability is gated by your plan rather than by an install. Per Freshworks' WhatsApp for Freshdesk Business Integration documentation, the WhatsApp channel is available on the Growth, Pro, and Enterprise plans (for both Freshdesk and Freshdesk Omni). Second, because it runs on the messaging layer, some of the behaviour — the 24-hour window, message templates, conversation billing — comes straight from Meta's WhatsApp Business Platform, not from Freshdesk's own rules. If you already run Freshchat alongside Freshdesk, it's worth understanding how those two products connect, which we cover in how to integrate Freshchat with Freshdesk.

What you need before you start

Connecting a number touches three accounts, so line these up first:

1. A Freshdesk plan on Growth, Pro, or Enterprise (trial accounts can connect one number; paid accounts up to 50).
2. A Meta Business Manager account — required to use the WhatsApp Business Platform with Freshworks and to verify your business.
3. A WhatsApp Business Account (WABA) and a phone number you can receive an OTP on. The number can't already be tied to a personal or standard WhatsApp app; it has to be free to register (or migrated) as a business number.

Step-by-step: connect a WhatsApp number

Here's the native flow, following Freshworks' documentation:

1. Go to Admin → Channels → WhatsApp.
2. Click Connect a new number (or Add new number if you already have one connected), then Get started.
3. You'll be redirected into Meta's embedded signup flow. Sign in to your Meta Business Manager account and grant Freshworks the permissions it requests.
4. Select or create the WhatsApp Business Account and the phone number you want to use.
5. Verify the number by OTP — choose SMS text message or a voice call, then enter the code and click Finish setup.
6. Back in Freshdesk, the number now appears as a WhatsApp channel, and incoming messages start creating tickets automatically.

If your number already lives with another BSP (Business Solution Provider), you don't have to start fresh. Choose the connect a number associated with another provider option to migrate it to Freshworks without losing the number — though that path is support-assisted and takes longer than a clean new setup.

The 24-hour window and message templates

This is the part people underestimate, and it's a Meta rule rather than a Freshdesk one. When a customer messages you, you can reply freely — within a 24-hour customer service window, back-and-forth replies are unrestricted and billed as a service conversation. But the moment you want to message a customer proactively, or reply after that 24-hour window has closed, you can only send a pre-approved message template.

Per Freshworks' Create and Use WhatsApp Message Templates guide, templates come in three Meta categories:

• Utility — transactional updates like order confirmations and post-purchase notifications.
• Authentication — one-time passcodes and login verification.
• Marketing — promotions, offers, and awareness messages.

Templates are created and submitted for approval in Meta Business Manager, and Meta's review can take up to 24 hours. Once approved, agents apply them in Freshdesk from the Reply button by selecting Message Template. Reply-via-template is available from the Growth plan onward. The practical takeaway: build and get your core templates approved before you launch, or your first out-of-window follow-up will be blocked.

What it costs

WhatsApp isn't free to run at scale, and the billing changed recently. Effective July 1, 2025, WhatsApp moved to per-message pricing through Meta, and on top of Meta's charges, Freshworks applies a 20% markup to that billing. So your true cost is Meta's conversation/message rate plus that markup, on top of your Freshdesk subscription.

A couple of related limits to plan around:

• An unverified WhatsApp Business Account can only initiate 250 business-initiated conversations in a rolling 24-hour window — you'll want to complete Meta's business verification before any real outbound volume.
• The default threading interval is 24 hours: messages inside that window append to the same ticket; a message after it opens a new one.

Native channel vs. middleware vs. an AI layer

There's more than one way to get WhatsApp working with Freshdesk, and they solve different problems. This isn't an either/or with the AI row — that layer sits on top of whichever channel you choose.

The native channel is the cleanest choice for most support teams because everything stays inside Freshdesk. Middleware earns its keep when WhatsApp is a serious marketing channel with campaign needs the native integration doesn't cover. And the AI row is about what happens after a message becomes a ticket — which is where the honest limits below come in.

The honest limits — and where an AI layer picks up

Credit where it's due: the native WhatsApp channel is well built. It puts real-time chats into the same ticket system as everything else, respects Meta's rules, and doesn't ask you to bolt on a separate app. For getting WhatsApp into Freshdesk, it's the right tool.

But notice what it does and doesn't do. The channel is transport — it delivers the message and creates the ticket. It doesn't read the message, understand what the customer is asking, or write the reply. And WhatsApp raises the stakes on that gap, because customers expect chat-speed answers: a two-hour email turnaround feels fine, the same delay on WhatsApp feels broken. The 24-hour window is generous on paper, but the expectation is minutes.

There are also the ordinary frictions: the channel is plan-gated (no WhatsApp on lower tiers), you're on the hook for Meta's per-message costs plus a 20% markup, and template approval adds a Meta-side workflow you don't control. None of that is a knock on the integration — it's the reality of the WhatsApp Business Platform.

This is the seam where an AI agent layer fits, and it's worth being clear-eyed about the build-versus-buy tradeoff first. The broader category of AI agents for customer service exists to do the reasoning-heavy work a transport channel can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, and it doesn't become your WhatsApp gateway. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your channels create. Once a WhatsApp conversation has landed in Freshdesk as a ticket, Macha can draft or post a grounded reply on it, triage it by intent, and look up order or account status through a custom tool that turns a REST API into something the agent can call — so a "where's my order?" over WhatsApp gets answered inside the window instead of queued. (One boundary to keep straight: Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. It works on the WhatsApp tickets in Freshdesk, not on the WhatsApp channel itself. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: let Freshdesk's native channel own getting WhatsApp messages in and out, and layer an agent on top for the part transport can't do — actually answering fast enough to match WhatsApp expectations. If you'd rather see the AI side end to end, how to automate Freshdesk with AI walks through it.

FAQ

Where do I set up WhatsApp in Freshdesk? Go to Admin → Channels → WhatsApp, click Connect a new number, and follow Meta's embedded signup to link your WhatsApp Business Account. It's a native channel, not a Marketplace app you install.

Do I need Freshchat to use WhatsApp with Freshdesk? Not as a separate subscription — WhatsApp runs on Freshworks' native messaging layer (the same one that powers Freshchat), and the channel appears directly under Admin → Channels once your Freshdesk plan supports it.

Which Freshdesk plans include WhatsApp? The WhatsApp channel is available on the Growth, Pro, and Enterprise plans, for both Freshdesk and Freshdesk Omni. Reply-via-template is available from the Growth plan. Trial accounts can connect one number; paid accounts up to 50.

Why do I need message templates? WhatsApp only lets you reply freely within a 24-hour customer service window. To message a customer proactively or after that window closes, you must use a Meta-approved template (Utility, Authentication, or Marketing), which you create in Meta Business Manager and which can take up to 24 hours to approve.

Can I add AI to WhatsApp tickets without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and works on the tickets your channels create — including WhatsApp-sourced tickets. It drafts or sends grounded replies and triages by intent, while Freshdesk's native channel stays the WhatsApp gateway. Macha connects to Freshdesk, not to Freshchat.

Ready to answer WhatsApp tickets at chat speed instead of just routing them? Start a free trial of Macha and connect it to your Freshdesk in minutes.