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

Improvement: Provide different landing page and ticket notes for "I need help, please contact/guide me" option during migration flow #97664

Open
cuemarie opened this issue Dec 19, 2024 · 4 comments · May be fixed by #98092
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. [Feature] Site Migration Features related to site migrations to WPcom [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Status] In Progress [Type] Feature Request Feature requests

Comments

@cuemarie
Copy link

cuemarie commented Dec 19, 2024

What

TLDR

Clicking this link should lead to a "We'll be in touch" type of landing page instead, that does not promise we can/will migrate their site yet. I think it should also not set the destination site into "migration started", and, ideally, the zendesk tickets this flow generates can be updated to be more accurate to where the customer asked for help in the process.

Current Flow

During the migration flow, there are a couple points at which a customer can select I need help, please contact me; once on the "Tell us about your WordPress site" page, and also on the "Looks like there's been a mix-up" page, (I need help, please guide me) if a customer tries the flow with a non-wp site.

Tell us about your WordPress Site Looks like there's been a mix-up
Image Image

Clicking this link on either page takes the user to the same "We'll take it from here!" page we show when they do submit a WP site and credentials, which advises that the customer is all done, and sets the expectation that we'll migrate their site in 2-3 business days.

Image

It also then changes their destination site into "Migration Started", and again sort of promises the user their migration is happening.

Image


Lastly, these flows generate a generic ticket in the migration queue, identical between the two flows noted above, with the following note:

The user has requested an assisted migration in one of our migration flows. This ticket was created automatically to get the request into our ZenDesk migration queue. Next steps are to contact the user to get migrations details from them.

Examples:

  1. Ticket from "Tell us about your WordPress site": 9196241-zen
  2. Ticket from "Looks like there's been a mix-up": 9196268-zen

Why

If a customer is submitting a site that is not a WordPress site, they should not be told that their migration is in process and that we'll be done in 2-3 business days, as this is not true. They are about to get one of two possible emails from support:

  1. (If they have a WP site) details on what to expect, and a request for their credentials in order to get started; i.e., their migration is not underway until they reply.
  2. (If they have a non-WP site) a reply stating we cannot migrate their site; which is likely to be frustrating after the flow just told them it was underway.

How

For the customer's experience, a We'll be in touch soon! page would be much better; it could also reiterate that "If your site is not yet built with WordPress, then we can't migrate it for you, but here are some links and also DIFM instead".

For the Tickets in Zendesk, noting where they were in the flows when they asked for help would be helpful context for HEs. For example:

From the Tell us about your WordPress site page:

The user has requested we contact them about a migration in lieu of sharing any WordPress site credentials or Backup files. Please double check their submitted source site.

From the Looks like there's been a mix-up page:

The user has requested we contact them about a migration, but the migration flow detected their source site is not built with WordPress. Please double check their submitted source site.

@cuemarie cuemarie added [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. [Feature] Site Migration Features related to site migrations to WPcom [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Feature Request Feature requests labels Dec 19, 2024
Copy link

github-actions bot commented Dec 19, 2024

Support References

This comment is automatically generated. Please do not edit it.

  • 9196241-zen
  • 9196268-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Dec 19, 2024
@Robertght
Copy link

I'm not changing its type yet, but I agree it would be great to have and improve clarity and expectations, especially for newcomers.

I'm adding a High priority and flagging it for @Automattic/serenity

@Robertght Robertght added the [Pri] High Address as soon as possible after BLOCKER issues label Dec 20, 2024
@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Dec 20, 2024
@cuemarie
Copy link
Author

Thanks! I should have added that I also chatted about this with Serenity here: p1734625232781969-slack-C0Q664T29

@gabrielcaires
Copy link
Contributor

gabrielcaires commented Jan 8, 2025

@cuemarie The correct step page should be this:
Image

The PR Site Migration: Show correct landing page when the user asks for help #98092 is fixing it.

Thanks for reporting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature Group] Content Management Features related to the tools and screens that admins use to manage their sites core content. [Feature] Site Migration Features related to site migrations to WPcom [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Status] In Progress [Type] Feature Request Feature requests
Projects
Development

Successfully merging a pull request may close this issue.

4 participants