# Zendesk Web Widget: Setup, Plan Gates and Limits (2026)

> How to set up the Zendesk messaging Web Widget: one snippet, four Admin Center tabs, AI agents first, JWT sign-in, plan gates and the 2028 Chat deadline.

_Source: https://professionalstoolkit.com/articles/zendesk-web-widget — The Professional's Toolkit · updated November 2026_

---

The Zendesk Web Widget is the chat window you add to your website by pasting one snippet, and on any account created after 2 November 2021 it already exists as a messaging widget that only an admin can set up.[1] The cheapest plan that includes it is Suite Team. Support Team, the email-only plan, does not carry messaging at all. Setup takes four tabs in Admin Center, and the hard part is not the code. It is deciding what greets visitors first: an AI agent, a contact-details form or a person. That choice, and the plan gates behind it, decide what the widget costs you.


**4,096** — Characters per message in the messaging Web Widget, for customers and agents alike.



- **1 snippet** — Shared by the messaging widget and Web Widget (Classic)
- **31 Jan 2028** — Zendesk Chat deprecation date for messaging-eligible accounts
- **10 keys** — Maximum JWT signing keys per account


## Which widget you have: messaging or Classic

Zendesk runs two widgets. The **messaging Web Widget** is the current one, built on Sunshine Conversations, the same platform behind WhatsApp, Instagram and the mobile SDKs, so a conversation started on your site can continue on another channel. Messaging is the default experience on Suite plans, and new accounts get it switched on with no way to opt out. The older **Web Widget (Classic)** bundles a contact form, live chat, a call option and help center search, and it is configured through JavaScript commands rather than Admin Center.

The two share the same snippet.[2] Converting a Classic widget happens per brand in Admin Center and carries over its position, theme color and button text, which becomes the launcher text. Two things do not move. Custom JavaScript written for Classic may stop working, and call options disappear from the messaging widget, although calls still reach agents in Agent Workspace. Deployed Android, iOS and Unity SDKs are also untouched: the messaging SDKs are separate builds you configure and ship on their own.

**The deadline matters.** Zendesk Chat, the live-chat product behind Classic's chat window, has had no enhancements since 2020, is closed to new customers and will be deprecated on 31 January 2028. Accounts on Suite with Agent Workspace must migrate to messaging before then. A setup wizard carries Chat triggers and logic over and shows a checklist of pending items. Chat-only plans are not currently eligible for the move.

## Plans, prices and the gates that touch the widget

Zendesk's pricing page lists Suite Team at $55 per agent per month billed annually, or $69 billed monthly, and Suite Professional at $115 billed annually or $149 billed monthly.[3] Every agent seat is paid, admins included, so the bill follows headcount; our [Zendesk pricing guide](/articles/zendesk-pricing) covers the full seat rules. On Support plans, messaging and live chat are sold as a separate product and come bundled only inside Suite. Non-Suite accounts that add messaging also need Agent Workspace on, at least one agent with a Chat role and older social messaging integrations turned off.

| Widget feature | Suite Team | Suite Professional | Suite Enterprise |
|---|---|---|---|
| Messaging Web Widget and mobile SDKs | Yes | Yes | Yes |
| Messaging departments | 2 | Unlimited | Unlimited |
| Rich-text formatting in messages | No | Yes | Yes |
| Included automated resolutions | 5 per agent a month | 10 per agent a month | Talk to Sales |
| Removing Zendesk branding | No | No | Yes |

The table hides a sizing question. By our arithmetic, three agents come to $165 a month on the team tier billed annually against $345 a month a tier up, a gap of $180 a month. That buys unlimited departments, formatted replies and twice the resolution allowance. If your traffic splits into more than two queues, such as sales and support in two languages, the higher plan is the one that fits.


> 💡 **Count your queues before choosing:** Suite Team allows two messaging departments; Suite Professional removes the cap. Map sales, support and languages first.


## Setting it up, step by step

Messaging channels live in Admin Center under Channels, then Messaging and social, then Messaging. Each web or mobile channel has Style, Responses, Preferences and Installation tabs, and the work runs in that order.

1. **Style.** Set the primary color, a header title and an optional logo. You can add a privacy notice with a recording notice and a link to your policy.
2. **Responses.** Choose what answers first: an AI agent or the basic messaging response that collects customer details. This replaces the old Chat pre-chat form.
3. **Preferences.** Set business hours, which take over from Chat's offline form, plus multi-conversations, transcript downloads and whether agents can end sessions.
4. **Installation.** Copy the snippet into every page where the widget should appear, or into your help center theme.

Messaging is turned on per brand, so a company with three storefronts repeats these steps three times, and turning it on also creates a digital line named after each brand. Supported browsers are the latest two versions of desktop Chrome and Firefox, Edge, the latest Safari, the latest two versions of iOS Safari, and Android's browser and Chrome Mobile.

Shopify stores skip the snippet. The free Shopify app adds the widget for the default brand automatically, with messaging on by default; other brands need the code pasted into the Shopify theme by hand. If messaging is switched off, the app installs Web Widget (Classic) instead. Disconnecting a store removes the widget along with the sidebar apps.

For developers, the messaging widget now exposes behavioral APIs that create and fetch conversations, send messages and intercept messages before they display, plus a minimalistic styling preset with options for avatar size, timestamps and bubble width. A custom launcher works on the Web Widget only, not in the mobile SDKs.

## Putting an AI agent or a trigger in front

Turning on messaging makes AI agents available as the first responder in the widget. Zendesk recommends at least 10 published help center articles on common questions before you rely on one. Every plan includes AI agents, but they are billed per automated resolution, meaning a conversation the agent closes without handing it to a human. After the plan allowance, extra resolutions cost $1.50 each committed or $2.00 each pay-as-you-go. Committed resolutions, bought ahead, are 25% cheaper each by our arithmetic, so commit only the volume you are confident you will use, after a measured month on pay-as-you-go. Included resolutions do not roll over. At the limit, admins either allow overage or pause the AI agents, which sends conversations to live agents.

**Test before launch.** The test widget and the conversation simulator do not consume resolutions; testing on your live site can. The test widget cannot reproduce restricted help center content or CRM actions, so check those paths in a sandbox, which also consumes nothing. One live path does count: a help center generative search conversation that the AI agent resolves uses a resolution.


> 💡 **Test in the simulator, not live:** The test widget and conversation simulator do not consume automated resolutions. Testing on your live site can.


If you skip the AI agent, three standard messaging triggers cover the basics: First Reply, which sends an acknowledgement after 5 seconds, Request Contact Details and All Agents Offline. All three are inactive by default. Proactive messages can now be tied to a specific AI agent use case, and business metadata about a visitor can act as a trigger condition. With multi-conversations on, each proactive message opens a new conversation instead of joining an old one, and the AI agent runs again every time a customer starts one. Our [Zendesk AI playbook](/articles/zendesk-ai-playbook) explains what counts as a resolution in detail.

## Identity, safety and the limits you will hit

Anonymous visitors are tracked only through browser session storage. They cannot be followed across browsers. To tie a conversation to a known customer, the widget supports end-user authentication with signed JSON Web Tokens.[4] An admin can create up to 10 signing keys, the external ID must be an alphanumeric string of at most 255 characters that is unique across brands, and the token scope must be user. With multi-conversations, an authenticated user can hold up to 100 active tickets at once, while anonymous users have no cap. When a visitor signs in mid-conversation and the external ID already exists, the anonymous record merges into the known user. Delayed sign-in can leave duplicate tickets for agents to merge by hand.

Teams without back-end developers have a newer route: since 2 November 2026, AI agents can verify customers with one-time passcodes by adding an email verification block to a dialogue. That also works on WhatsApp and other third-party messaging channels, where JWT does not reach. Signed-in customers are not asked by the AI agent for their name or email, and their conversations sync across devices. The remaining limits are short:

- Each message, from customer or agent, holds up to 4,096 characters.
- IP bans cover the Web Widget and the iOS and Android SDKs, up to 5,000 records, managed by admins; banned users are not told.
- Attachments are scanned for malware, and flagged files wait for an admin's approval.
- Skill-based routing does not work on the Web Widget or any SDK; omnichannel routing handles messaging instead.
- Rich text lets agents format replies, but customers cannot format theirs and inline images are not supported.


> ⚠ **Classic JavaScript may break:** Converting to the messaging widget keeps position, color and launcher text, but custom code written for Web Widget (Classic) may not be supported, and call options are not available in the messaging widget.


Brand filtering, released in August 2026, shows customers only the current brand's conversations, but it needs multi-conversations and at least two brands. The widget also speaks every language Classic supported, and articles from your help center open in an in-widget viewer. Our [help center guide](/articles/zendesk-help-center) covers the knowledge base those AI answers draw on.


## FAQ

**Can I add the Web Widget to my help center?**

Yes. Messaging can be deployed on a website or a help center through the Web Widget, and Zendesk's conversational help center early-access program requires the widget embedded in the help center with multi-conversations on.

**Does the messaging Web Widget work with Google Analytics?**

Automatic Google Analytics event reporting is documented for Web Widget (Classic), which sends widget and channel events when the analytics tag is on the page. It can be turned off by setting the analytics option to false.

**Can customers call us from the messaging widget?**

Not from the widget itself: call options are not available in the messaging Web Widget. Digital lines can be added to it through the Zendesk API, and calls still reach agents in Agent Workspace.

**Can an agent end a messaging session?**

Yes. Once an agent ends it, the customer cannot reach that agent through any messaging channel, and a new reply in the widget starts a new session and a new ticket.


## The bottom line

The messaging Web Widget is the only widget worth building on now: Classic's live chat ends on 31 January 2028, and the snippet does not change when you switch. Start on Suite Team if one or two queues and plain-text replies cover you, and move a tier up once you need more departments or formatted answers. Before go-live, test the AI agent in the simulator, decide whether overage or a pause fits your budget, and add JWT sign-in if customers expect their history to follow them across devices.



## Sources

[1] Zendesk help: Setting up Web Widget to add messaging to your website or help center — https://support.zendesk.com/hc/en-us/articles/4409103246874-Setting-up-Web-Widget-to-add-messaging-to-your-website-or-help-center (2026-11)
[2] Zendesk help: Setting up Web Widget for messaging when using live chat and Web Widget (Classic) — https://support.zendesk.com/hc/en-us/articles/4408832031898-Setting-up-Web-Widget-for-messaging-when-using-live-chat-and-Web-Widget-Classic (2026-11)
[3] Zendesk Pricing Plans - Starting from $19/month Skip to main content Try for free Platform Zendesk Resolution Platform Deliver faster, highe — https://www.zendesk.com/pricing/ (2026-11)
[4] Zendesk help: Understanding and setting up end-user authentication for messaging — https://support.zendesk.com/hc/en-us/articles/4411666638746-Understanding-and-setting-up-end-user-authentication-for-messaging (2026-11)
[5] Zendesk help center — https://support.zendesk.com/hc/en-us
[6] Zendesk Customer Agreement — https://www.zendesk.com/company/agreements-and-terms/zendesk-customer-agreement/
[7] App Store (US), Zendesk Support listing — https://apps.apple.com/us/app/zendesk-support/id1174276185