Skip to content
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

Onboarding Emails 4.0 #150

Merged
merged 10 commits into from
Nov 21, 2023
Merged

Onboarding Emails 4.0 #150

merged 10 commits into from
Nov 21, 2023

Conversation

joethreepwood
Copy link
Contributor

@joethreepwood joethreepwood commented Nov 8, 2023

It's the biggest thing to happen to onboarding emails since 3.9.

These suggested changes would alter the way in which we check for elligibility for upselling users, and introduce three new back-up emails as fallbacks.

Changes:

  • users now receive 1x email each week for each of the first three weeks.
  • added four new fallback emails as if a user is already subscribed to all features, focusing on Betas, Community, Templates, Content
  • prepped a notebooks upsell for when that launches
  • merged AARRR email inside the welcome email
  • added have four new early-stage fall backs within the role flow at the start
  • bias towards upsell emails, over other types of comm
  • bias towards upselling Analytics, Session Replay, then Flags, then Surveys - in that order.
  • add have an onboarding flow for Analytics which includes an upsell cycle for Group Analytics.
  • reconciled the existing experiments to use the most successful variant.
  • no longer check if a user completes onboarding to send the per-feature emails when someone subscribes to a product.
  • add properties to track onboarding goals at a higher level than before

I've drafted all new content and appended as comments

Feedback on all points - including the underlying logic - greatly appreciated.

Copy link
Contributor

@ivanagas ivanagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 😄

requests-for-comments/2023-10-31-onboarding-emails.md Outdated Show resolved Hide resolved
9. Wait 1 week.
1. If `Yes`, check if the user is in the `Subscribers to Feature Flags` segment
1. If `Yes`, if the user is in the `Subscribers to Surveys` segment
1. If `Yes`, send [New email about using templates]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. If `Yes`, send [New email about using templates]
1. If `Yes`, send [New email about using Survey templates]

I do think survey templates are a lot more obvious than dashboard templates because they show when you create a new one. Maybe advanced survey usage (targeting + multi question), we have some nice tutorials upcoming for this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2023-11-09 at 14 18 25

requests-for-comments/2023-10-31-onboarding-emails.md Outdated Show resolved Hide resolved
requests-for-comments/2023-10-31-onboarding-emails.md Outdated Show resolved Hide resolved
joethreepwood and others added 2 commits November 9, 2023 09:55
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
@joethreepwood
Copy link
Contributor Author

joethreepwood commented Nov 9, 2023

I've added 4x more fall backs, for early in the flow.

13. Wait until a weekday between 1PM and 5PM in the users' time zone (UTC fallback)
14. Check if the user is in the `Subscribers to Surveys` segment
1. If `Yes`, do nothing. (See Survey onboarding flow)
1. If `Yes`, [send new email about notebooks]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2023-11-09 at 14 35 37

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of "multiple insights or sessions" maybe we should restructure to say "multiple insights and sessions".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2023-11-09 at 16 33 26

2. 50% recieve Feature Flag Upsell email 2
12. Wait 5 days.
1. If `Yes`, check if the user is in the `Subscribers to Surveys` segment
1. If `Yes`, [send new email about Toolbar]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. If `Yes`, [send new email about Toolbar]
1. If `Yes`, [send new email about handbook]

I actually think pushing some content may work best here...

Screenshot 2023-11-09 at 14 59 10

@joethreepwood
Copy link
Contributor Author

Draft content now added for each new step, so open to feedback on that too.

Copy link
Contributor

@ivanagas ivanagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a few comments on the content

@joethreepwood
Copy link
Contributor Author

I've updated to a new version.

Main changes:

  • Onboarding now takes 4 weeks, and involves an upsell cycle for Product Analytics
  • I've added an onboarding campaign for when a user subscribes to analytics, which includes an upsell to groups
  • I've defined and refocused all of the fall-back emails

@joethreepwood
Copy link
Contributor Author

I've also removed the AARRR step, to speed things up, and incorporated it directly into the welcome email.

1. If `No`, send Feature Flags Upsell email.
2. If `Yes`, check if the user is in the `Subscribers to Surveys` segment
1. If `No`, send Surveys Upsell email
2. If `Yes`, send email email about dashboard and survey templates
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll replace this with a notebooks email when it's ready

@joethreepwood
Copy link
Contributor Author

This is now ready for re-review. I've updated the top comment to summarize the current state of it, as it adds several new emails.

Copy link
Contributor

@ivanagas ivanagas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 😄

@joethreepwood
Copy link
Contributor Author

OK, the new version is available as an email and will be easier to review. This version should be the final one. Would love to get a quick check through of the logic however.

@joethreepwood joethreepwood merged commit 64b2223 into main Nov 21, 2023
@joethreepwood
Copy link
Contributor Author

Launched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants