> ## 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. # October 5, 2026 The following are the Latchel updates for the week of October 5, 2026. ### **New Features** 1. **Autopilot AI Is Live** Autopilot AI — our upgraded Autopilot product for customers who want the strongest AI in maintenance — launched this week. It includes: * Outbound voice AI * (Beta) AI support across every resident and vendor message * (Coming soon) Warranty management * (Coming soon) Smart Estimates — better numbers, faster * (Coming soon) Preventative maintenance suggestions > [card] [Not on Autopilot yet?](https://latchel.com/latchel-autopilot-ai-product-launch/) > > See what's included. 2. **Automated Vendor Status Calls Are Now Turning On** Following up with vendors is one of the most repetitive parts of running maintenance. If you're already an **Autopilot** customer, we're turning on automatic daily outbound calls to your vendors. > [!WARNING] > > **What's happening:** > > * Every business day, Latchel calls each vendor to get status on their open work orders. > * Latchel writes the result back to every work order it discussed. If it deliberately skipped a job, it leaves a note explaining why. > [!TIP] > > **What this means for you:** > > * Status chasing comes off your team's to-do list. You only get pulled in when something needs a human decision. > * **You don't need to do anything.** If you'd rather not have this turned on, reach out to [success@latchel.com](mailto:success@latchel.com). 3. **AI Messaging Beta!** SMS and in-app messages from residents and service providers are about to get smarter. Starting next week, we're rolling out **AI Messaging** — our next step in automating the back-and-forth that eats up your team's day. **Here's what changes:** * Residents and vendors message you; Latchel's AI reads and responds to routine ones ("I scheduled this for tomorrow." ✓) * Messages outside AI's scope get routed where they belong — to you if it's a PM-managed work order, to Latchel if we manage it * No more manual tagging — conversations auto-tag to work orders and close themselves when you reply * You stay in control: rate AI responses to help us improve, and customize when you want notifications We're currently in a 2-week beta with a limited group of customers before rolling out to everyone. > [!TIP] > > Want to join the beta? **Reply to this email** and we'll get you set up. 4. **Recurring Work Orders (V1)** You can now create and manage recurring work orders yourself in Latchel. Set it once, and the work order shows up on your cadence. **Here's what you can do:** * Pick a frequency, start date and (optional) end date * Assign a service provider if you want the same vendor on every occurrence * Choose whether Latchel should coordinate with the resident and collect their scheduling info * Pause and resume a recurring work order anytime * Run recurring inspections in an external tool? Create the recurring work order in Latchel and add a link to your inspection tool in the description **Who it's for (today):** This is an early version, built for one recurring work order on a cadence for a single unit or building. It's a good fit for common areas and other recurring needs in larger buildings, or for single-family homes with unique recurring work. **Who it's not for yet:** You need the same recurring task across many units (ex: gutter cleanings at 100 properties every six months). V2 is coming soon with bulk recurring work orders, so you can set it up once, or use Autopilot AI to suggest preventative maintenance, and apply it across many units. Give it a try under the **Maintenance** tab, and if it's not the right fit yet, stay tuned. We're moving fast. > [card] [How to Submit and Manage Recurring Work Orders](https://help.latchel.com/s/topic/0TO5e000000h9wqGAA/how-to-submit-and-manage-recurring-work-orders.md) > > Set up, pause and manage work orders that repeat on a schedule. ### **Resolved Bugs** **Rent Manager Work Orders Syncing Again** > [!WARNING] > > **What was happening:** > > A timing bug was preventing work orders from reaching the PMS when a vendor was assigned right after creation. > [!TIP] > > **What's fixed:** > > The fix is live, and we've confirmed work orders are syncing properly now. ### **What Should Latchel Build Next? You Decide.** We're locking our **2027 priorities** soon, and this is your chance to influence what we build next. It takes less than **60 seconds** — and every response goes straight to the product and leadership teams. > [card] [Submit your feedback here!](https://forms.gle/AbUoieefga3azLmH7) Your input directly shapes which features ship, improve, or get deprioritized — this is where ideas turn into action. ### **Interested in learning more about Latchel's products? Book a meeting with us.** > [card] [Get a Demo](https://latchel.com/demo-request-releases/)