Pain point
One fault, two tickets, two vendor visits
The same underlying issue often gets reported more than once — a second tenant in the same unit, a follow-up call treated as new, a recurring fault nobody connected to the last visit. Each one dispatched separately wastes a vendor trip.
The problem
Without duplicate detection, a coordinator has to remember or manually search recent tickets to catch that a new report matches one already in progress.
Why it matters
A vendor dispatched twice for one fault costs twice, and a tenant who reports the same issue a second time and gets a second 'we'll look into it' loses confidence fast.
How Meridian helps
- New tickets checked against recent open tickets on the same unit or asset automatically at intake
- Recurring-issue detection flags a fault that keeps coming back, not just an exact duplicate
- Coordinators see the match before dispatch, not after a second vendor is already on-site
FAQ
How does duplicate detection tell issues apart?
New tickets are checked against recent open tickets on the same unit or asset, matching on category and description before a second dispatch happens.