Other

Most Elise "Other" tickets resolve when the right configuration change or bug report is routed to the admin team quickly — many are completed same day.

• Check if the issue is a known Elise bug first. Inspection form problems (e.g., a photo being incorrectly required when answering "No" on yes/no questions) have been fixed platform-wide by Elise after a single report. Try reloading the app or logging out and back in to pick up any recent fixes before submitting a ticket.
• Use Elise's built-in reports for data Yardi can't display. Technician attribution for completed work orders cannot be written to Yardi due to a missing field — this is a platform limitation. Instead, pull technician completion data directly from Elise's reporting dashboard.
• Verify the actual sender before escalating an unexpected email. If a resident or applicant receives a surprising auto-email, confirm whether it matches Elise's email format. Staff-sent emails using internal templates can look automated but are not from Elise.
• Request a daily report opt-out (admin only). If unwanted Elise daily reports start arriving after a new login is created, an admin can submit an opt-out request to Elise to have those reports removed for specific users.
• Request Knowledge Central updates (admin only). Adding vendor information (e.g., laundry service contacts or URLs) or emergency transfer destinations to Elise Knowledge Central requires an admin to make the change directly in Elise settings.
• Request feature/configuration changes through a ticket (admin only). Enabling or disabling Elise features (such as delinquency) or adding new transfer categories requires an admin to action the change on the back end.

If none of these solve it, file a ticket and include: the specific Elise feature or app screen affected, the exact behavior observed vs. expected, whether the issue affects all users or specific logins, and — for inspection bugs — the inspection type and the question where the block occurs.