Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help: Ending a chat while a user is on /help/contact is a jarring experience. #1341

Closed
dllh opened this issue Dec 7, 2015 · 5 comments · Fixed by #1714
Closed

Help: Ending a chat while a user is on /help/contact is a jarring experience. #1341

dllh opened this issue Dec 7, 2015 · 5 comments · Fixed by #1714
Assignees
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Pri] BLOCKER Requires immediate attention. [Type] Bug When a feature is broken and / or not performing as intended
Milestone

Comments

@dllh
Copy link
Member

dllh commented Dec 7, 2015

Repro:

  1. Target a group with operators available.
  2. Navigate to /help/contact and initiate a chat.
  3. As an operator, end the chat.

Expected: There'll be some reasonable indicator that the chat has ended.

Actual: The screen refreshes to the offline contact form and shows the Sorry! We just missed you as our Happiness Engineers stepped away. notification.

To better illustrate the interaction, here's a gif of the interaction:

chat-end

It's a pretty jarring experience. I'm not sure what the proper experience here is. Maybe on !end in this scenario, we could show a notification that the chat has been ended and disable the text entry field? Cc @mattmiklic for design feedback.

@dllh dllh added [Type] Bug When a feature is broken and / or not performing as intended Live Chat [Feature Group] Support All things related to WordPress.com customer support. labels Dec 7, 2015
@dllh dllh added this to the Help: v1 milestone Dec 7, 2015
@omarjackman
Copy link
Contributor

@dllh I agree this is pretty jarring but I should note something thats missing from your test instructions: All operators go away after the chat has ended.

Typically the chat would just stay there so that you could resume it if you wanted to. This is tricky because a user might want to continue the chat after the op has ended it and then may choose to create a ticket if theres no one else to chat with.

@omarjackman
Copy link
Contributor

@dllh What bothers me most about this is the widget flicker in the bottom right corner that occurs when the chat is unmounted and the contact form gets mounted. I'm hoping that it was inperceptible and was only caught by your animated gif maker because it caught the lucky frame that showed it.

@dllh
Copy link
Member Author

dllh commented Dec 10, 2015

Wouldn't my repro still be valid in cases in which all operators are busy when the chat ends?

I don't remember noticing the flicker you point out when I was testing, but it's something we should maybe test a bit more and see if we can fix if it is in evidence outside of screen capture software.

@mattmiklic
Copy link
Member

Here's what I was thinking, based on our conversations about this previously. Keeps the chat visible, so the user can refer back to it, but disables the text field (using the styling from the standard disabled text input). Since we automatically send the user a transcript, we let them know that. The end of the chat is marked with a line and the W logo; the same treatment we use at the end of a list of posts, etc.

chat-full

(The sidebar here hasn't been updated to the latest design, but it doesn't affect the Contact Us design)

@mattmiklic mattmiklic reopened this Dec 10, 2015
@dllh dllh added the [Pri] High Address as soon as possible after BLOCKER issues label Dec 14, 2015
@omarjackman
Copy link
Contributor

I will add the notification here however the styling with the WP logo will have to come later when I start restyling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Pri] BLOCKER Requires immediate attention. [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
3 participants