# 1. Email Campaigns User Type: **Super Administrator** Source: *Mi Digital Academy - Education CRM Features Document* --- ## 1. Email Campaigns ### 1.1 Drip Campaigns for Onboarding **What it does:** Runs the drip campaigns for onboarding: the drip campaign (the campaign, the email, the sequence, the trigger, the schedule) is run for the onboarding of the new users, so the new users are guided through the onboarding (the drip is the sequence). The Super Administrator runs the drip campaigns for onboarding (the campaign, the email, the sequence, the trigger, the schedule) so the drip is structured and the onboarding is explicit. **Sub-features:** - Drip campaign: the campaign (the campaign, the email, the sequence, the trigger, the schedule) - Email: the email (the email, the subject, the body, the link) - Sequence: the sequence (the sequence of the emails, the order, the timing) - Trigger: the trigger (the trigger of the campaign, e.g., the signup, the course start) - Schedule: the schedule (the schedule of the emails, the delay, the frequency) - Campaign status: the status (the active, the paused, the completed) - Campaign view: the view (the campaigns, the emails, the sequences, the schedules) - Audit logging of the drip campaign configuration **Super Administrator User Journey:** 1. Super Admin runs the drip campaign for onboarding: the campaign (the campaign, the email, the sequence, the trigger, the schedule), the emails (the email, the subject, the body, the link), and the trigger (the trigger of the campaign, e.g., the signup, the course start); the drip is explicit. 2. Creates the emails: the email (the email, the subject, the body, the link); the email is the message. 3. Sets the sequence: the sequence (the sequence of the emails, the order, the timing); the sequence is the order. 4. Sets the trigger: the trigger (the trigger of the campaign, e.g., the signup, the course start); the trigger is the start. 5. Sets the schedule: the schedule (the schedule of the emails, the delay, the frequency); the schedule is the timing. 6. Views the campaign status: the status (the active, the paused, the completed); the status is the state. 7. The drip is running: the campaigns, the emails, the sequences, the schedules, so the onboarding is complete. 8. The drip campaign configuration is audit-logged with the campaign, the trigger, and the timestamp. **Rules & Edge Cases:** - The drip campaign is the sequence (the campaign, the email, the sequence, the trigger, the schedule); the drip is the flow. - The email is the message (the email, the subject, the body, the link); the email is the content. - The sequence is the order (the sequence of the emails, the order, the timing); the sequence is the path. - The trigger is the start (the trigger of the campaign, e.g., the signup, the course start); the trigger is the event. - The drip is running (the campaigns, the emails, the sequences, the schedules); the onboarding is managed. - Drip campaign configuration is audit-logged with the campaign, trigger, and timestamp. ### 1.2 Re-engagement Emails for Inactive Users **What it does:** Sends the re-engagement emails for the inactive users: the re-engagement email (the email, the user, the trigger, the schedule) is sent for the inactive users, so the inactive users are re-engaged (the re-engagement is the win-back). The Super Administrator sends the re-engagement emails for the inactive users (the email, the user, the trigger, the schedule) so the re-engagement is structured and the win-back is explicit. **Sub-features:** - Re-engagement email: the email (the email, the user, the trigger, the schedule) - Inactive user: the user (the inactive user, the inactivity, the date) - Inactivity trigger: the trigger (the trigger of the inactivity, e.g., the 7 days, the 30 days) - Email content: the content (the content of the email, the subject, the body, the offer) - Schedule: the schedule (the schedule of the email, the delay, the frequency) - Campaign status: the status (the active, the paused, the completed) - Campaign view: the view (the emails, the users, the triggers, the schedules) - Audit logging of the re-engagement email configuration **Super Administrator User Journey:** 1. Super Admin sends the re-engagement email for the inactive users: the email (the email, the user, the trigger, the schedule), the users (the inactive user, the inactivity, the date), and the trigger (the trigger of the inactivity, e.g., the 7 days, the 30 days); the re-engagement is explicit. 2. Selects the inactive users: the user (the inactive user, the inactivity, the date); the user is the target. 3. Sets the inactivity trigger: the trigger (the trigger of the inactivity, e.g., the 7 days, the 30 days); the trigger is the condition. 4. Creates the email content: the content (the content of the email, the subject, the body, the offer); the content is the message. 5. Sets the schedule: the schedule (the schedule of the email, the delay, the frequency); the schedule is the timing. 6. Views the campaign status: the status (the active, the paused, the completed); the status is the state. 7. The re-engagement is running: the emails, the users, the triggers, the schedules, so the win-back is complete. 8. The re-engagement email configuration is audit-logged with the email, the trigger, and the timestamp. **Rules & Edge Cases:** - The re-engagement email is the win-back (the email, the user, the trigger, the schedule); the email is the message. - The inactive user is the target (the inactive user, the inactivity, the date); the user is the recipient. - The inactivity trigger is the condition (the trigger of the inactivity, e.g., the 7 days, the 30 days); the trigger is the rule. - The schedule is the timing (the schedule of the email, the delay, the frequency); the schedule is the control. - The re-engagement is running (the emails, the users, the triggers, the schedules); the win-back is managed. - Re-engagement email configuration is audit-logged with the email, trigger, and timestamp. ### 1.3 Promotional Email Blasts **What it does:** Sends the promotional email blasts: the promotional email (the email, the audience, the content, the date) is sent to the audience, so the promotion is broadcast (the blast is the broadcast). The Super Administrator sends the promotional email blasts (the email, the audience, the content, the date) so the blast is structured and the broadcast is explicit. **Sub-features:** - Promotional email: the email (the email, the audience, the content, the date) - Audience: the audience (the audience of the email, the segment, the count) - Email content: the content (the content of the email, the subject, the body, the offer) - Send date: the date (the date of the send, the time) - Send status: the status (the scheduled, the sent, the completed) - Open rate: the rate (the rate of the opens, the percentage) - Click rate: the rate (the rate of the clicks, the percentage) - Audit logging of the promotional email blast **Super Administrator User Journey:** 1. Super Admin sends the promotional email blast: the email (the email, the audience, the content, the date), the audience (the audience of the email, the segment, the count), and the date (the date of the send, the time); the blast is explicit. 2. Selects the audience: the audience (the audience of the email, the segment, the count); the audience is the target. 3. Creates the email content: the content (the content of the email, the subject, the body, the offer); the content is the message. 4. Sets the send date: the date (the date of the send, the time); the date is the moment. 5. Sends the email: the send (the send of the email, the time, the status); the send is the action. 6. Views the open rate: the rate (the rate of the opens, the percentage); the rate is the measure. 7. Views the click rate: the rate (the rate of the clicks, the percentage); the rate is the measure. 8. The blast is sent: the emails, the audiences, the content, the dates, so the broadcast is complete. 9. The promotional email blast is audit-logged with the email, the audience, and the timestamp. **Rules & Edge Cases:** - The promotional email is the broadcast (the email, the audience, the content, the date); the email is the message. - The audience is the target (the audience of the email, the segment, the count); the audience is the recipient. - The send date is the moment (the date of the send, the time); the date is the schedule. - The open rate is the measure (the rate of the opens, the percentage); the rate is the engagement. - The blast is sent (the emails, the audiences, the content, the dates); the broadcast is managed. - Promotional email blast is audit-logged with the email, audience, and timestamp. ### 1.4 Personalized Course Recommendations **What it does:** Sends the personalized course recommendations: the recommendation (the recommendation, the user, the course, the reason, the date) is sent to the user, so the user is recommended the relevant courses (the recommendation is the personalization). The Super Administrator sends the personalized course recommendations (the recommendation, the user, the course, the reason, the date) so the recommendation is structured and the personalization is explicit. **Sub-features:** - Recommendation: the recommendation (the recommendation, the user, the course, the reason, the date) - User: the user (the user, the profile, the history) - Course: the course (the course, the name, the recommendation) - Recommendation reason: the reason (the reason of the recommendation, e.g., the history, the interest) - Recommendation date: the date (the date of the recommendation, the time) - Recommendation status: the status (the sent, the opened, the clicked) - Recommendation view: the view (the recommendations, the users, the courses, the dates) - Audit logging of the recommendation sending **Super Administrator User Journey:** 1. Super Admin sends the personalized course recommendation: the recommendation (the recommendation, the user, the course, the reason, the date), the users (the user, the profile, the history), and the courses (the course, the name, the recommendation); the recommendation is explicit. 2. Selects the users: the user (the user, the profile, the history); the user is the recipient. 3. Selects the courses: the course (the course, the name, the recommendation); the course is the content. 4. Sets the recommendation reason: the reason (the reason of the recommendation, e.g., the history, the interest); the reason is the logic. 5. Sets the recommendation date: the date (the date of the recommendation, the time); the date is the moment. 6. Sends the recommendation: the send (the send of the recommendation, the time, the status); the send is the action. 7. Views the recommendation status: the status (the sent, the opened, the clicked); the status is the state. 8. The recommendation is sent: the recommendations, the users, the courses, the dates, so the personalization is complete. 9. The recommendation sending is audit-logged with the recommendation, the user, and the timestamp. **Rules & Edge Cases:** - The recommendation is the personalization (the recommendation, the user, the course, the reason, the date); the recommendation is the match. - The user is the recipient (the user, the profile, the history); the user is the target. - The course is the content (the course, the name, the recommendation); the course is the offer. - The recommendation reason is the logic (the reason of the recommendation, e.g., the history, the interest); the reason is the basis. - The recommendation is sent (the recommendations, the users, the courses, the dates); the personalization is managed. - Recommendation sending is audit-logged with the recommendation, user, and timestamp. ### 1.5 A/B Testing for Campaigns **What it does:** Runs the A/B testing for the campaigns: the A/B test (the test, the variant, the audience, the metric, the result) is run for the campaigns, so the best variant is identified (the test is the experiment). The Super Administrator runs the A/B testing for the campaigns (the test, the variant, the audience, the metric, the result) so the test is structured and the experiment is explicit. **Sub-features:** - A/B test: the test (the test, the variant, the audience, the metric, the result) - Variant: the variant (the variant of the test, e.g., the A, the B) - Audience: the audience (the audience of the test, the segment, the count) - Test metric: the metric (the metric of the test, e.g., the open rate, the click rate) - Test result: the result (the result of the test, the winner, the percentage) - Test status: the status (the running, the completed, the analyzed) - Test view: the view (the tests, the variants, the audiences, the metrics) - Audit logging of the A/B test configuration **Super Administrator User Journey:** 1. Super Admin runs the A/B test for the campaign: the test (the test, the variant, the audience, the metric, the result), the variants (the variant of the test, e.g., the A, the B), and the audience (the audience of the test, the segment, the count); the test is explicit. 2. Creates the variants: the variant (the variant of the test, e.g., the A, the B); the variant is the option. 3. Selects the audience: the audience (the audience of the test, the segment, the count); the audience is the target. 4. Sets the test metric: the metric (the metric of the test, e.g., the open rate, the click rate); the metric is the measure. 5. Runs the test: the run (the run of the test, the time, the status); the run is the action. 6. Views the test result: the result (the result of the test, the winner, the percentage); the result is the outcome. 7. Views the test status: the status (the running, the completed, the analyzed); the status is the state. 8. The test is complete: the tests, the variants, the audiences, the metrics, so the experiment is complete. 9. The A/B test configuration is audit-logged with the test, the variant, and the timestamp. **Rules & Edge Cases:** - The A/B test is the experiment (the test, the variant, the audience, the metric, the result); the test is the comparison. - The variant is the option (the variant of the test, e.g., the A, the B); the variant is the choice. - The audience is the target (the audience of the test, the segment, the count); the audience is the recipient. - The test metric is the measure (the metric of the test, e.g., the open rate, the click rate); the metric is the value. - The test is complete (the tests, the variants, the audiences, the metrics); the experiment is managed. - A/B test configuration is audit-logged with the test, variant, and timestamp.