Intercom WhatsApp Integration: Setup, Limits, and What It Costs
Intercom supports WhatsApp on paid plans, but you bring your own WABA and it must be in USD forever. Here is what the channel can send, what its API cannot, and the 2026 cost change support teams should price in now.
Short answer: yes, Intercom integrates with WhatsApp, but unlike Zendesk it is not your BSP. You bring your own WhatsApp Business Account, connect it to Intercom on a paid plan, and Intercom handles the inbox and outbound campaigns on top of it. The two catches that cost teams the most are that the WABA currency must be USD and can never be changed afterwards, and that Intercom's REST API cannot send WhatsApp templates at all.
Intercom is where a lot of US SaaS companies already run support, so adding WhatsApp to it looks like a small configuration job. It mostly is. But the WhatsApp channel behaves differently from Intercom's own Messenger in ways that are not obvious until you are live, and a couple of decisions you make in the first ten minutes are permanent. This walks through what Intercom's own documentation says, where the integration is genuinely good, and where it runs out.
What the Intercom WhatsApp integration actually is
WhatsApp is a paid channel in Intercom, available on the Essential, Advanced, and Expert plans. Once connected, inbound WhatsApp messages arrive as Intercom conversations in the same inbox as your Messenger and email conversations, and your agents reply from the same place.
The important structural point is who owns the WhatsApp side. Intercom connects to a number that is already registered to the WhatsApp Business Platform under a WhatsApp Business Account you control in your own Meta Business Manager. Intercom is not acting as your Business Solution Provider the way Zendesk does through Sunshine Conversations. You bring the WABA; Intercom is the interface on top of it.
That is genuinely better for portability, because the account relationship with Meta stays yours. It also means the setup has more steps: you need a verified Meta Business Account, a number registered to the platform, and a WABA configured correctly before Intercom has anything to connect to. If you have not been through that before, our guide to the WhatsApp Business API covers registration and verification end to end.
The USD requirement nobody warns you about
Intercom's documentation is blunt about this one: your WhatsApp Business Account must be set to USD for the integration to work. Meta does not allow the currency of a WABA to be changed after it has been created.
Read that twice if you are setting up a new WABA. If you create it in another currency because that is what your finance team asked for, the Intercom integration will not work, and the fix is not a settings toggle. You create a new WhatsApp Business Account in USD and migrate the number to it. For a US company this is usually a non-issue, but for anyone with a non-US parent entity or a finance team that defaults to a local currency, it is the single most expensive thing to get wrong on day one.
What Intercom can and cannot send
Inbound is straightforward. A customer messages your number, the conversation lands in the Intercom inbox, an agent replies. That reply is free-form and works because it happens inside WhatsApp's 24 hour customer service window, which opens each time the customer messages you and runs for 24 hours from their last message.
Outbound is where the rules bite. WhatsApp only allows businesses to start conversations with pre-approved message templates, so you cannot type a fresh message to someone who has not written to you recently. Intercom supports this properly through its Outbound section: you can send one-off messages or ongoing dynamic messages, triggered on event or date based rules, and you select from templates you created in WhatsApp Manager. Templates are not authored inside Intercom, and you cannot edit the text of a template when you send it.
Then there is the API gap, which matters if you were planning to drive WhatsApp from your own backend. Intercom's REST API does not currently support sending WhatsApp message templates, and it is not possible to start a WhatsApp conversation via the REST API at all. Replies to existing conversations through the API do go out over WhatsApp, but anything that needs a template, which is everything outside the 24 hour window, will not deliver. If your plan involved triggering WhatsApp messages programmatically from your own systems, that plan needs the API directly rather than through Intercom, and our walkthrough of the WhatsApp send message API shows what that call looks like.
Intercom WhatsApp limitations worth knowing before you commit
Intercom lists several things the WhatsApp channel does not support: group conversations, phone calls, creating tickets from WhatsApp, and CSAT remarks. For a support org that runs on tickets and satisfaction scoring, that last pair is a real workflow gap rather than a footnote, because a WhatsApp conversation will not feed the same reporting your email and Messenger conversations do.
There are also volume limits. Free trial accounts are capped at 100 messages in the last 30 days, and paid workspaces have a monthly outbound WhatsApp limit tied to the plan, with a specific error when you exceed it. That cap is the thing to check against your actual send volume before you build a campaign program on top of Intercom.
One more, for anyone thinking about the exit. When you remove a number from Intercom it stays tied to the WABA that was used with Intercom. To use it somewhere else you create a new WABA and migrate the number to it. Numbers can move between providers, but it is a deliberate process rather than a disconnect button, and we have written up what carries over when you switch WhatsApp API providers.
Intercom vs a dedicated WhatsApp platform
These tools are solving different problems, and the honest comparison makes that obvious.
| Capability | Intercom WhatsApp channel | Dedicated WhatsApp platform |
|---|---|---|
| Who is your BSP | You, through your own WABA | Varies; check before you sign |
| Unified inbox with email and chat | Yes, this is the main reason to use it | WhatsApp only |
| Outbound bulk campaigns | Yes, capped by a plan-level monthly limit | Capped only by your Meta messaging tier |
| Send templates via REST API | Not supported | Core function |
| Start a conversation via API | Not supported | Core function |
| Tickets and CSAT from WhatsApp | Not supported on this channel | Varies |
| Template authoring | In WhatsApp Manager, selected in Intercom | Usually in-product |
| Best fit | Support teams already standardized on Intercom | High-volume sending and API-driven messaging |
If Intercom is already your support system of record and WhatsApp is a secondary channel with modest volume, the native integration is the right call and you should not add another tool. If WhatsApp is where your customers actually are, if you send campaigns to a real list, or if you need to trigger messages from your own code, the plan-level outbound cap and the API gap will find you. That is the case for running sends on a dedicated WhatsApp bulk messaging platform and keeping Intercom for the conversations your agents handle.
What it costs
Intercom publishes plan pricing but does not publish a flat price for the WhatsApp channel itself, and we are not going to invent one. What we can say precisely is that there are two separate cost layers and people routinely forget the second.
The first is Intercom's own plan cost, since WhatsApp is a paid channel on Essential, Advanced, or Expert. The second is Meta's per-message charge, billed per delivered template by category and destination country. Meta publishes no US dollar per-message rate in its developer documentation, so the honest US reference point is Twilio's published rate card, where a delivered US utility template works out to roughly $0.0084 all in, or $8.40 per 1,000.
Two changes are worth pricing in now. From October 1, 2026, service messages, meaning any non-template reply your agents send inside an open 24 hour window, become chargeable at the utility rate with no free volume tier, and utility templates delivered inside an open window lose their free status. Almost every article about WhatsApp support still says service messages are free with no end date. For a support team, where nearly every message is a service message, that is the line item that changes most. Meta has committed to publishing final rates by September 1, 2026, so treat any specific cent figure today as an estimate. Our WhatsApp pricing changes hub tracks it as details land.
A US-specific warning about marketing templates
If you are planning WhatsApp promotions to US customers through Intercom Outbound, they will not arrive. Meta paused delivery of marketing-category templates to United States phone numbers on April 1, 2025, and the pause is still in force. Marketing templates aimed at +1 numbers fail with error 131049, after the template has been approved and the campaign has run.
US programs work on utility templates, which cover order, account, and appointment updates, on authentication templates for codes, and on click-to-WhatsApp ads, where someone tapping the ad opens a free 72 hour window you can reply in conversationally with no template at all. That ad route is untouched by the 2026 billing changes and is the strongest US play available.
Setting it up
The sequence, assuming you already have an Intercom workspace on a qualifying plan:
- Complete Meta Business Verification, and make sure the WhatsApp Business Account you will use is set to USD before anything else.
- Register your business number to the WhatsApp Business Platform. This permanently removes it from the consumer and WhatsApp Business apps, and no chat history transfers, so use a number you are willing to commit.
- Connect the WhatsApp channel in Intercom and authorize against your Meta Business Account.
- Create the templates you need in WhatsApp Manager, in the correct category, and wait for approval. Our WhatsApp message template examples are written to be adapted.
- Set up routing and an away message so chats arriving outside staffed hours get an answer, then watch how often the 24 hour window closes before someone replies.
That last measurement is the one that predicts your bill after October. A conversation you answer inside the window is one free-form reply today; a conversation you let expire costs a template to reopen. Support teams that get good at this tend to have two things in place: an away message that sets a real expectation, and a fast way for agents to find the answer instead of asking a colleague. If your agents lose time hunting through Notion, Drive, and old tickets for the same answers, an internal search layer that pulls answers out of every work system at once does more for response time than another macro.
Frequently asked questions
Does Intercom support WhatsApp?
Yes. WhatsApp is a paid channel on Intercom's Essential, Advanced, and Expert plans. Inbound messages arrive as normal Intercom conversations and agents reply from the same inbox they use for email and Messenger. You connect a number that is already registered to the WhatsApp Business Platform under your own WhatsApp Business Account.
Is Intercom a WhatsApp BSP?
No. Intercom connects to a WhatsApp Business Account you own in your own Meta Business Manager rather than hosting the account for you. That differs from Zendesk, which becomes your BSP through Sunshine Conversations when you add a number. The practical benefit is that your relationship with Meta stays yours, and the practical cost is a longer setup.
Can I send bulk WhatsApp messages from Intercom?
Yes, from the Outbound section, as one-off or ongoing dynamic messages using pre-approved templates and event or date based triggers. The limit is your plan's monthly outbound WhatsApp allowance, not your Meta messaging tier, so check that cap against your real send volume before planning campaigns around it.
Can Intercom's API send WhatsApp templates?
No. Intercom's REST API does not currently support sending WhatsApp message templates, and you cannot start a WhatsApp conversation through the REST API. Replies to existing conversations do send over WhatsApp, but anything outside the 24 hour window needs a template and will not deliver. Programmatic sending has to go through the WhatsApp API directly.
Why does my WhatsApp Business Account need to be in USD for Intercom?
It is a requirement of Intercom's integration. The part that matters is that Meta does not allow a WABA's currency to be changed after creation, so a non-USD account cannot be corrected later. You would need to create a new WhatsApp Business Account in USD and migrate the number across, which is why this is worth checking before you create anything.
What are the limitations of Intercom's WhatsApp channel?
Intercom lists no group conversations, no phone calls, no ticket creation from WhatsApp, and no CSAT remarks. There is also a monthly outbound message cap by plan, a 100 message limit over 30 days on free trials, and no template sending through the REST API. For ticket-driven support orgs, losing ticket creation and CSAT on the channel is the most disruptive gap.
Can I move my number off Intercom later?
Yes, though not instantly. When you remove the number it remains tied to the WhatsApp Business Account used with Intercom, and reusing it elsewhere means creating a new WABA and migrating the number into it. Because you own the WABA, you can drive that process yourself rather than waiting on a provider to release the account.