Housing Society Complaint Management: Tickets, SLAs and Escalation

Complaint management in a housing society

Every society has a complaint process. In most it is: tell a committee member when you see them, or put it in the WhatsApp group and hope.

That process has a specific failure mode. A complaint in a group chat generates agreement — six neighbours saying "yes, ours too" — and no owner, no date, and no resolution. Three weeks later the resident raises it again, more sharply, and the committee genuinely does not remember it. Nobody behaved badly. The system had no memory.

A ticketing process fixes exactly one thing: every complaint gets an owner and a record. That is enough to change the character of the relationship between residents and the committee.

What a complaint actually needs

Four things, and a WhatsApp message supplies none of them reliably:

1. A unique reference, so both sides are talking about the same thing
2. An owner — a named person or role, not "the committee"
3. A state — open, assigned, in progress, waiting on the resident, resolved, closed
4. A record of what was done, by whom, and when

The third one carries more weight than it looks. "Waiting on the resident" is the state that prevents most disputes: it makes visible that the society is not the blocker, which is a fact that otherwise gets lost entirely.

Categories worth having

Keep the list short — long category lists cause misfiling, which defeats reporting. Eight to ten is usually right for a residential society:

Lift entrapment is not a ticket. Anything involving a person trapped, fire, a medical event or a security threat goes to the emergency path, not the helpdesk queue. Say so explicitly on the raise screen, or someone will eventually file a trapped-in-lift ticket and wait.

Response targets that survive contact with reality

Publish targets, but set them where a volunteer committee can actually meet them. A target the society misses every time is worse than no target, because it teaches residents the published process is fiction.

A workable structure separates acknowledgement from resolution:

Acknowledgement is the promise that matters most. Residents tolerate a slow fix far better than silence — most escalation is caused by not knowing whether anyone has seen the complaint.

Be honest about dependencies. A lift spare that takes eleven days to arrive is not a committee failure, but it must be visible on the ticket, or it reads as neglect.

Escalation

An escalation path exists so a resident does not have to know which committee member to corner.

1. Assigned owner — usually the facility manager or the relevant staff lead
2. Portfolio committee member — the member holding that area
3. Secretary
4. Managing committee, as an agenda item at the next meeting
5. General body, for systemic or budgetary matters

Escalate on time elapsed, automatically, not on how loudly the resident complains. That single design decision removes the advantage currently enjoyed by the most persistent residents and is the main fairness gain from ticketing.

Where a complaint is against a committee member, it must be able to skip that member entirely. A process that routes a complaint about the secretary to the secretary is not a process.

What to review monthly

Four numbers, at the committee meeting:

• Open tickets by age. Anything over 30 days needs a reason or a decision.
• Volume by category. Repeated complaints in one category are an asset problem, not a service problem — twelve seepage tickets in one wing is a waterproofing decision, not twelve repairs.
• Median time to acknowledge and to resolve, against the published targets.
• Reopened tickets. A high reopen rate means things are being closed rather than fixed.

Present the category breakdown at the AGM. It converts "the committee does nothing" into a discussion about where the money should go, which is a far more productive argument.

Making residents use it

Adoption is the hard part, because the WhatsApp group is right there and costs no effort.

• Do not answer maintenance complaints in the group. Reply once, politely, with the link to raise a ticket. This is uncomfortable for two weeks and then it works.
• Close the loop visibly. A resident who gets a resolution notification tells three neighbours.
• Let staff raise tickets too — the guard who notices a broken light should not need a resident to report it.
• Allow photos. A picture of the seepage removes an entire round of clarification.
• Keep raising a ticket to under thirty seconds. Category, description, photo, submit. Every extra required field costs you reports.
• Do not require login for the guard's tablet in the cabin — friction there means nothing gets logged.

How this works on Plinth

Tickets are raised by residents or staff against a category, with photos, and carry an explicit state through to resolution — including a waiting-on-resident state, so a stalled ticket shows why.

Ownership sits with a named assignee rather than the committee generally, escalation runs on elapsed time against the society's configured targets, and complaints involving a committee member can route past them. Because the helpdesk shares the society's flat roster, a ticket is tied to a flat and a member without re-keying anything.

The committee gets ageing and category breakdowns for the monthly review and the AGM, and every state change is written to the society's append-only audit log — so "this was reported in March and nothing happened" is a question with an answer.

Frequently asked questions

How is a helpdesk better than a WhatsApp group for complaints? A group produces agreement; a ticket produces an owner, a state and a record. The group is fine for conversation and hopeless as a work queue.

What response times should a housing society commit to? Whatever the committee can actually meet — commonly same-day for critical issues, a few days for high, a week for medium. Acknowledge fast even when the fix is slow.

Who should own tickets in a self-managed society? Assign by portfolio to committee members, with the facility manager or caretaker as first-line owner. Avoid assigning everything to the secretary.

Should residents see other residents' complaints? Common area issues, usefully yes — it prevents duplicates and shows work happening. Complaints concerning a specific flat or a person should stay private.

What about complaints against the committee itself? The path must bypass the person concerned and reach the full committee or general body. Build that in before you need it.

Can staff raise tickets? They should. Guards and housekeeping see faults first, and a system only residents can use loses most of its early warning.

Step-by-step guides

• Admin: Set Up the Helpdesk
• Staff: My Helpdesk Tasks
• Admin: Triage Tickets on the Helpdesk Kanban Board
• Admin: Staff, Vendors & Vendor Escalation
• Helpdesk Troubleshooting
• Resident: Raise and Track a Ticket

Related: common housing society problems and fixes · monsoon checklist for committees · asset maintenance schedules