Support escalation and bug reporting

Try refreshing, reviewing filters, confirming permissions, and opening the record directly if possible. Many issues are caused by filters or permissions.

If the issue remains, collect useful details instead of a generic description like the page does not work.

Do not send passwords, verification codes, API keys, full bank data, or unnecessary customer information. Send only what helps solve the issue.

Write: what were you trying to do, what happened, what did you expect, does it repeat, and does it affect one user or many users?

Escalate immediately if the issue blocks collections, shows wrong data to an owner or tenant, affects invoice or tax, or prevents an entire team from signing in.

Before raising an issue, collect the page URL, user role, affected record, approximate time, and an error screenshot if available. Do not send passwords, API keys, or unnecessary sensitive data.

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 is documented as an available workflow, but results can still vary by user permissions, agency settings, and data quality.

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.