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.
- Messages have no owner. A complaint everyone can see is a complaint nobody is responsible for.
- Volume is invisible. Without a queue, a committee cannot tell a busy week from a systemic failure.
- The loudest resident wins. Attention follows escalation rather than age or severity.
- Nothing is measurable. You cannot improve a response time you have never once calculated.
Key capabilities
Capture, routing and deadlines do the work. Ratings and reports are what stop it degrading after three months.
Category-wise ticket capture
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 the routing and the SLA.
Tickets can also be raised by guards on patrol, by staff, and by the committee on a resident’s behalf, which matters for the members who will phone rather than use an app. A complaint made by phone should still become a ticket, and this is how.
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. What matters is that every ticket has exactly one owner at every moment, never a group.
SLAs with escalation matrix
Each category carries a response time and a resolution time. When either is breached the ticket escalates automatically — to the supervisor, then to the committee member holding that portfolio — without a 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.
Photo and video attachments
A photograph resolves most of the ambiguity in a complaint. 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 rather than making a diagnostic visit first.
Attachments on closure matter equally. A ticket closed with a photograph of the completed work is one a resident is far less likely to reopen, and it gives the committee evidence when a vendor invoices for it.
Resident ratings on closure
When a ticket closes the resident is asked whether it was actually resolved and to rate it. A low rating reopens the conversation rather than closing the loop on a job that was marked done but was not.
Ratings aggregate per vendor and per category, which is what turns a vague sense that the plumbing contractor is unreliable into a number to raise at contract renewal.
Turnaround-time reports
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.
How it works
Nothing here depends on somebody reviewing a queue every morning.
Who it helps
The helpdesk is usually the module residents judge the whole platform by, because it is the one where they can see whether anything actually changed.
SLAs societies typically set
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 |
Works with the rest of KeyMatrix
A ticket is attached to a unit or a location, which is what makes its history useful. Open a flat and you see every complaint ever raised from it; open a lift and you see every stoppage. That second view is the one that changes capital decisions — four stoppages in six weeks is an asset nearing the end of its life, not four unrelated inconveniences.
Tickets do not stay inside the helpdesk. A complaint that turns out to be a failing asset becomes a work order against that asset. One that needs an AMC vendor routes to the vendor holding the contract, and the vendor’s response times accumulate into the scorecard that gets read at renewal.
- Asset management. Repeat complaints against equipment become service history, not separate tickets.
- Work orders and PPM. A recurring fault converts into scheduled preventive work.
- Vendor management. AMC vendors receive tickets directly, and their SLA record builds their scorecard.
- Unit management. Every ticket hangs off a flat, so complaint history follows the unit through a sale.