Update the Switch to Expensify Classic survey to drive better feedback

[danielrvidal]

Problem: We are currently prompting people who Switch to Classic with a modal asking for a reason. But we do it inconsistently (on web but not mobile), and there are too many results to look at, and the results are kind of useless because they include known complaints from users we don’t actually think should be using New Expensify, and that we aren’t going to prioritize.

Solution:

Case 1: People that are redirected into NewDot.

• This user group has the NVP tryNewDot.classicRedirect.dismissed set to false
• We show them the existing survey when they click Switch to Expensify Classic in Settings.
• We add a new page to the start of the flow to offer a call to speak to a product manager. Clicking Book a call will open this Calendly link in a new browser tab, and closes the RHP modal when clicked.
• Make the free form response page in the survey not mandatory anymore

Copy:

**Would you like to speak to a product manager?** 

By switching to Expensify Classic, you will miss out on:
* Chatting directly on expenses and reports
* Ability to do everything on mobile
* Travel and expense at the speed of chat

We'd be excited to get on a call with you to understand why. You can book one with one of our senior product managers to discuss your needs.

[No thanks]
[Book a call]

• [Internal - NW] Keep creating GHs for the research team. Engineering don't need to worry about this.

Case 2: People not redirected into NewDot

• This user group has no tryNewDot NVP OR tryNewDot.classicRedirect.dismissed===true
• We do not show them the survey when they click Switch to Expensify Classic in Settings.
• Instead, we show them a new page to educate them on how to go directly to Expensify Classic next time.

Copy:

Quick tip... 
You can go straight to Expensify Classic by visiting expensify.com. Bookmark it for an easy shortcut!
[Take me to Expensify Classic]

• [Internal - DV/TRJ] Track the button click on that page separately in FullStory, so we can see how many keep hitting this flow going forward and continue to try and curb it if it remains high. I've purposely labelled this button slightly differently to Case 1 to make it easy for us to do that.

[anmurali]

This is going to be implemented on web and hybrid app, correct? cc @AndrewGable

[AndrewGable]

Yes it should be implemented on all platforms 👍

[danielrvidal]

Asking for the next steps, let's try to make quick progress on this one!

[trjExpensify]

Updated the solution OP to reflect where we landed. My next steps:

• Get the Calendly link to include
• Confirm if any of this actually needs backend (I don't think it does).
• Get someone to start on it.

[trjExpensify]

I've been chatting to Hans and confirmed we don't need any backend here. He's going to take on the implementation for us, starting today (tomorrow his time).

Working on getting the calendly link, and I'll add it to the OP.

[trjExpensify]

Added the Calendly link to the OP, @hungvu193.

[hungvu193]

Thanks Tom, I'll prepare a PR today!

[hungvu193]

I created a PR here: #52526

Also waiting for confirmed translations here:
https://expensify.slack.com/archives/C01GTK53T8Q/p1731572881369449