Keep learners going and celebrate completion
When to use it
Section titled “When to use it”- You run online courses or a learning app, and many learners start strongly and drift away.
- Your app sends an event for each lesson completed and another when a course is completed.
- Mentors or tutors can call learners who are slipping, and you want completions celebrated and turned into reviews.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| Events from your app or website (needs a developer) | Your learning app sends the lesson-completed and course-completed events. The course-completed event can carry a certificate link. |
| A CSV upload | No developer yet? If your platform exports lesson activity, upload it as Events every week. The nudges then run on that schedule. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Mentors | Calls learners who have gone quiet; gets the weekly report. | Empty |
| Segment | Learners gone quiet | Did a lesson in the last 30 days, none in the last 7, and hasn't finished a course lately. | Ready |
| Segment | Learners at risk | Did a lesson in the last 30 days, none in the last 14, and hasn't finished a course lately. | Ready |
| Segment | Active learners | Did a lesson in the last 7 days. | Ready |
| Template | Pick up where you left off (email) | Pick up where you left off. | Ready |
| Template | Pick up where you left off (SMS) | Second nudge by SMS. | Ready |
| Template | Course completed (email) | Congratulations with the certificate link. | Ready |
| Template | Review and share (email) | Review and referral ask two days later. Each link only shows if you set it. | Ready |
| Question | Report: active learners | Learners who did a lesson in the report's period. | Ready |
| Question | Report: course completions | Learners who completed a course in the report's period. | Ready |
| Report | Weekly: learners | The week's active learners and completions, how many are quiet or at risk, and the state of the mentor calls. | Off |
| Follow-up | Learning 1: pick up where you left off | Email, then SMS three days later, for learners who go quiet; stops when they do a lesson. | Off |
| Follow-up | Learning 2: mentor call | A mentor call task for learners at risk; the outcome is saved. | Off |
| Follow-up | Learning 3: course completed | Congratulations and the certificate link, then a review and referral ask two days later. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What should messages call your school or platform? | none, must answer | org_name |
| 2 | Where do learners go to continue a course? (your app or course page) | none, must answer | portal_url |
| 3 | Which team calls learners who have gone quiet? (mentors, tutors or one person) | Mentors | mentor_team |
| 4 | Which event means a learner completed a lesson? | Lesson Completed | lesson_event |
| 5 | Which event means a learner completed a whole course? (it can carry a certificate_url property) | Course Completed | completed_event |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Where learners can leave a review (optional) | review_url | |
| Where learners can invite a friend (optional) | referral_url | |
| Hours a mentor has to make the call | 48 | call_due_hours |
| Sender address | ‹workspace default_sender› | email_from |
| Time zone for the report | ‹workspace timezone› | timezone |
| Weekly learning report | 0 8 * * 1 | report_cron |
| Greeting when a first name is missing | there | greeting_fallback |
Timings
Section titled “Timings”- 7 days with no lesson (after lessons in the last 30 days): a "pick up where you left off" email, then an SMS 3 days later if they are still away. It stops as soon as they do a lesson.
- 14 days with no lesson: a call task for Mentors, due in 48 hours.
- Course completed: the congratulations and certificate link straight away, then a review and referral ask 2 days later.
- Weekly learning report: 0 8 * * 1 in ‹workspace timezone›.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The nudge, the congratulations and the review ask | A verified sending domain for ‹workspace default_sender›. | |
| sms | The second nudge | An SMS provider, or Origamy managed SMS after business verification (KYC). |
What you need to do
Section titled “What you need to do”- Send Lesson Completed for every lesson and Course Completed for every course, with the learner's email and phone as traits. If the course-completed event has a certificate_url property, the congratulations links to it. Otherwise it links to ‹Learning link›.
- Add people to the Mentors team. A task assigned to an empty team reaches nobody.
- Give each lesson event a stable messageId per occurrence, so retries are dropped.
- Only add a review or referral link if you want one. Leave both blank to send the thank-you without an ask.
- Verify the sending domain, connect an SMS provider or finish business verification, switch the follow-ups and report on, and test with your own account.
- Send
Lesson Completedfor every lesson andCourse Completedfor every course. Addcourse_nameandcertificate_urlproperties to the course event and the congratulations will use them; without a certificate link it points to your learning page. - “Gone quiet” needs a lesson in the last 30 days, so learners who never started aren’t nudged here. Use your onboarding playbook for them.
- Learners who finished a course in the last 90 days are left out of the nudge and the mentor call, so someone who just graduated isn’t chased.
- Review and referral links are optional. In markets where WhatsApp is the main channel (Nigeria, Kenya, India), a short “share with a friend” link that opens WhatsApp often works better than a review site.
This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval):
Our learning app sends Lesson Completed and Course Completed events. If a learner has done lessons recently but nothing for a week, email them to pick up where they left off, and text them three days later if they're still away, stopping when they do a lesson. After two weeks away, give our mentors a task to call them. When someone completes a course, email congratulations with their certificate link, then two days later ask for a review and a referral. Send our mentors a weekly report of active learners, learners at risk and completions.
It passes when every piece is a valid draft and everything lands off, with at least: segment, workflow, message_template, report.
