-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$250] Ask our admin leads qualifying questions in Stage 1 and trigger "set up accounting integration" task #48745
Comments
On this copy, can you actually change it later? If so, where?
I kinda' worry that our top end option being 50+ employees makes us seem like we're not a fit for even MM leads, let alone ENT leads that come looking, so I wonder if we tweak these a bit to include some larger company size ranges? I.e
Sidebar: given the qualifiers on the home page for 1-9 or 10+. Will we only show this screen to ask the question again if they've selected 10+ on the sign-up page? Seems a bit repetitive to ask it again for someone who has already told us they're a VSB with an employee count of 1-9.
Instead of "None" on the accounting solution list, should we change that to "None of the above" or something? For example, if I use Microsoft Dynamics, SAP, Oracle, Sage 50 etc as my accounting solution, "None" isn't an accurate choice for me to select to answer this question. I do use an accounting solution, just not one that has an out-of-the-box connection with Expensify. |
I think the intention behind saying "Don't worry you can change this later" was to convey the fact that this doesn't mean you can't add more employees. Maybe we can reword that to convey the point, which is - give us your best guess, you're not locked down to this range per se. cc @jamesdeanexpensify |
I agree, let's use what @trjExpensify recommended for the ranges.
Also agreed, let's update that @dubielzyk-expensify can you update the Figma but maybe let's wait for James to give us alternate copy for the size range sub text and we can update in one go? |
It feels like we don't even need to add that subtext at all - the question seems straightforward enough - "How many employees do you have?" |
I think we need some copy for this. A title and description. |
Oh sorry, I was responding to my tag here. Maybe @anmurali or @trjExpensify could confirm what's needed? |
No worries, @jamesdeanexpensify! I was just generally noting that it was needed, but if you can help would be amazing 🙇 |
Sounds good!
I don't think anything is needed per se, I'd also be down for starting with no sub-titles. |
@dubielzyk-expensify could you add a comma to "1000" so it's "1,000"? Thank you! I couldn't find the figma file. Am I needed for anything else in this issue? I'm happy to help, but I want to make sure what (if anything) remains! |
Still need copy for this. |
I am waiting for Zach and Doza to come back from Netsuite conference to write this copy. But we're not blocked on building this alternate flow . Let's make that an External? @marcaaron |
Job added to Upwork: https://www.upwork.com/jobs/~021833948133359014485 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
Minor nitpicks but for the final screen there, does the intro text stay fixed and not scroll with the page? I would expect it to scroll with the page I think. Also, looks like we need to back the card padding down to 20px there too. Otherwise looking great! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Ask our admin leads qualifying questions in Stage 1 and trigger "set up accounting integration" task What is the root cause of that problem?This is a new feature What changes do you think we should make in order to solve the problem?
Then when we choose the App/src/pages/OnboardingPurpose/BaseOnboardingPurpose.tsx Lines 69 to 72 in 336e478
App/src/pages/OnboardingPurpose/BaseOnboardingPurpose.tsx Lines 69 to 72 in 336e478
What alternative solutions did you explore? (Optional) |
Looks great @dubielzyk-expensify - and thanks for filing that bug! |
@nkdengineer Thanks for the proposal. Overall the suggested flow looks good to me. 🎀 👀 🎀 C+ reviewed |
Current assignee @marcaaron is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
LGTM, but we are missing details about what to send to the API. I think we should start sending the |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
BE is in progress on this. We can split it into two front end PRs.
Sound good @nkdengineer ? |
@marcaaron That sounds good. |
@dubielzyk-expensify Does the close icon exist in the app? |
I'm not sure if it does, so if you can't find it, here is a svg you can use: |
It does! It's |
Backend changes are on production now btw. We still need the copy for the tasks. @nkdengineer let's get this PR merged and then we will come back to add the relevant task data once we have it? |
I started working on the accounting task copy here https://docs.google.com/document/d/1AgQpxsUk7zcGJDVqlsMVXckD4c3LfDFa6Ppy7jj-xl0/edit |
Great! We're almost ready here maybe we can actually get it done all in the same PR after all @nkdengineer. There are a couple of small backend changes here we are blocked on: |
Got it. |
@anmurali, @s77rt, @marcaaron, @nkdengineer Whoops! This issue is 2 days overdue. Let's get this updated quick! |
PR still under review. We are almost there |
Backend changes are fully done now and front end is very close to done. I will be going OOO on Friday so it would be great if we can get the current frontend PR merged tomorrow if possible. And maybe we can create a new ticket for the "accounting task" itself. |
P/S in slack here
Proposal: Ask top down leads relevant qualifying questions so we can customize their onboarding tasks accordingly
Problem: Expensify caters to companies of all sizes, starting from sole props all the way to companies with 1000s of employees and several entities. Further the optimal setup of a workspace varies based on other conditions such as whether the company has an accounting integration or not. The way our current onboarding is designed, it assumes the same tasks, in the same order are important to all of them. This might not be a home run with every lead and might lead to a higher abandonment rate
Hypothesis: If we ask the lead a few simple qualifying questions and use those to show them tasks that we know other leads with similar answers prioritized before adding a card on file, then we have a higher chance of converting them to paid. So, if the same or more admins finish Stage 1 and give us this info, then having this info is more valuable than their company name and first/ last name
Solution:
In Stage 1 onboarding, for users that select
Manage my team’s expenses
, drop asking for Company name and User name. Instead ask for the number of employees they want to onboard and if they have an accounting package. [External]Customize the stage 2 onboarding tasks to include accounting integration if one is selected [Internal]
Show the accounting feature as enabled in workspace settings LHN if an accounting integration is selected [External]
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @s77rtThe text was updated successfully, but these errors were encountered: