Announcing Composer resize persistence - We need your feedback :)
Rollout start: May 16, 2023
Rollout end: May 19, 2023
The new composer resize capability is now available on Agent Workspace.
What’s changing?
With this release, when you resize the composer in a ticket, the new size is saved for the next tickets you open. It stays the same size until you resize the composer again. You’ll also see a new splitter button for resizing the composer, standardizing the design pattern we use for resizing. The splitter button is keyboard accessible and fixes a few other concerns with the previous design.
Why is Zendesk making this change?
Previously, if you changed the composer size, the new size would not persist when you opened another ticket. We heard your feedback and you’ll no longer be required to resize the composer each time you open a ticket.
What do I need to do?
Composer resize persistence is activated by default for all accounts that have Agent Workspace enabled.
We’d love to hear from you. Please let us know how you’re using this new capability, what’s your impression of it, and how we can improve this experience! Thank you!
-
Great useful feature without any downsides. Don't know what more to add.
-
Just a shame we have to put up with the rest of the new UI which is not good...
-
Thanks, Tommy (Anatolii Binkovskyi). Appreciate your feedback :)
Hello Vicki Irvine - We have an update on that here: https://support.zendesk.com/hc/en-us/community/posts/4409222725530/comments/5937176966042 Thanks!
-
Anything that helps is much appreciated because Zendesk has fallen so far. Every-single-ticket is a new frustration. I have to adjust that stupid editor box around to see everything. All I need to do is enter replies and notes to ticket, such an integral/primary function, but it sucks every single time. I would pay more than Zendesk itself for a desktop app that put the focus on writing replies to tickets.
-
With the current persistence, there is an unexpected outcome where if the Browser Window becomes very small (for instance, it is resized while being dragged between two monitors or Snap zones), the Composer can grow to overtake the majority of the Workspace when the window is maximized again. That new large size then persists across tickets and windows until manually resized smaller.
-
Hi all, thank you for your continued feedback here. We are monitoring this post and appreciate you sharing your thoughts with us. Thanks again!
Vous devez vous connecter pour laisser un commentaire.
6 Commentaires