-
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
[f-1] Audit and update all Chat UI's and invite notifications #38498
Comments
Alright, was able to "clear my plate" so to speak on a few things, so i will review the thread you posted last week, nick, and then start updating our tracking sheet. |
moving to daily to focus on this week |
Started a DOC to keep track of screenshots for styling in later phases! |
P/S sent to strategy@ cc: @maddylewis |
|
Planning out a pre-design to decide what needs to be QA'ed. |
@danielrvidal and I are still working through finalizing the pre-design that will go out this week. |
We're now a/b testing the updated version: #47108 |
Still working on the A/B test. We're just waiting on the F1 room to open. |
Still waiting on a/b testing linked above. So this will be on hold. Moving to monthly to keep it open but no update needed for a while. |
You moving this into f1 project, Dan? |
Yea, I just updated to that project and will track it there. |
We're a/b testing the subject lines to start. |
This is still ongoing but not high priority. |
Still open but no progress. We're prioritizing a/b testing. |
This is still on hold pending A/B testing. |
I am going to close this until we have concluded AB testing - let me know if you disagree. |
High level problem:
Currently, our invite notifications don’t really follow a cohesive pattern. There are many ways to invite people and then even more emails/notifications that are sent as a result of adding/updating users to workspaces, UCRs, invoice rooms and so on. We need to do an audit of all that messaging and update/standardize it all so:
The text was updated successfully, but these errors were encountered: