-
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
[$250] Remove the Expensify DM from onboarding #48021
Comments
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as outdated.
This comment was marked as outdated.
Almost done with frontend changes for this, but switching tasks to another issue for a second. |
Going to briefly mark this external to get a C+ assigned who can help review the PR. |
Job added to Upwork: https://www.upwork.com/jobs/~021831465852515898823 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
To clarify, we're not looking for proposals here - this will be handled internally. |
十分抱歉 !我的账户在前段时间被黑客盗用,并且传播相同的病毒文件,如果你们遇到要下载一个fix.zip的千万不要下载!就是它导致我账户被攻占的 |
Everything is deployed here and there's this issue for payment to @fedirjh, so I think we can close this. |
不要下载我前段时间发的文件,那不是我发的,是另一个人控制我,如果你使用了这个病毒文件,你也会被控制,并且疯狂转发这个病毒 |
Proposal: Remove the Expensify DM from onboarding
Background — we wanted to test if putting tasks in the Expensify DM is more effective than putting the tasks in the Concierge chat. The original goal was to have a WhatsApp style DM that is used for education. Our design has evolved and we have not found the Expensify DM to be more effective than Concierge. Here is a look at the data:
Problem: We could continue to wait for more data but we see no reason it would change AND keeping the Expensify DM has costs:
Solution: Remove the Expensify DM so all onboarding tasks live in Concierge going forward. As discussed in this thread, we will leave the Expensify DM in the accounts where it is but we will no longer be creating these DMs going forward.
I'm going to work with @francoisl on this one as he implemented it originally.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @fedirjhThe text was updated successfully, but these errors were encountered: