Tenant portal experience and payment readiness

Review tenant phone, email, lease, unit, payment schedule, and open invoices. An invitation does not fix missing data.

If lease or amount is wrong, the tenant will see the error and support requests will increase.

Before sending a payment link, confirm integration status, payment method, amount, and reference. If payment happens outside the platform, record it manually after confirmation.

Send a clear message to the tenant: what is needed, amount, due date, and how to ask for help. Vague messages increase delay.

Tenant portal, payment links, and automated messages can depend on agency settings and integrations. If not clearly visible, treat them as In Progress.

Review contact details, lease, unit, payment history, overdue balances, and maintenance requests before communication or escalation.

If the tenant appears in more than one lease, confirm the intended lease so a payment or note is not recorded against the wrong record.

Turn the article into a small dashboard action: open the related record, review the data, make the appropriate update, then document the outcome so the rest of the team can see it.

If the action involves a financial, regulatory, owner, or tenant-impacting decision, ask the responsible role to review it before final approval.

This feature or workflow is partial. Use only the controls visible in the interface and do not assume every option is available for every agency.

If a step described here is not visible in the agency dashboard, treat it as not enabled for your account and check with your admin or Product.