Initial feedback on the Agent Workspace

19 Kommentare

  • Offizieller Kommentar
    Amisha Sharma
    Zendesk Product Manager

    Hello Everyone,

    Thanks for engaging in this post. As we work on redesigning the reading and writing experience, your feedback is very valuable. I'm looking to meet with you 1:1 or in a group to get feedback on the new designs.

    Please do not post your personal information when responding to this request, but please let us know if you're open to meeting 1:1 or in a group setting to provide feedback on a few new designs. Thanks! Once we hear back from you, we'll coordinate time with you and send a calendar invite for a 30-minute session. 

  • Seconded. I am curious why such a big company like Zendesk does not understand the basic agent needs (less scrolling, fewer clicks, clear visual marks, etc.)

    3
  • Rina

    Darren Bell I agree with Point 5, the macro field would be better positioned where it originally lived, directly under the email/ correspondence field.

    0
  • Sydney Neubauer

    +1 this is all the UI feedback I had noted as well. Thank you for creating this post!

     

    Here is one of the feedback posts I made for creating better differentiation of Agent/End-user replies:https://support.zendesk.com/hc/en-us/community/posts/4408860699034-Agent-Workspace-conversation-line-breaks-color-coded-replies

    1
  • Darren Bell

    I have seen a number of similar comments spread across different posts. We looked at the Agent Workspace when it first came out but I wasn't really aware of the Zendesk Community pages at that point so had nowhere really to document my feedback. 

    I don't see any of my points as needing major effort from Zendesk to change and implement and would make a lot easier for people to migrate over - it all depends on whether Zendesk see them as part of their vision for the Agent Workspace.  Let's see how Zendesk respond.....

     

     

    0
  • Tobias Hermanns

    We need mandatory migrate to Workspace because of some feature and enhancements we need. I raise similar and more feedback years ago during early Agent Workspace phase. They didn't change anything it is not agent friendly and performance is terrible me.

    So stop dreaming.

    -1
  • Amisha Sharma
    Zendesk Product Manager

    Hello Darren Bell,

    Thanks for providing feedback. We appreciate hearing from our customers so that we can take steps in the right direction to improve the current experience. I'd like to address a couple of points and would love further engagement here:

    1. This is great feedback. This is the first time we have come across this one but it makes sense. We are currently working on redesigning how the conversation log looks, so we will take this one into account.

    2. The vertical spacing between ticket fields is based on the recommendation from our Garden design system, we'll work with them to see if we could reduce the vertical spacing between ticket fields so that agents could see more fields without having to scroll. We've also recently launched an enhancement so that agents could look at 2 or more rows of ticket fields whenever needed.

    3. Agreed that this needs to be improved. We are taking this feedback into consideration during our redesign. Besides this, we are also working on ways to better distinguish between agent response, end-user response, light agent response, and external response. We believe the new designs should help solve some of these pain points.

    4. The reasoning behind having a channel switcher is to be able to have an integrated and unified system. I understand how two clicks instead of previously one click can be annoying and can seem unnecessary, but this will help us scale well if there are new channels added to the channel switcher. Since everything is in one place, we could have any number of channel switch options in a single ticket.

    How would you feel about using the keyboard shortcuts to switch channels? We provide keyboard shortcuts to open a public reply box and an internal note box in the composer.

    5. We do understand the frustration with this change and I'll share this feedback with the team. This change was made in order to provide our customers with the ability to configure the layout of their ticket interface. We want to provide a flexible workspace and this change will help achieve that from a technical standpoint.

    6. Thanks! We'll look into ways to improve the internal comment posting during our redesign.

    Appreciate the engagement here! We are working towards some of these pain points.

     

    0
  • Anne-Flore Caire

    Hello

    To complete this feedback, our company's feedback is as follows. We have migrated to the new workspace. And the next day, we went backwards, because :

    1) And this is the main reason: we no longer see the recipients and CC of the received and sent emails! On exchanges with multiple interlocutors with some added in exchange, it's impossible to do without! To compensate for the disappearance of this basic display in a ticketing system, the agents have to display the Events, which is not desirable for our employees who work in particular on tickets with several dozen comments

    2) The fact of having the input field at the bottom means that when you open a ticket, you are automatically moved to the bottom, at the end of the last message received. But when Zendesk can't identify the history of emails to a reply, and leaves everything displayed, you have to scroll up, and sometimes a lot, to get to the beginning of the last message (which should be the target of the arrival on the ticket).

    3) The loss of the small summary of the arrival information under the subject (email from the requester to which support email address, and via whom/what)

    4) The title of the tab shows the name of the requester and not the ticket title

    Hopefully, changes will be possible soon, as this will definitely prevent us from deploying other messaging channels

    0
  • Amisha Sharma
    Zendesk Product Manager

    Thanks for the additional feedback, Anne-Flore Caire

    1. We realize that the current display of CCs is not working in several situations. The team is currently working on a fix and we should be able to release it in the next couple of weeks. I'll update here once released. :)

    2. Thanks for the feedback. We have planned to work towards opening the ticket at the top of the latest message instead of the bottom. We should have updates on this one soon.

    3. Could you elaborate a bit more on this? We display the via channel information. What are some of the reasons your team needs the display of the requester's email address and to's email address in the ticket header? Would love to understand your workflow. Thanks!

    4. I'll share this feedback with the team. Can you share the primary channel for your business?

    Thanks for engaging!

    0
  • Amisha Sharma Hi! I would be happy to provide feedback on new design.

    0
  • Amisha Sharma
    Zendesk Product Manager

    Thanks, Tommy (Anatolii Binkovskyi). Sending you an email :)

    0
  • Tobias Hermanns

    Hi,

    please add us too for feedback.


    Thanks.

    Tobias

    1
  • Anne-Flore Caire

    Hi Amisha Sharma

    Thank you for your feedback and consideration of the points above.
    I am answering your question about my feedback on the loss of the small summary of the arrival information under the subject.

    This small summary was perfect for our agents to immediately identify the requester, his company (when possible via the domain of his email address. It also immediately identifies the most important clients), and which team was requested. 
    Most of our departments have multiple teams and multiple support emails depending on our products so we can assign requests to the right team. And some collaborators are in multiple teams so it allows them to identify the right team to respond to when they handle a ticket. It's like conscious or unconscious conditioning. 
    Another benefit is that our agents can see immediately if the ticket is from another team. We have Support and Administration departments deployed on Zendesk, so it often happens that a technical support request ends up in our Sales department, or vice versa. They have the reassignment information in the ticket, but when it is long, having this visual information first saves time for the agents in understanding the ticket they are starting to process, which may already be long. 
    In addition, we work with applications that are important to us and priority is often given to the application side rather than the requester information side.

    Best regards

    0
  • Trudy Slaght

    In regard to number 5, I have a feedback post specifically on this at https://support.zendesk.com/hc/en-us/community/posts/4505307685914-Format-issue-Macro-Menu-Location-Moved-on-March-30-now-covers-part-of-forms 

    We have stayed in agent workspace as we needed to in order for a channel integration we had to make, but our team continues to hope some of the things you've mentioned will be improved or fixed. 

    0
  • Amisha Sharma
    Zendesk Product Manager

    Tobias Hermanns - Sending you an email.

    Anne-Flore Caire- Thanks for explaining, very helpful. I'll be looking into this.

    Trudy Slaght - Shared this post with the team.

    Thanks all!

    0
  • Darren Bell

    Hi Amisha Sharma

    I also would be happy to give direct feedback on any new design

    1
  • JJ Miclat
    Zendesk Product Manager

    Hi all, 

    We've heard your feedback loud-and-clear, and have reduced the vertical spacing between ticket fields (while still taking aesthetics into account), and removed the horizontal separator between the Brand and the Requester field, so that we maximize the amount of ticket fields agents could see in their default browser viewport.

    Cheers,
    JJ

    2
  • Tommy (Anatolii Binkovskyi)

    Awesome, that's a step in the right direction. Thanks!

    1
  • Darren Bell

    Just checked in my Sandbox and yes, the ticket fields look so much better now! :-)

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk