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
Do not send first Zulip Updates message with onboarding messages in new organization #30053
Comments
Hello @zulip/server-bots, @zulip/server-onboarding members, this issue was labeled with the "area: onboarding", "area: bots" labels, so you may want to check it out! |
@prakhar1144 Would you be up for taking care of this one? Please flag if this is tricky; I think from a product perspective, there are other reasonable options, as long as we delay the message. |
I'm not sure if there are product decisions specific to self-hosters that need to be considered here. |
To help users focus on the onboarding experience, we no longer send the introductory "Zulip updates" message as part of onboarding in a new organization. We send it right before the first update message. Fixes zulip#30053.
To help users focus on the onboarding experience, we no longer send the introductory "Zulip updates" message as a part of onboarding. Now, we send the introductory message just before the first update message. Fixes zulip#30053.
To help users focus on the onboarding experience, we no longer send the introductory "Zulip updates" message as a part of onboarding. Now, we send the introductory message just before the first update message. Fixes #30053.
To help users focus on the onboarding experience, we should not send the introductory "Zulip updates" message ("Welcome! To help you learn about new features and configuration options, ..." as part of onboarding in a new organization.
It probably makes the most sense to just wait until we are sending the first update, and send it right before the first update message. We should drop "Welcome!" from the start of the message.
The text was updated successfully, but these errors were encountered: