Feature
Maintenance ticket automation, from report to invoice
A maintenance ticket touches a tenant, a vendor, an owner and sometimes an asset's full repair history. Meridian automates the handoffs between all four so a coordinator manages exceptions, not every single step.
The problem
Manually triaging, assigning and following up on every maintenance ticket doesn't scale past a handful of properties.
Why it matters
Slow or inconsistent maintenance response is one of the most common reasons tenants don't renew — and untracked recurring issues quietly become bigger repairs.
How Meridian helps
- AI categorisation, priority assignment and duplicate detection on ticket creation
- Warranty checks before a vendor is dispatched for something still under coverage
- Owner approval triggered automatically above a configured cost threshold
- Before/after photo verification and tenant sign-off before a ticket closes
- Vendor score and asset maintenance history updated automatically on completion
Workflow example
- 1Tenant reports issue
- 2AI categorises and checks for duplicates and warranty coverage
- 3Vendor recommended and scheduled, SLA timer starts
- 4Owner approval triggered if the cost exceeds their threshold
- 5Vendor updates with photos, tenant signs off, invoice generated, asset history and vendor score updated
FAQ
How does duplicate detection work?
New tickets are checked against recent open tickets on the same unit/asset before a second vendor gets dispatched for the same fault.
What triggers owner approval?
A configurable cost threshold per owner or property — jobs above it pause for approval before a vendor is scheduled.