Purchases: Update the cancelation survey so that it shows different reasons for Jetpack subscribers. #10506
Conversation
…easons for Jetpack subscribers. This change adds a few new cancelation responses specific to Jetpack plan subscribers and displays them accordingly during the cancelation process to only such subscribers.
|
Here is what the Jetpack reasons should look like:
|
bubel
added
.org Plans
[Feature] Purchase Management
|
Curious, why would it say "WordPress" was too hard to use, and not "Jetpack"? They're refunding that plan, not their entire use of WordPress. This is something on top of that. |
|
@sararosso If they found WordPress, as a platform, too difficult to use and no longer want to pursue it, that's an interesting insight - especially if they have a specific problem they ran into. Would love to know if Jetpack could help. |
|
I see your point, I just think it's trying to get too much out of the survey as-is, which is tied to a specific purchase, and question one focuses on reasons why you're canceling Jetpack's Plan. If Jetpack is too hard to use, that feedback will also be lost. Maybe adding an additional option to #2 - "I'm moving off WordPress" or something similar could be a good chance to follow up with users and get more information, or if this is critical, maybe adding a 3rd question altogether asking the user about their experience using WordPress and whether they intend to stay / move off / frustrated, etc. |
|
That's fair. I'll make some changes later today. |
…ancelation survey. After some feedback, this change removes one reason from the first question and adds a new reason to the second question. Test plan is the same.
|
Updated the reason groupings based on your feedback. Should now look like this:
|
|
I went through the test plan and everything worked as expected. Canceling WordPress.com Personal: Canceling Jetpack Personal: |
There was a problem hiding this comment.
Works as expected 👍 I've done tests with half of the options, and all of them worked as expected.
I've posted a couple of minor notes on the code. Also, I'm noticing that the survey for Jetpack plans is a little narrow, which is just fine, however some of the placeholders are not entirely visible:
Other than that, this LGTM 👍
| }, | ||
|
|
||
| getInitialState() { | ||
| // shuffle reason order, but keep anotherReasonOne last | ||
| const questionOneOrder = shuffle( [ | ||
| var questionOneOrder = shuffle( [ |
There was a problem hiding this comment.
Using var is discouraged in favor of let and const - since these can change, you can use let.
|
|
||
| const questionTwoOrder = shuffle( [ | ||
| var questionTwoOrder = shuffle( [ |
There was a problem hiding this comment.
Using var is discouraged in favor of let and const - since these might change in the code flow, you can use let.
…the var keyword for let. Use of the `var` keyword is discouraged, my apologies; this change substitutes that use in the code generating the different reason groupings with the keyword `let`.
|
Thanks, @tyxla! I've substituted those keywords - thanks for the lesson. Regarding the text sizing issue, the Jetpack dialog is certainly thinner than WordPress.com's since the max reason statement length is shorter. Unfortunately, I'm still unable to replicate it. I suppose we could try just reducing the font size. |
bubel
added
[Status] Ready to Merge
and removed
[Status] Needs Review
This change adds a few new cancelation responses specific to Jetpack plan subscribers and displays them accordingly during the cancelation process to only such subscribers. Currently, both Jetpack and WordPress.com subscribers see the same exact cancelation reasons, although they are primarily meant for WordPress.com subscribers. There is no change to what WordPress.com subscribers see.
Test plan:
Log in to an account that has both a WordPress.com paid subscription and a Jetpack paid subscription.
Go to /me/purchases and attempt to cancel each of the subscriptions.
Confirm that, when attempting to cancel the Jetpack subscription, you are presented with the new reasons added via this change.
Confirm that, when attempting to cancel the WordPress.com subscription, you are presented with the standard reasons.
Make sure that you can toggle each reason as expected and that the placeholder text appears where/as it should.
Confirm that each of the cancelations is successful (the product is removed) and finishes as expected.