46 lines
1.7 KiB
Markdown
46 lines
1.7 KiB
Markdown
# Email Automation
|
||
|
||
The idea is to follow up on user actions. For example, if a user signs up but then doesn’t use Ruumio for an extended amount of time, we want to ask if they need any help.
|
||
|
||
## Segmentation
|
||
It’s important to segment the user base into interest groups because the emails are more personalized to the individual’s interests. Maybe this is not yet important for Ruumio because we do not have that many users 😥
|
||
|
||
## Personalization
|
||
Personalized emails have higher open and click-through rates.
|
||
|
||
## A/B Testing
|
||
A/B Testing: Experiment with different subject lines, content, or calls to action to optimize your email performance. Split testing allows you to identify what resonates best with your audience.
|
||
|
||
## Tracking
|
||
Track click-through rates, monitor which campaigns are doing well and which not so much.
|
||
|
||
|
||
## *Action Plan:*
|
||
|
||
Find out what we want to achieve with the email campaigns
|
||
1. Generate new users
|
||
2. Convert existing users to paid users
|
||
3. Provide useful content regarding Ruumio/Workshops to our users
|
||
4. ...?
|
||
|
||
Discover how we can do it technically?
|
||
1. Use N8N for most of the automation
|
||
2. Do we need to build a special API for N8N to access Ruumio to generate personalized emails/react to events
|
||
3. QStash do create send timed emails
|
||
4. How do we track open rates? Do we need to? Can we track links we put into the emails?
|
||
|
||
Create a concept of what email/email automation we want to setup?
|
||
1. First follow up after one week
|
||
2. Maybe we can find out if user used Ruumio or not
|
||
2. Success Emails?
|
||
3. “Heyy you just created your first workshop”
|
||
4. “Wow you invited 10 people to your workshop”
|
||
...
|
||
|
||
|
||
Setup technical infrastructure
|
||
|
||
Setup email workflows
|
||
|
||
Monitor
|