-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add an optional test receipt and test "boss" to receive the expense in the Submit flow #51513
Comments
We're working on mocks for this so still making progress. |
Working on the proposal here: https://expensify.slack.com/archives/C07HPDRELLD/p1730244332711079?thread_ts=1729818780.617059&cid=C07HPDRELLD |
I'm actually going to start writing a design doc for this one. |
We're still working on the finalised proposal. |
Sent it out to recruit an engineer today! |
@danielrvidal Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Design doc is here!Please take a look at this when you have a chance! I am leaving the Daily on this one as it is a CRITICAL feature in a high-priority room. @grgia will likely start working on detailed later this week. |
@grgia and the team are working on this daily! |
@danielrvidal, @grgia Whoops! This issue is 2 days overdue. Let's get this updated quick! |
We're working on this daily, updates in convert. |
We've been working on this daily. |
We're getting pretty close to done! |
Chugging through the BE, but things have been going well! Julian and Jakub from CS have been on top of the FE as well |
FE is making loads of progress, BE PR for the payment logic is in review! Chat logic is in progress! |
@danielrvidal, @grgia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
FE PRs up, BE chatbot v1 is in progress |
Daily progress in Slack! |
NEARLY there! Getting the transaction chat trigger done today |
Being worked on daily! |
Design Doc
Problem: People are interested in testing SmartScan, but can't because they don't have a real receipt.
Proposal: Add an optional test receipt and test "boss" to receive the expense in the Submit flow
Background: Increasing conversion is super important for both the top down flow and bottom up flow. The bottom up flow is something that is pretty unique to Expensify. Even if it does not generate the large majority of workspaces, it is a growth funnel that is unique to Expensify and thus can be a source of revenue our competitors don’t have. Thus, it is important to continue to improve and iterate on.
Problem: Out of 710 Production web users that selected the intention “Get paid back by my employer” in the last 30 days only 145 (20%) end up creating an actual expense. Thus most never experience the aha moment, do not hang around, and do not ever bring in their decision maker. Anecdotally, we see a lot of users in FullStory start to go through the submission flow to back out and the drop off.
Solution: In the Submit expense flow, let's add a low risk option for the user to experience the aha moment. For a user that has never scanned an expense and submitted to someone
In the Scan step, show an optional link to use a test receipt we offer to scan to create the expense
In the next step, show an optional "[email protected]" under Contacts for the user to submit to.
The flow will look something like this:

On web:


The text was updated successfully, but these errors were encountered: