Follow up on rent.
Keep your own voice.
Start with an unpaid rent charge. Check the balance, prepare the appropriate reminder and review the recipient and wording. Your pilot settings govern eligible sends; required approvals still apply.
- Your message templates
- Clear follow-up stages
- Rental context

Review the tenant’s charge and recent payment activity.


Check the stage, balance threshold and property-specific message.


Eligible sends follow pilot settings; required approval and confirmation remain in place.

Write it once. The ladder personalizes every send.
Each stage's subject, email body, and text message take placeholders that resolve from the real lease at send time: the tenant's name, the exact balance, the due date, days overdue, the late fee when there is one, and a private link that takes the payment on the spot. That link needs no account and no password, so a reminder never dead-ends at a sign-in screen for the tenant who does not use the portal. Conditional blocks show a line only when it applies, so a tenant without a late fee never reads about one. A preview button renders the whole thing before you save.
A floor under the ladder, and a switch per building.
Set the minimum balance a stage will chase; anything under it is skipped, so nobody gets a certified-tone email over $2.40. Decide per stage whether leases already in eviction keep receiving reminders, since counsel usually has an opinion. And when one building runs different rules, override just that stage for just that property; removing the override snaps it back to company policy.
Collections questions
What are the five stages?
Can one building follow different rules?
Will it chase a $3 balance?
Does the AI send these on its own?
What if the tenant never set up a portal login?
Stop improvising late-rent emails.
Author the ladder once and let every property, and every tenant, hear it the way you meant it.
Included with rent collection. No per-reminder fee.