KYC nudge
When to use it
Section titled “When to use it”- People sign up for a loan, wallet or account and must verify their identity before they can use it.
- Your system sends an event when someone signs up and another when verification is approved.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| Events from your app or website (needs a developer) | Your app sends the sign-up and KYC-approved events. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Onboarding | Calls people who haven't verified. | Empty |
| Segment | Signed up, not verified | Signed up in the last 30 days, not verified. | Ready |
| Template | Finish verification (SMS) | First reminder by SMS. | Ready |
| Template | Finish verification (email) | Second reminder by email. | Ready |
| Follow-up | KYC nudge | SMS, email, then a call task; exits on approval. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What should messages call your company? | none, must answer | org_name |
| 2 | Which event means someone signed up? | Signed Up | signup_event |
| 3 | Which event means their verification was approved? | KYC Approved | approved_event |
| 4 | Where do they finish verification? (your app or a deep link) | none, must answer | app_url |
| 5 | Which team calls people who still haven't verified? | Onboarding | onboarding_team |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Sender address | ‹workspace default_sender› | email_from |
| Greeting when a first name is missing | there | greeting_fallback |
Timings
Section titled “Timings”- SMS 1 day after sign-up, email 3 days later, call task 3 days after that (due in 48 hours).
- Stops as soon as KYC Approved arrives.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| sms | The first reminder | An SMS provider, or Origamy managed SMS after business verification (KYC). |
| The second reminder | A verified sending domain for ‹workspace default_sender›. |
What you need to do
Section titled “What you need to do”- Send Signed Up and KYC Approved from your backend.
- Never ask for ID numbers, documents, PINs or one-time codes by message. These messages only point to your app; say so on your support pages so customers can spot fakes.
- Add people to the Onboarding team.
- Connect an SMS provider or finish business verification, verify the sending domain, then switch the follow-up on and test it.
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):
People sign up for our loan app but many never finish KYC. Text them the day after sign-up, email them a few days later, and then have our onboarding team call. Stop once their KYC is approved.
It passes when every piece is a valid draft and everything lands off, with at least: workflow, message_template.