Zendesk is excited to announce that customers can now control when the messaging composer is shown in the Messaging Web Widget, as well as the iOS, Android and Unity SDKs.
Announced on | Rollout starts | Rollout ends |
October 15, 2025 | October 14, 2025 | October 15, 2025 |
This announcement includes the following topics:
What is changing?
Previously, the messaging composer was always visible. Now, you have the option to hide it in situations where it might be more beneficial. For example, when you want users to select options from a form instead of typing a response.
Why is Zendesk making this change?
This update aims to improve the user experience by helping you guide users through the most suitable interaction flow in their conversations. It’s especially valuable when immediate, predictable, or structured responses are necessary to fulfill legal obligations, prevent confusion, direct users to specific AI Agent flows, or maintain an overall seamless experience. Additionally, it can be useful to hide the composer while users are waiting for an agent to join or while they are on hold.
What do I need to do?
You can hide the messaging composer by using the blockChatInput
parameter in the Post Message API. To hide the composer, include blockChatInput: true
in your workflow when calling the API. To show the composer again, send a subsequent message without the parameter or set blockChatInput: false
. For more information and examples, see Sending messages.
If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.