How to Set Up Complaint SLAs for Your Housing Society

Why SLAs matter

Without a service-level agreement (SLA), every complaint is a debate: "How long should this take?" "Why isn't it done yet?" SLAs make expectations objective, reduce committee-vs-resident friction, and create accountability for staff and vendors.

Recommended SLAs by category

These are battle-tested benchmarks from 1000+ Indian societies. Adjust to your context.

| Category | Critical | High | Medium | Low | |----------|----------|------|--------|-----| | Security incident | 30 min | 1 hr | 4 hr | — | | Lift breakdown | 2 hr | 4 hr | 8 hr | 24 hr | | Water supply | 4 hr | 8 hr | 24 hr | 48 hr | | Power outage (common area) | 1 hr | 4 hr | 12 hr | 24 hr | | Plumbing leak | 4 hr | 12 hr | 24 hr | 72 hr | | Electrical (member flat) | — | 12 hr | 24 hr | 48 hr | | Civil (cracks, paint) | — | 24 hr | 72 hr | 168 hr | | Housekeeping miss | — | 4 hr | 8 hr | 24 hr | | Garden / landscaping | — | — | 48 hr | 168 hr | | Noise complaint | 1 hr | 4 hr | 12 hr | — | | Pest control | — | 24 hr | 48 hr | 168 hr |

How to define priority

Don't let residents self-assign critical priority — they'll all do it. Use rules:

Critical: Affects life/safety or large groups. Examples: lift stuck with people inside, fire/smoke detection, medical emergency, water completely out.

High: Affects > 1 family or major service. Examples: lift down (no one stuck), power out for full block, sewage backup, water out for 1 wing.

Medium: Affects 1 family or non-essential service. Examples: low water pressure in 1 flat, common-area light not working, lift slow.

Civil + cosmetic: Almost always Low priority unless safety-related (e.g. cracked wall threatening collapse).

What to do when SLA breaches

1. Auto-escalate: Past SLA = automatic escalation to society admin / president
2. Notify resident: Send WhatsApp/SMS to the complainant ("Sorry, we've missed our SLA. Escalating to admin now.")
3. Status note: Document why it's late (vendor unavailable, parts ordering delay, etc.) — don't pretend it isn't late
4. AGM review: Track SLA breach rate monthly; review vendor performance based on it

Vendor accountability

Tie vendor contracts to SLA performance:

• 95%+ on-time = full payment
• 85-95% = 5% deduction
• < 85% = 10% deduction + warning
• < 75% for 2 months = contract review

Track in HiSociety: every complaint assigned to a vendor logs the assignment-to-resolution time. Monthly vendor scorecard auto-generated.

Closing the loop

A complaint isn't done when the work is done. It's done when the resident says it's done.

After fixing:

1. Mark complaint as "Resolved" (not Closed)
2. Notify resident: "Issue resolved. Please verify and rate."
3. Resident rates 1-5 stars + optional feedback
4. If 1-3 stars or no response in 48hr → re-open
5. If 4-5 stars or "verified" → status moves to Closed

This loop is the difference between residents trusting your committee and residents revolting at the AGM.

Real example

A 250-flat society in Pune ran 184 complaints last quarter:

• 94% closed within SLA
• Avg resolution time: 6.2 hours
• Resident satisfaction: 4.6/5

Six months earlier (before HiSociety SLA system):

• 43% closed within SLA (most complaints had no defined SLA)
• Avg resolution time: 18 hours
• Resident satisfaction: 2.8/5
• Committee getting daily WhatsApp complaints from frustrated residents

How HiSociety does this

• Each category has a default SLA + ability to customize per society
• Visual progress timeline on every complaint (Raised → Assigned → In Progress → Resolved → Closed)
• SLA breach indicators in red
• Auto-escalation to admin
• Resident rating after resolution
• Vendor scorecards updated continuously

Conclusion

SLAs sound bureaucratic but they're the antidote to the "WhatsApp complaint chaos" most societies suffer. Set them, measure them, enforce them — and your society becomes a place residents actually like living in.

Read next