The triggers teams typically automate first

How payment and lifecycle actions can be sequenced

Where approvals and guardrails still matter

Automation Rules: Path: /admin/settings/automation Trigger Example Action --------- ---------------- Payment Overdue Send SMS + queue AI call Lease Expiring Send renewal email Move-In Scheduled Create checklist task Failed Access Alert staff + log Lead Stale Queue AI follow-up "Automation rules handle the repetitive work. Payment overdue for 3 days?

Payments and Dunning: Path: /admin/customers > Customer Detail > Payments Method Use Case -------- ---------- Credit/Debit Cards Most common, autopay enabled ACH Bank Transfer Lower fees, slower processing Stripe Terminal Card-present at kiosk Cash Manual recording by staff Check Manual recording with check number Day Action ----- -------- Day 1 Payment fails, automatic retry Day 2 Email + SMS notification sent Day 5 Second retry attempt Day 7 AI collections call queued Day 14 Third retry, late fee applied Day 30 Account lockout (gate code suspended) Day 45 Lien warning sent Day 60 Sent to collections "Automated dunning handles delinquencies. The system retries automatically, sends notifications, and queues AI collections calls.

Tasks and Alerts: Path: /admin (dashboard alerts) or via command palette Alert Priority Action ------- ---------- -------- Payment Overdue High AI collections call Low Inventory Medium Adjust pricing Maintenance Due Low Create task Move-In Today Medium Prepare unit Lease Expiring Medium Renewal outreach Feature Description --------- ------------- Categories Maintenance, Collections, Move-in, Move-out, General Assignment Assign to staff members Due dates With reminder notifications Automation Tasks created by automation rules "The system creates tasks automatically based on triggers - payment overdue, move-in scheduled, maintenance due. Staff see their task queue with priorities and due dates." ---

Use this guide when designing rollout sequences for reminders, follow-up, and delinquency workflows.