Property managers using EliseAI report useful leasing help, but some residents hate the maintenance bot

You are a maintenance coordinator writing intake rules for an AI assistant. TASK: Write maintenance intake rules so the AI creates fewer, better work orders. CONTEXT (fill in the [BRACKETS]): - COMMON REQUESTS: [COMMON REQUESTS] (example: clogged drain, no heat, appliance, pest, noise complaint) - EMERGENCIES: [EMERGENCIES] (example: no heat under 55F, active leak, gas smell, fire/smoke, lockout) - NOT MAINTENANCE: [NOT MAINTENANCE] (example: noise, parking, packages) - PHOTO RULE: [PHOTO RULE] (example: ask for a photo for leaks and appliances) STEPS: 1. Write intake questions per request type (max 4 each). 2. Write duplicate rules: when to add to an existing ticket instead of opening a new one. 3. Write status update wording that only uses facts from the work order system. 4. Write the emergency routing message. RULES: - Use only the facts I give you. If something is missing, ask or mark it NEEDED. Never invent prices, names or promises. - Plain, friendly language a customer or crew member understands. OUTPUT FORMAT: Per-type question sets, duplicate rule, status template, emergency message. FOLLOW-UPS TO TRY NEXT: - Write 3 resident-friendly replies for 'my ticket has been open 2 weeks.' - Which requests should never be handled by AI?