Close/End Chat button
Non planifiéeThere should be a new feature added to the chat window. Make the close/end chat button more obvious, not under "options". this way people feel they have a way out of the conversation without having to look for it.
-
Commentaire officiel
Hi everyone,
Just providing a short update on this request and the direction the company is heading towards with our agent workspace and messaging experiences.
As mentioned previously, there are no planned changes to the existing Chat and Web Widget (Classic)/legacy Chat widget experience.
Agent workspace end chat behaviour
With agent workspace, the owner of the visitor session lifecycle changes and the agent gets to terminate the chat session by clicking on the 'End Chat' button. Previously, only the visitor was the owner of the session lifecycle but this is no longer the case if/when your account moves to agent workspace.
You can learn more about agent workspace and the associated changes to the Chat experience here.
Messaging experience and behaviour in Web Widget
If you decide to move from Chat to Messaging, the widget look and feel also changes (it is the same one we use with you when you reach out to our advocacy team). In Messaging, the conversations are no longer session based and are asynchronous so the need to surface an end chat button to the visitor goes away.Here is what the Messaging widget experience looks like if you haven't seen it before:
To learn more about Messaging, you can read this article. If you want to see the configuration options in the Messaging widget experience, this article does a good job listing what is currently available.
Migration options for Chat Phase 0/1 Accounts
Phase 1 accounts (legacy Support+Chat) who are not eligible for agent workspace, Suite, or Messaging can request for a handheld migration of their account to Phase 4 to become eligible.
Phase 0 accounts (legacy Chat/Zopim standalone) will have the option to migrate to Phase 4 in the later half of this year (2022) and can then choose to upgrade to the Suite/use agent workspace and/or Messaging.
You can learn more about the migration request process through this article.
Thanks,
Ramin
-
+1
While we've only been on Zopim for a week, I've personally seen at least 4 customers ask me "how do I close this thing".
There should be a nice, big, fat "End Chat" button that's not buried under a click.
-
Customers can't find close button and this makes our live support team crazy. We are a very crowded website, please add X(CLOSE) on the main chat view.
-
+1 on the prominent "close" button. It's a common UI feature found on the web. I've included a screenshot of a competitor for reference.
Thank you -
Please add a close button to the UI for end users. The current option is never found by end users and causes chat sessions to drag for much longer than they need to, tying up valuable agent resources.
Please don't refer us to the Web SDK or custom code. This is a simple fix to your UI/UX. Web users understand the difference between minimize and close functionality.
Thank you for reading
-
I honestly don't think Zendesk ever listens to crucial feedback. The only reply that we ever get it is, "It is not in the roadmap". Well, what actually is? We have tons of customers everyday asking how to close the chat, as the button to close the chat is buried underneath options and do not serve the purpose. As Dan Ross mentioned, DO NOT ask us to web SDK, API or something. YOU (Zendesk) have to fix this up. Also, the chat cannot be ended by the agent which is again a huge headache. We are done with the conversation, the agent leaves the chat room, the customer says "thank you" and it goes as another chat to another agent. And they say "welcome", leave the chat, customer says "bye" and it goes to another chat. This is just purely ridiculous and it blocks the valuable time of all our resources. Please Zendesk, JUST LISTEN to your customers' important requirements rather than adding stupid emojis as a feature.
-
Ramin,
In all your responses you are not listening to any of your customers. You clearly believe from a product perspective you are making the best choice for the customers. I suggest you look more closely at the use cases and consider this request. We have many curious customers who click on LIVE CHAT just to see what it looks like then want to "go back a page" to where they can self-serve (as you promote) and use the help center instead. By not allowing this (unless they completely reload the browser), you are creating a very negative experience for the customers and more steps to get the answers/help they need. There needs to be an option to cancel the chat request before it even starts or end the chat easily without jumping through hoops. I don't care about real estate on the widget. it doesn't take up that much space.
-
This is a big loss for a company like zopim. Think about our request again please.
-
Hi Ramin,
More to do with customers rather than analytics re when chat 'ends'.
The option that you are outlining might not be viable since we would prefer not to inject iframes for security reasons. Would like to still see what you are recommending and determine whether this would even work for us.
Given the number of folks who have requested this and there not being an official workaround, I am surprised this is not on the feature list for more than year.
Cheers,
Nari
-
Hi,
There is a big difference between minimize the chat and close it, if it is only minimized, chat is still active and it will interfere on the queue waiting time.
I understand the zopim team point of view regarding service, but different companies have different public, products and needs, therefore to provide the companies at least with the option of having the close/end chat button on chat window or not would be a very good idea.
The workaround I saw is way too complicated, I am surprised as pretty much all products (live chats) I have worked with on the last 9 years they all had a close button it seems the most basic feature to have.
Right now, We saw our selves in a position of having to finish chats with instructions on how to close it, what is far from ideal.
I hope zopim team will take our requests in consideration soon.
Thanks very much,
Regards,
-
@Nicole Thanks so much for getting this one in front of Product! I know it keeps coming up in the forums (I know I've commented on several threads on the idea, and it is a request that comes up from an agent every week or two) and it would be really great for everyone here to be able to engage on this topic!
I think we need to give credit where it's due - Nicole & Jessie on the Community team have been making a real effort the last few months to communicate forum requests out to the Product team. Every time I've seen them say they're going to try to get a PM in a conversation, a PM has come by to comment.
There must be a mountain of content in these forums to go through and watch, but I really do get the feeling now that someone at Zendesk is actively reading feedback comments in the forums and getting them in front of the right people. That's not something I could have said when we started using the platform and engaging in the community ~two years ago.
I know it's easy to get really frustrated when you're missing what feels like an obvious feature or commenting on a three year old feature request, but I think it look like things are starting to head in the right direction with regards to having the Product team engage with customers. There's now active discussions with PMs on the forums on requests like real Sandbox environments and overhauls to Views, things that have been requested for years!
I feel there's been measurable improvements made in getting Product Managers involved in conversations with customers, especially on some of the really sore longer-term requests, like this one. It's not a guarantee that every issue will get addressed, but it's an important first step, one which seldom happened before!
-
Hi all -
Thanks for your feedback. I've spoken with the product team and have some good news: in an upcoming iteration of the Chat experience specific to the Web Widget, there will be a more obvious "leave chat" icon button that - at least as currently planned - will not be buried under another menu as it is currently. The design team is determining what will be least confusing to end-users, and expects to roll this out later this year.
We'll provide more updates as we're able, but I wanted to let you know that your voices have been heard and the problem is being worked on.
-
Hello!
We are beginning our chat rollout in 2 weeks at our very large organization and anticipate that the hidden "end chat" button will be problematic for us.
I will keep the team posted - our chat volume is very high and we intend to grow chat as our main communication channel.
-
Not only is it confusing, but the customer is left in that chat and if they click "Help" again, they are put directly into that chat screen and not prompted for a subject. The initial prompt for a topic is how we hope to deflect issues and send customers to our Help Center.
Right now we use a product that is not integrated with our Help Center, however this isn't any better if, after the first chat, our customers can't get back to the initial prompt screen.
-
Yes please! If it could have a separate buttons, and possible make the options button smaller, and possibly a gear (to save size) that would be really helpful.
We've had quite a few customer complaints on how the options button is too small. Our agents already have to use a textexpander in addition to what they usually do to close out chat to let the user know where to go to end the chat. This would save our agents and our users time.
In addition to not being able to find the button, sometimes the user end just gets left open for ages, cause they don't see our message and don't end the chat. Sometimes they'll reply with a Thanks! after no one has been in chat with them, and this opens up an entire new case.
-
Hi Aswin -
Thanks for your feedback. I've escalated this with Product Management.
-
Hi Ramin,
Thanks for your response.
Are you aware of other customers who have been successful in adding a custom close button?
I approached our development team with your response and we are not able to add a custom close button because there is no way to add arbitrary HTML to the chat window.
-
Hi Nari,
Thanks for the feedback. So to be clear, customers are sending messages post chat to you or your agents asking how to end the chat?
If you are not comfortable with the iframe injection method you can potentially look at another workaround using the JS APIs:
- Use isChatting to see if there is an active chat conversion going on
- use the window.onHide callback API to trigger a dialog to ask the customer if they want to end the chat or minimise
- If they select 'end chat', use the endChat API to end the chat session.
We are actively looking into this issue in conjunction with more widget customization options. Nothing to announce just yet, but will notify you if/when more options become available.
Thanks,
Ramin -
I agree with Maisa on this one. This has caused frustration on our side as well
-
I also suggest to have prominent end chat on web, app and mobile-site. Customer is king and if he feels telling hosting company that I have ended chat or don't want to chat - he should be allowed to do so and also hosting client should honor.
-
Just adding out vote. Sorry, but the chat minimize-button that locks the widget instead of resetting it and closing chat is super confusing.
-
Just like Jenn said, the current behavior does not play well when Zendesk Chat is served through the Zendesk Web Widget.
-
I agree with Aswin, Yuwen, Steven, etc., this is a glaring omission. With agents at our end unable to unilaterally close tickets from our end , we end up with, "Zombie" chat sessions floating around until the customer closes the browser window/tab or restarts their computer, possibly hours later...
-
Hi
We use the integrated chat experience but it's not clear from the icon that it closes the chat:
Is it possible to have a more universal icon for leaving chat?
Thanks
-
Hi Harriet,
If you want a more visible close button, the only option today is to build a custom widget using the Web SDK.
As for the ownership of the session being tied to the visitor and the agent not having the ability to close the chat session, this behaviour will be changed alongside some Support agent interface updates that will available in 2020.
Thanks,
Ramin -
Yes, please make it easier for customer to end the chat. Agents have been asking for a notification of when a customer leaves the chat so that they know they can close the ticket and free up a chat slot for a new customer. If customers do not know how to end a chat easily, they are just going to close their browser and we will not be notified that they have left. This is resulting in unnecessarily long handled chat times and long queue/wait times. :( This enhancement has my vote! Two thumbs up!!
-
Hi Glenn,
Thank you for taking the time to post in our Product Feedback Forum. In order to best respond to your request, I'd like to clarify a few points and offer a suggestion. First, are your customers seeing the minimize chat button in the upper right corner of the widget? They can use that to remove the conversation without having to enter into the options menu.
Have your customers expressed the need to immediately end the chat rather than minimize it? I am wondering what exactly is the flow that your customers are following and if we have a current method that can accommodate their needs.
Sincerely,
James Peterson -
Hi Cristina,
I will reach out to you via a ticket regarding examples.
Thanks,
Ramin
-
We have been a Zopim customer for a year now, and this has come up on different occasions. The close chat seems to be hidden under Options. Is there a way to add the x close window button on top that will do the same? Users are used to seeing that in browser windows.
Can you share the script for adding a custom button to invoke the API? Thanks.
-
Hi Nari,
The code is much more complicated that invoking the JS API and is a workaround, is not officially supported by us.
If you are okay with the risk and having to support it yourself, you will need to both inject the iframe to add a close button and use the JS APIs mentioned earlier to end the chat on button click.
Are you getting customers commenting that they don't know how to close the chat after the conversation has ended? Or you worried that chat conversions are not ending 'on time'?
-Ramin
Cette publication n’accepte pas de commentaire.
51 Commentaires