Other

Most miscellaneous Yardi tickets resolve when the correct codes or configuration settings are verified first, then escalated to admin or Yardi support if the underlying data is corrupted.

• Check for special characters in address fields before running screening — an apostrophe or unexpected character in a street address can silently block screening from running. Remove it and retry.
• Verify t-codes vs. r-codes in CRM IQ when generating roommate riders — CRM IQ may pull the wrong resident's code. Cross-reference the correct code directly in Voyager, update it, then regenerate the document.
• Run guarantor and applicant screening separately — Yardi does not combine both parties on a single screening report. Generate one report per person.
• Use a paper application as a fallback if an online applicant is locked out of RentCafe and a move-in deadline is imminent. Upload the completed paper form and manually enter the data to unblock the process.
• Check for a recent process or workflow change (admin only) before assuming a bug — some issues (e.g., NTV amounts not populating) stem from newly automated workflows that replaced manual steps. Admins can share updated onboarding materials or a walkthrough video.
• Escalate to Yardi support (admin only) for persistent errors such as duplicate rows in screening setup, prospect status not converting after payment, roommate rider generation failures, or countersign prompts missing after a resident signs. These are typically backend data issues Yardi must fix directly.

If none of these solve it, file a ticket and include: the exact error message text, the document or workflow type (e.g., roommate rider, NTV, screening report), which resident role is affected (applicant, guarantor, staying vs. leaving roommate), and any troubleshooting steps already attempted with Yardi Chat.