Customer Lifecycle — from On Track to Lost
Lifecycle Overview
Every customer in Paymely follows a defined lifecycle. Transitions happen automatically at midnight (Toronto time) via the nightly check.
On Track → Overdue → Stopped (no follow-up) → In Settlement → Lost
↑ ↓
└────────────────────── Reset cycle ───────────────────────┘
The 8 Possible Statuses
| Status | Meaning | Trigger |
|---|---|---|
| Inactive | Added but no schedule assigned | Manual / default on creation |
| On Track | Schedule running, due date not yet passed | Schedule assignment |
| Overdue | Due date passed, after-due reminders still being sent | Automatic (nightly check) |
| Paid | Balance fully settled | Payment recorded (auto or manual) |
| Stopped (no follow-up) | All reminders exhausted, no communication running | Automatic (nightly check) |
| In Settlement | Settlement offer assigned, sequence actively sending | Settlement offer creation |
| Lost | Settlement offer expired without response | Automatic (nightly check) |
| Legal | All communication blocked (legal proceedings) | Manual only |
Transition: On Track → Overdue
When? Every night at midnight (Toronto time), the system checks all on-track customers.
Condition:
- The customer's due date is strictly past (the day after the due date)
- Balance is not fully settled
What happens:
- Status → Overdue
- Reminders continue to be sent normally (after-due stages)
Example: Due date = February 25th. The customer stays On Track all day on the 25th. At midnight on February 26th → Overdue.
Transition: Overdue → Stopped (no follow-up)
When? Same nightly check at midnight (Toronto time).
Condition:
- Customer is Overdue
- All enabled steps of all active (non-settlement) schedules are exhausted
- The last reminder date has passed
What happens:
- Status → Stopped (no follow-up)
- No more reminders are sent — the customer is waiting for a decision
Important: A Stopped customer receives no communication at all. It's up to you to decide the next step.
Transition: Stopped → In Settlement
When? When you create a settlement offer for the customer.
Condition:
- Customer is Stopped (no follow-up)
- A settlement offer is created (manually or in bulk)
What happens:
- Status → In Settlement
- If a settlement schedule is assigned → the sequence messages are sent automatically
- The customer receives the offer with a deadline to pay
Transition: In Settlement → Lost
When? Same nightly check at midnight (Toronto time).
Condition:
- Customer is In Settlement
- Associated settlement offer has expired (past its expiry date)
- No payment received
What happens:
- Status → Lost
- No more automatic sends
Transition: → Paid (automatic)
When a payment is recorded (manual or via AI reconciliation):
- If the total amount paid covers the full amount due → status automatically changes to Paid
- All ongoing reminders stop immediately
Edge case: If a partial payment is recorded and the remaining balance > 0, status remains unchanged.
Reset the Cycle
If a Stopped, In Settlement, or Lost customer comes back (e.g., dispute resolved, new agreement), you can reset their cycle:
- Open the customer profile
- Click Reset cycle
- Confirm
What resets:
- Cycle counter → 0
- Last cycle completion date → cleared
- Status → On Track
- Customer restarts at step 1 of their schedule
Cycle Counter
The cycle counter tracks how many times the customer has completed a full collection cycle. Useful for identifying repeat offenders.
Known Issue: Late-Added Customers
If you assign a schedule to a customer whose due date has already passed, the nightly check may move them to Stopped quickly if all reminders are already exhausted, without having sent any messages.
Workaround: Manually check the status after assigning a late schedule.