Weekly Testing

Most Elise AI weekly testing tickets resolve when the knowledge base is updated to reflect current policies or when Elise's existing behavior is clarified as working as intended.

• Check whether the behavior is actually a bug before requesting a change — some responses (e.g., an asterisk indicating a feature applies only to select units) are intentional design choices, not errors.
• Document specific units or exceptions if a feature or amenity does not apply universally. Compile a list of which units qualify and submit it so the admin can load unit-level data into Elise. (admin only to load)
• Test lease policy responses by calling the AI number and posing as a resident. Note exactly which questions Elise answered correctly and which it could not answer, so the knowledge base gaps are clearly scoped.
• Submit missing policy details to the admin — such as notice-to-vacate periods or updated lease terms — so Elise can be updated promptly. (admin only to update)
• Configure complex or variable fee questions as a handoff rather than expecting Elise to state a specific amount. When fee amounts vary by resident or are subject to change, routing the caller to the office team is the safer resolution path. (admin only to configure)

If none of these solve it, file a ticket and include: the exact question asked during testing, Elise's verbatim response, the correct answer Elise should have given, and whether the issue is a missing response, an inaccurate response, or an unwanted response. This detail speeds up knowledge base updates significantly.