
Between 3 and 6 November 2026, Zendesk rolled out a set of changes to its messaging Web Widget. Announced on 5 November, they include a new pre-conversation page and a redesigned message composer. One part of the update is worth knowing about if you run a support queue: with the pre-conversation page, a conversation is created only when the visitor actually sends a message.
The other part matters just as much: according to Zendesk's own instructions, that useful half is enabled through its developer APIs. The half that arrives automatically is the composer redesign.
Zendesk describes the pre-conversation page this way:
"Greet end users before a conversation begins with a customized title, subtitle, icon, and suggested prompts. Conversations are created only when a user sends a message, helping keep your conversation queues organized."
Alongside it come layout options: where the privacy notice appears (top of the message log by default, or below the composer), and whether "End conversation" stays a header button or moves into the overflow menu. There is also a redesigned composer:
"Attachments are now displayed as chips within the composer, allowing users to send text and attachments together in a single message rather than sending files instantly upon selection."
Zendesk's own reasoning is direct:
"Keep conversation queues clean: Tickets and chat records are generated only when a user sends an initial message, ensuring agents focus exclusively on active requests."
Anyone who has worked a chat queue knows the problem this addresses. A visitor clicks the launcher out of curiosity, sees the greeting and closes the tab. If that creates a record, an agent eventually has to look at it, decide it is empty and close it. Each one takes seconds. Across a busy week of them, it is real time spent on conversations that never happened, and they also distort reporting: a "conversation" count that includes people who never typed is not a measure of demand.
Waiting for the first message before creating anything is the sensible default, and it is good to see it stated as a design goal.
The "What do I need to do?" section of the announcement splits the update in two:
"The pre-conversation page can be enabled using the Set Behavior API, while composer and message log layout options are configured via the Set Customization API."
"The redesigned composer and updated attachment handling are applied automatically and require no administrator action."
So, in practice:
That is a reasonable way to ship it. A pre-conversation page changes what every visitor sees first, and an opt-in avoids surprising teams that have tuned their greeting. But the announcement gives only the API route, and describes no Admin Center setting. An admin who reads "new Web Widget customization" should expect someone to add a call to the widget's embed code.
We build DeskLeap, a helpdesk with ticketing, live chat and a knowledge base, so we are not neutral about chat widgets. This post is about Zendesk's change and what a Zendesk admin needs to do to get the useful part of it. If you are on Zendesk and empty chats are a problem, the pre-conversation page is worth an afternoon of a developer's time.
All quotations are from Zendesk's announcement, read in full on 9 November 2026:
If Zendesk updates the announcement and we have missed it, tell us and we will correct this page.