Society complaint management system
A complaint becomes a ticket with an owner and a deadline. Escalations fire on their own when a deadline slips, and turnaround time becomes a number the committee can report rather than a feeling.
A society complaint management system turns resident complaints into tracked tickets: captured by category, auto-assigned to the right staff member or vendor, governed by an SLA with automatic escalation, and closed with a resident rating. Turnaround times are reported per category and per owner.
Complaints should have deadlines, not destinies
The default complaint system in most societies is a WhatsApp group. A resident reports a leaking tap at eleven at night, three people react to the message, somebody says they will look into it, and the message scrolls out of view by morning. Nothing was assigned, nothing had a deadline, and nobody can later say what happened.
What makes this worse than it looks is that it fails invisibly. There is no list of open complaints, so a committee cannot tell whether it has four outstanding issues or forty. The only signal is the tone of the group, which means the loudest complaint gets attention and the patient resident waits indefinitely.
A ticket fixes three things at once: it exists after the conversation scrolls away, it has exactly one owner, and it has a date by which something must happen. None of those requires a committee to work harder. They require the complaint to be a record rather than a message.
From report to rating: the life of one ticket
Every complaint passes through the same four moments. Each one is where the WhatsApp version quietly fails.
Category-wise ticket capture, with photos
A resident raises a ticket in three taps: category, flat or location, and a short description. Categories match how the property is actually maintained — plumbing, electrical, lift, housekeeping, security, common area, billing — because the category decides who gets it and how long they have.
A photograph or a short video resolves most of the ambiguity. Which tap, which corridor, how bad the seepage actually is: all of it is faster to show than to describe, and it lets a technician arrive with the right part instead of making a diagnostic visit first.
Guards on patrol, staff and the committee can raise tickets on a resident’s behalf. That matters for the members who will always phone rather than use an app — a complaint made by phone should still become a ticket.
Auto-assignment to the right staff or vendor
Each category has an owner: an in-house technician, the housekeeping supervisor, or the AMC vendor holding that contract. A lift complaint reaches the lift vendor directly, rather than reaching the secretary who then phones the vendor.
Assignment can vary by time and location — the night-shift owner differs from the day one, and a tower with its own supervisor routes there. The rule that matters is that every ticket has exactly one owner at every moment, never a group.
An SLA with an escalation matrix behind it
Each category carries a response time and a resolution time. When either is breached, the ticket escalates on its own — to the supervisor, then to the committee member holding that portfolio — without the resident having to complain a second time.
The escalation ladder is the part that changes outcomes. An SLA with no escalation is a target; an SLA that automatically involves someone more senior is a commitment. Set the ladder before go-live, because retrofitting it after residents have lost faith is much harder.
Closure the resident confirms
A ticket closes with a photograph of the finished work, and the resident is asked whether it was actually resolved. A low rating reopens the conversation instead of closing the loop on a job that was marked done but was not.
The closing photo also protects the committee. When a vendor invoices for a repair, the evidence that it happened is already attached to the ticket it came from.
SLAs societies typically set, by complaint category
These are the starting points most societies land on. The right numbers for your property depend on whether the trade is in-house or on an AMC.
| Category | Typical response SLA | Typical resolution SLA | Usual owner |
|---|---|---|---|
| Water supply failure | 30 minutes | 4 hours | In-house plumber |
| Lift stoppage | 15 minutes | 4 hours | Lift AMC vendor |
| Power or DG failure | 30 minutes | 6 hours | Electrical AMC vendor |
| Plumbing leak in common area | 2 hours | 24 hours | In-house plumber |
| Housekeeping | 4 hours | 24 hours | Housekeeping supervisor |
| Common area lighting | 8 hours | 48 hours | In-house electrician |
Turnaround-time reports, and the faults that keep coming back
Median and worst-case resolution time by category, by owner and by month, with SLA breach counts. That is the report a committee should read every month and present at the AGM, because it is the closest thing to an objective measure of whether the property is being maintained.
The distribution matters more than the average. A category with a two-hour median and a nine-day tail has a specific problem in a specific subset of jobs, and the average conceals exactly that.
Because every ticket hangs off a flat or a location, history accumulates where it is useful. Open a flat and you see every complaint ever raised from it; open a lift and you see every stoppage. Four stoppages in six weeks is an asset nearing the end of its life, not four unrelated inconveniences — and that is the point at which a complaint becomes a work order against the asset, and the AMC vendor’s response record becomes the number read out at contract renewal.