Module

Request Autopilot

Intake → assign → track → close work requests without spreadsheet chaos.

Who

Operators and service teams who still route work through email threads and spreadsheets — including property-maintenance crews via the first industry pack.

What

Request Autopilot is an industry-agnostic work-request module: capture requests, assign owners, track status through completion, and measure cycle time. Industry packs (starting with property-maintenance) add categories and vocabulary without forking the product.

Why

Teams still route work requests through email threads and spreadsheets. Requests get lost, assignees are unclear, cycle times stretch, and managers cannot see what is open versus done.

Outcomes

  • Single intake channel instead of scattered email and sheets
  • Clear ownership with assign → in-progress → done workflow
  • Measured cycle times and completion counts (estimates labeled separately)
  • Multi-tenant isolation so each org only sees its own requests
  • Industry packs layer domain language without apartment-only hard-coding

Demo walkthrough

  1. Create a work request from intake (title, category, priority, location).
  2. Assign it to a team member — status becomes assigned.
  3. Move through in_progress / waiting as work happens.
  4. Mark done — cycle time is recorded from create → complete.
  5. Review ROI metrics: completed count, average cycle time, open backlog.

Industry packs: Property Maintenance — domain vocabulary without forking the core product.