> ## Documentation Index
> Fetch the complete documentation index at: https://help.latchel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# June 1, 2026

The following are the Latchel updates for the week of June 1, 2026.

### **New Features**

1. **Intake Settings Rule Analyzer — Write Clearer Rules from the Start**

We’ve introduced the Intake Settings Rule Analyzer to help you write rules that your AI intake system can interpret accurately every time. When you add a new rule, the system automatically highlights potential for misinterpretation and suggests clearer wording — then lets you accept the suggestion, request changes, or have a conversation about exactly how you want the rule framed.

<Frame>
  <img src="https://mintcdn.com/latchel-81/LVnu9qJsX3C32qwD/images/Latchel-05-29-2026_12_49_PM.png?fit=max&auto=format&n=LVnu9qJsX3C32qwD&q=85&s=07f0ebb4f4020b73baf92dc1319b9f87" alt="Latchel 05 29 2026 12 49 PM" width="1117" height="763" data-path="images/Latchel-05-29-2026_12_49_PM.png" />
</Frame>

This matters because ambiguous phrasing can be read multiple ways by the system that processes intake sessions. The Rule Analyzer catches these edge cases and offers plain-language alternatives before you save.

<Check>
  **How it works:**

  You’ll be able to test your rules by simulating a conversation as if you are the resident. Ask questions, provide answers, and see exactly how your rules respond to real-world scenarios — no more guessing whether your intake logic works the way you intended.

  **See the full guide here:**

  <Card title="Intake Settings Rule Analyzer" color="#ff9b8a" icon="head-side-brain" horizontal>
    Learn how the Rule Analyzer helps you write clearer, more accurate intake rules—and how to simulate a resident conversation to test them.
  </Card>
</Check>

2. **Latchel MCP for AI Assistants**

The **Latchel MCP connector** lets you talk to your Latchel account directly from AI assistants like Claude and ChatGPT. Ask in plain English, and the assistant can pull and act on your real work-order data — **no copy-pasting, no switching tabs.**

Everything is scoped to your PM company and gated behind your own Latchel login, so the assistant only ever sees what you're allowed to see.

<Check>
  **What you can do:**

  * **Work orders** — list them, get full details (including open tasks), review activity history, and create new ones.
  * **Tasks** — list, view details, create, resolve, and reschedule (defer) tasks on a work order.
  * **Lookups** — search your properties, see the residents on a property, and browse your company's users and user groups.

  A typical request just works conversationally, e.g., **"Open a work order for a leaking faucet at 123 Main St for the current tenant"** or **"What's still open on work order #4821?"**
</Check>

<Icon icon="camera-movie" iconType="duotone" color="#ff9b8a" size="25" /> **Watch this video:**

<iframe src="https://www.youtube.com/embed/T8g6FqcLxfQ" title="YouTube video player" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

**Learn how to get started here:**

<Card title="Latchel MCP for AI Assistants" color="#ff9b8a" icon="microchip-ai" iconType="duotone" href="/s/topic/0TO5e000000h9wqGAA/latchel-mcp-ai-assistants">
  Learn how to connect Latchel to AI tools giving you instant access to help guides.
</Card>

### **Resolved Bug**

**Intake Asked Resident for Temperatures**

<Warning>
  **What was happening:**

  In some intake sessions for HVAC issues, residents were asked to self-report the temperature.
</Warning>

<Check>
  **What's fixed:**

  Intake will no longer prompt residents for temperature readings as Latchel’s system references the next 72 hours of weather data by default.
</Check>

### **Key Ops Process Changes**

**Ask Residents Before Escalating After-Hours**

We updated our emergency work order SOP to close a gap where troubleshooters were escalating to pre-dispatch contacts after-hours without first checking whether the resident was willing to wait until the next business day. The result was unnecessary calls to property managers when residents would have been fine with deferring service dispatch.

<Check>
  **The Key Change:**

  After completing troubleshooting, if the issue doesn’t cause property damage or pose an immediate safety risk, troubleshooters should now ask: “Based on what you’ve described, would you be comfortable waiting until \[tomorrow morning / next available time] for a service provider?”
</Check>

<Note>
  **What this means for you:**

  Fewer unnecessary after-hours calls when residents are comfortable deferring service.
</Note>

### **Industry News**

🏆 We're honored to be recognized by [BestAIFor.com](http://BestAIFor.com)'s 2026 AI Property Management Report as the leading specialist for maintenance triage and coordination.

**Check out the full report here:**

<Card title="AI Property Management Report 2026: What We Found Across 15 Tools" color="#ff9b8a" icon="party-horn" iconType="duotone" horizontal href="https://www.bestaifor.com/blog/ai-property-management-report-2026" />

### **Influence Our 2026 Roadmap**

We’re locking our **2026 priorities** soon, and this is your chance to directly **influence what we build next**. It takes less than **60 seconds** — and every response is reviewed by our product and leadership teams!

<Columns cols={2}>
  <Card title="Submit your feedback here!" color="#ff9b8a" icon="message-pen" iconType="duotone" horizontal href="https://forms.gle/AbUoieefga3azLmH7" />
</Columns>

Your input directly impacts which features get built, improved, or deprioritized — this is where that thought turns into action!

### **Interested in learning more about Latchel's products? Book a meeting with us.**

<Columns cols={2}>
  <Column>
    <Card title="Get a Demo" color="#ff9b8a" icon="comments-question-check" iconType="duotone" horizontal href="https://latchel.com/demo-request-releases/" />
  </Column>
</Columns>
