Repayment reminders
When to use it
Section titled “When to use it”- Borrowers repay on a schedule your loan system knows.
- Your system can keep the next repayment date and whether it's paid on each profile, and send an event when a repayment is received.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| A Google Sheet or Excel file, synced | Your loan book in Google Sheets or Excel, synced every hour as People: phone, next_repayment_due, repayment_status. |
| Events from your app or website (needs a developer) | Or your loan system updates the traits and sends the repayment event. |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Team | Collections | Calls borrowers with a late repayment. | Empty |
| Team | Collections supervisors | Hears about late-repayment calls not made in time. | Empty |
| Segment | Repayment due in 3 days | Repayment due within 3 days, unpaid. | Ready |
| Segment | Repayment due today | Repayment due today, unpaid. | Ready |
| Segment | Repayment missed | Repayment missed in the last 30 days. | Ready |
| Template | Repayment due soon (SMS) | SMS 3 days before. | Ready |
| Template | Repayment due soon (email) | Email 3 days before. | Ready |
| Template | Repayment due today (SMS) | SMS on the due day. | Ready |
| Template | Repayment missed (SMS) | SMS after a missed repayment. | Ready |
| Follow-up | Repayment 1: due in 3 days | Daily run over "due in 3 days". | Off |
| Follow-up | Repayment 2: due today | Daily run over "due today". | Off |
| Follow-up | Repayment 3: missed | Daily run over "missed": an SMS, then a collections call with escalation. Exits on repayment. | 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 trait holds the next repayment date? | next_repayment_due | due_trait |
| 3 | Which event means a repayment was received? | Repayment Received | repaid_event |
| 4 | Which team calls when a repayment is late? | Collections | collections_team |
| 5 | Who should hear if a late-repayment call isn't made in time? | Collections supervisors | supervisor_team |
| 6 | Where do borrowers repay? (your app or a payment page) | none, must answer | pay_url |
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 |
| Daily send time | 09:00 | send_time |
| Time zone for the daily run | ‹workspace timezone› | timezone |
Timings
Section titled “Timings”- Every day at 09:00 (‹workspace timezone›).
- Email and SMS 3 days before, SMS on the due day, SMS the day after a missed repayment, then a call task due in 24 hours that escalates to Collections supervisors after 24.
- The missed-repayment run stops when Repayment Received arrives.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| sms | All three reminders | An SMS provider, or Origamy managed SMS after business verification (KYC). |
| The early reminder | A verified sending domain for ‹workspace default_sender›. |
What you need to do
Section titled “What you need to do”- Fill repayment_status for everyone (paid or due). A blank status never matches, so that person gets no reminder.
- Keep next_repayment_due (ISO date) and repayment_status (paid or due) current on each borrower's profile, and send Repayment Received when a repayment lands.
- Add people to the Collections and Collections supervisors teams.
- Review the wording against your regulator's rules for collections. Reminders stay factual; never threaten, shame or contact third parties.
- Connect an SMS provider or finish business verification, then switch the follow-ups on and test with your own number.
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):
Remind borrowers three days before each repayment and on the due date by SMS. If they miss it, text them the next day and have collections call; if collections doesn't call within a day, escalate to a supervisor. Stop when the repayment comes in.
It passes when every piece is a valid draft and everything lands off, with at least: segment, workflow, message_template.