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

Cancelation flow's help link should open omnichannel instead of redirecting to /help #93568

Closed
jjchrisdiehl opened this issue Aug 15, 2024 · 2 comments
Assignees
Labels
[Feature Group] Support All things related to WordPress.com customer support. [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@jjchrisdiehl
Copy link
Contributor

Quick summary

When a customer proceeds through the cancelation flow they have the option to 'Ask a Happiness Engineer' if they have a question:

image

This link leads them to our general /help page which would then require a customer to click on 'Get help' to open an omnichannel chat:

image

A more optimal path may be to open the omnichannel chat directly from the cancellation page, similar to a pre-sale chat during Checkout. This would allow us quick access to a churning customer for one last attempt to address any concerns.

Happy path:
image

@Automattic/martech Is this an oversight or is this the expected behavior of the 'Ask a Happiness Engineer' link?

Steps to reproduce

  • Go to /purchases, click on a non-expired plan
  • Click on Cancel [product] at the bottom of the page
  • Click on 'Ask a Happiness Engineer'

What you expected to happen

I would expect priority access to a person, especially if I am having trouble using the product and I'm also willing to contact support from the cancelation page.

What actually happened

Instead I'm redirected to a generic /help page which makes me take extra steps for direct support from a person.

Impact

All

Available workarounds?

Yes, easy to implement

If the above answer is "Yes...", outline the workaround.

The work around is already completed here #93567

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@jjchrisdiehl jjchrisdiehl added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Aug 15, 2024
@jjchrisdiehl jjchrisdiehl self-assigned this Aug 15, 2024
@github-actions github-actions bot added the [Pri] Normal Schedule for the next available opportuinity. label Aug 15, 2024
@jjchrisdiehl
Copy link
Contributor Author

I have an open PR for this issue here #93567

I'm not sure of all of the inner workings of Odie, but if there is a way to funnel these contact requests into a 'pre-cancellation' flow it would help our support prioritize them.

Maybe @alshakero knows a bit more here?

@jartes jartes added Triaged To be used when issues have been triaged. [Feature Group] Support All things related to WordPress.com customer support. and removed Needs triage Ticket needs to be triaged labels Aug 21, 2024
@matticbot matticbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Aug 21, 2024
@jartes jartes added the [Product] WordPress.com All features accessible on and related to WordPress.com. label Aug 21, 2024
@jjchrisdiehl
Copy link
Contributor Author

Merged PR, closing.

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] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Development

No branches or pull requests

2 participants