- People sign up (or pay) and then have to do something to get value, like finishing their profile, completing onboarding or a first lesson.
- Your app sends an event when someone signs up and another when they finish getting started.
| How | What |
|---|
| Events from your app or website (needs a developer) | Your app sends the start and done events. Without an app, use a sign-up form as the start event and a staff form ("onboarding done") as the done event. |
| Kind | Name | What it does | Lands |
|---|
| Segment | Joined, not finished getting started | Joined in the last 30 days and hasn't finished getting started. | Ready |
| Template | Welcome (email) | The welcome email. | Ready |
| Template | Finish getting started (SMS) | Short "your place is saved, finish in two minutes" SMS. | Ready |
| Template | Finish getting started (email) | Second nudge by email. | Ready |
| Follow-up | Welcome | The welcome email. | Off |
| Follow-up | Finish getting started | Two nudges to finish getting started; leaves the moment they finish. | Off |
| # | Question | Default | Fills in |
|---|
| 1 | What should messages call your organisation? | none, must answer | org_name |
| 2 | Which event means someone just joined? (sign-up, first payment…) | Signed Up | start_event |
| 3 | Which event means they've finished getting started? | Onboarding Completed | done_event |
| 4 | Where do they go to finish? (a link into your app) | none, must answer | start_url |
| 5 | Which address should emails come from? | none, must answer | email_from |
These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|
| Welcome email after the start event | 2h | welcome_delay |
| First nudge (SMS) after joining | 1d | first_nudge_delay |
| Second nudge (email) after the first | 2d | second_nudge_delay |
| Greeting when a first name is missing | there | greeting_fallback |
- Welcome email 2h after Signed Up.
- If they haven't finished, an SMS nudge 1d after joining, and an email 2d after that.
- The nudges stop as soon as Onboarding Completed arrives.
| Channel | Needed for | Before it can send |
|---|
| email | The welcome email and the second nudge | A verified sending domain for ‹Sender address›, or Origamy's test sender while you try it. |
| sms | The first nudge | An SMS provider, or Origamy managed SMS after business verification (KYC). |
- Make sure your app sends Signed Up and Onboarding Completed for each person, with their email and phone on the profile.
- Verify the sending domain; for the SMS, connect a provider or finish business verification.
- Switch both follow-ups on (a follow-up only runs once it's on), run a test person through with your own phone and email, then erase them.
- The nudge stops itself. The exit condition ends the run the moment the done event
arrives, even in the middle of a delay, so nobody is nudged after finishing.
- No phone, no SMS. People without a phone number skip the SMS step and still get the email.
The request used to test the copilot on this playbook (a live eval):
When someone signs up, send a welcome email a couple of hours later. If they haven't completed onboarding after a day, text them a short reminder, then email them two days later. Stop as soon as they finish onboarding.
It passes when every piece is a valid draft and everything lands off, with at least: workflow, message_template.
