Zendesk WhatsApp Integration: WhatsApp Zendesk Plans, Setup and Pricing
Zendesk has a real, first-party WhatsApp channel. It turns incoming WhatsApp messages into tickets in the Agent Workspace, and it is built for replying, not for sending. That distinction decides whether Zendesk alone is enough for you.
Last updated August 2026. Not affiliated with Zendesk, Inc. or Meta Platforms, Inc.
Will Zendesk cover your WhatsApp setup?
No sign inThe WhatsApp channel is not sold on its own. Zendesk documents it as part of its Suite plans, and says customers without Suite need Support and Chat with the Social Messaging add-on.
This is the case Zendesk was built for. A customer messages your number, Zendesk opens a ticket in the Agent Workspace, and your team replies in the same thread. The one hard limit is time: Zendesk states that agents cannot respond more than 24 hours after the last end user response.
Reaching someone outside that 24 hour window takes an approved template, and the trigger for an order or appointment lives in your store or booking system, not in a support queue. Teams usually fire these from the Cloud API or a sending platform and let the replies land back in Zendesk.
Two separate walls. Zendesk ships no campaign builder, contact list, or send scheduler. And since April 1, 2025 Meta has paused delivery of marketing category templates to United States phone numbers, so no vendor can run WhatsApp promotions to US contacts right now.
Meta bills you separately per delivered template, by category and country, on your own WhatsApp Business account.
Does Zendesk integrate with WhatsApp?
Yes. Zendesk publishes a first-party WhatsApp channel that you add from Admin Center, and it is one of the few help desks where the connection is genuinely native rather than a third party bolt on. Incoming WhatsApp messages arrive as tickets in the Agent Workspace, agents reply in the same thread, and the conversation is reportable in Explore alongside email and chat.
The part that trips teams up is direction. Zendesk's WhatsApp channel is a reply surface. There is no contact list, no campaign builder, and no send scheduler, because a help desk is designed around conversations customers start. If your plan is to push a template to ten thousand people, that is a different product category, and on top of that Meta currently blocks marketing templates to US numbers entirely.
You also keep ownership of the underlying account. Zendesk's documentation is explicit that you host and own your WhatsApp Business Account through your own Meta Business Manager, so the number, the templates, and the quality rating stay yours even though Zendesk is the provider carrying the traffic.
What Zendesk plan do you need for WhatsApp?
Zendesk documents the WhatsApp channel as part of its Suite plans, and states that customers without Suite need Support and Chat with the Social Messaging add-on. Prices below are Zendesk's published list rates per agent per month paid yearly, checked in August 2026.
| Zendesk plan | List price | WhatsApp channel | What to watch |
|---|---|---|---|
| Suite Team | $55 | Included with Suite | The broader Sunshine Conversations channel set needs Professional or above |
| Suite Professional | $115 | Included with Suite | Zendesk states you need Suite Professional or above to access Sunshine Conversations channels |
| Suite Enterprise | Quoted | Included with Suite | Zendesk lists no public price and routes you to sales |
| Support Team, no Suite | $19 | Needs the add-on | Zendesk says non Suite customers need Support and Chat plus the Social Messaging add-on |
Zendesk seats are only part of the bill. Meta charges you per delivered template on your own WhatsApp Business account, by category and country, which is why the WhatsApp pricing calculator and the WhatsApp Business API pricing breakdown matter more than the seat price once volume grows.
How to connect WhatsApp to Zendesk
Zendesk's own setup flow runs through Admin Center and Meta's authentication. Before you start, confirm the number: it has to be one you own, it has to be able to receive international calls or SMS, and it cannot already be registered to another WhatsApp account.
Get admin rights in Meta Business Manager
Zendesk requires that the person connecting the phone number is an Admin within their own Meta Business Manager. Sort this out first, because a marketing agency owning the Business Manager is the single most common reason a setup stalls halfway.
Add the channel in Admin Center
Go to Admin Center, then Channels, then Messaging and social, then Messaging, and choose Add channel followed by WhatsApp. Zendesk hands you to Facebook to authenticate the profile linked to your Business Manager.
Pick or create the WhatsApp Business Account
You grant Zendesk permission, then select an existing Business Manager and WhatsApp Business Account or create them in the flow. This is the step where the account stays yours rather than becoming Zendesk property.
Set a display name that matches your brand
Zendesk warns that the display name should match your business name or branding, otherwise WhatsApp will reject it. A name that reads like a slogan or a campaign gets bounced and you wait through review again.
Verify the number and activate
Meta sends a code by call or SMS to the number you are registering. An automated switchboard cannot take that call, so use a direct line rather than a main reception number sitting behind a phone menu.
Route the tickets like any other channel
Once live, WhatsApp behaves like your other messaging channels. Triggers, business rules, omnichannel routing, and Explore reporting all apply, which is the real payoff of using the native channel instead of a bridge.
What the Zendesk WhatsApp channel does, and what it does not
This table is the whole buying decision. Almost every disappointed Zendesk WhatsApp review comes from expecting a column on the right to be a column on the left.
| Capability | Native in Zendesk | Detail |
|---|---|---|
| Inbound messages become tickets | Yes | Lands in the Agent Workspace next to email, chat, and social |
| Agents reply in thread | Yes | Subject to the 24 hour rule below |
| Business rules and routing | Yes | Triggers, omnichannel routing, and Explore reporting all cover it |
| You keep the WhatsApp account | Yes | Zendesk documents that you host and own the WABA in your Meta Business Manager |
| Bulk campaign to a contact list | No | No list manager, no campaign builder, no send scheduler |
| Proactive order notifications | Not really | The trigger lives in your store or booking system, so these are usually sent from the Cloud API |
| Marketing templates to US numbers | Blocked | A Meta policy since April 1, 2025, not a Zendesk limitation |
| Flat per message price | No | Meta bills per delivered template by category and country, separately from your seats |
The 24 hour rule is the one that surprises support managers
Zendesk states plainly that for WhatsApp, agents cannot respond more than 24 hours after the last end user response. That window opens when the customer writes to you and refreshes every time they write again. Miss it and a perfectly good reply typed at hour 30 simply will not send, because reaching that person now requires a template Meta approved in advance. Teams that work tickets in daily batches feel this immediately, and the fix is usually a routing rule that puts WhatsApp ahead of email rather than a bigger plan. The mechanics are covered in more depth on the WhatsApp service messages page.
Who the native channel is right for
The honest version: Zendesk is an excellent answer to one half of WhatsApp and no answer at all to the other half.
Support teams already living in Zendesk
If your agents work tickets all day and WhatsApp is just one more inbox, use the native channel. Nothing else gives you WhatsApp inside the same queue, the same macros, the same SLAs, and the same Explore dashboards without maintaining a bridge.
Ecommerce teams sending order updates
You want two things at once: shipping and delivery notifications going out, and the questions they generate coming back to agents. Send the notifications from the Cloud API or a sending platform, keep Zendesk as the reply surface, and both halves work.
Marketing teams planning promotions
Zendesk is the wrong tool, and right now so is every other tool if your list is US based. Meta paused marketing template delivery to United States numbers, so utility and authentication messages are the only categories reliably reaching those contacts.
Frequently asked questions
Does Zendesk support WhatsApp?
Yes. Zendesk publishes a native WhatsApp channel that you add from Admin Center under Channels, then Messaging and social. Incoming WhatsApp messages become tickets in the Agent Workspace, agents reply in the same conversation, and the channel works with triggers, omnichannel routing, and Explore reporting like any other Zendesk channel.
What Zendesk plan do I need for WhatsApp?
Zendesk documents the WhatsApp channel as part of its Suite plans, and says customers without Zendesk Suite need Support and Chat with the Social Messaging add-on. Separately, Zendesk states you need a Suite Professional plan or above to access Sunshine Conversations channels, which is the wider set beyond the natively supported ones.
How much does Zendesk WhatsApp integration cost?
Two bills, not one. Zendesk charges per agent per month, listing Suite Team at $55 and Suite Professional at $115 paid yearly in August 2026, with Enterprise quoted by sales. Meta then bills you separately for every delivered template by category and country, on your own WhatsApp Business account, which is usually the larger number at volume.
Can you send bulk WhatsApp messages from Zendesk?
No. Zendesk has no contact list, no campaign builder, and no send scheduler, because it is designed around conversations that customers start. Running a broadcast means sending from a platform built for it on Meta's Cloud API, then letting the replies route back into Zendesk so agents handle them where they already work.
Is Zendesk a WhatsApp Business Solution Provider?
Zendesk carries WhatsApp traffic for its customers through Sunshine Conversations, so in practice it acts as your provider. The nuance worth knowing is ownership: Zendesk's own documentation says you host and own your WhatsApp Business Account through your Meta Business Manager, so the number, templates, and quality rating remain yours.
Can agents reply to WhatsApp messages any time in Zendesk?
No. Zendesk states that for WhatsApp, agents cannot respond more than 24 hours after the last end user response. The window refreshes each time the customer writes again. Once it closes, the only way to reach that person is an approved template, so a late reply typed into the ticket will not deliver.
What do I need before connecting a WhatsApp number to Zendesk?
A Meta Business Manager belonging to your organization, with the person doing the setup as an Admin of it. The phone number must be able to receive international phone calls or SMS, must not already be registered to another WhatsApp account, and the display name must match your business name or branding or WhatsApp will reject it.
Can I use a Zendesk WhatsApp chatbot?
Yes, within limits. Zendesk's own bots and AI agents work on the WhatsApp channel like other messaging channels. Note that Meta prohibits distributing general purpose AI assistants on the WhatsApp Business Solution, which is aimed at products whose primary function is a general chatbot. A structured support bot answering questions about your business is explicitly unaffected.
Can I keep my number in the WhatsApp Business app and use Zendesk too?
Not the same way at once by default. A phone number can be registered to one WhatsApp account at a time, so connecting it to Zendesk means moving it off the free app. Meta's coexistence option changes this for some setups, and the tradeoffs are covered on the WhatsApp coexistence page.
Keep Zendesk for replies, send from something built to send
Zendesk answers the conversations customers start. WaBulkSend is pre-launch and building the other half on Meta's official Cloud API, with approved templates, scheduling, and delivery reporting planned for the outbound side, so your agents can carry on working wherever they already do.
Join the waitlist