Case Study · 03 / 10 Property Management Save as PDF ↓
Customer support agent · 5-week build

The 2AM support queue.

How a Pune property management firm killed their inbox — without firing or hiring.

ClientHabitat Collective LocationPune, India PublishedMay 2026
Industry
Property mgmt · Rentals
Scale
4,200 units · 1,100 landlords
Team
62 employees · ₹38 Cr ARR
Engagement
5 weeks to live traffic
Outcomes · 90 days post-launch
47m → 31s
Avg first response time, from 47 minutes to 31 seconds
67%
Of queries now handled autonomously by the agent
4.4/5
Tenant CSAT, up from 3.6 / 5
§ 01 · The company

4,200 rental units. 1,100 NRI landlords. One inbox.

The company

Habitat Collective is a rental property management firm in Pune managing 4,200 residential units across Kharadi, Wakad, Baner, and Hinjewadi for 1,100+ NRI and HNI landlords. Founded in 2018, 62 employees, ~₹38 Cr ARR — mostly a 7% management fee on rent collected.

Their protagonist is Aniket Deshmukh, Head of Tenant Operations, who runs a team of 14 support associates and hasn't had a Sunday off since Q3 2024.

§ 02 · The problem

380 messages a day. 64% of them, the same eleven questions.

Inbound load

Tenant requests landed across four channels: WhatsApp (61%), in-app tickets (22%), email (11%), and direct calls (6%). Volume averaged 380 messages/day, spiking to 540 on weekends and the 1st–5th of every month. The team had a 4-hour internal SLA. They were hitting 71%.

Breaking pointMar 14, 2025

A burst geyser in a 3BHK in Kharadi sat in the WhatsApp queue for 19 hours because the associate who'd seen it first went on leave and never reassigned it. The tenant escalated to the landlord in Dubai, the landlord threatened to switch managers, and Habitat lost the contract.

₹4.2L annual contract walked

Aniket's audit found that 64% of all queries fell into 11 repeating categories: rent receipts, society NOC, water tanker bookings, maintenance status, lease renewal, brokerage clarifications, move-out checklists, and four others. The team was burning 9.5 person-hours a day on questions they had answered a thousand times before. Hiring two more associates would cost ₹14L/year and not fix the routing problem.

§ 03 · The solution

A tenant-facing AI on WhatsApp + in-app, with real system access.

Architecture

Vynara built a tenant-facing AI agent on WhatsApp Business API and the in-app chat, with a single shared context layer pulling from Habitat's existing PMS (custom Laravel app), Razorpay rent-collection records, and the society management portal. The agent handles 11 query categories end-to-end — including generating signed rent receipt PDFs and booking water tankers via the existing vendor API.

Anything outside its remit, or anything emotional ("this is the third time the lift is broken"), gets escalated to a human with a one-line summary, full conversation history, and a suggested first response already drafted. Build to live tenant traffic: 5 weeks. Maintenance dispatch, legal queries, and any landlord-facing conversation stayed 100% human by design.

Always escalates to human if
outside 11 categories OR emotional sentiment OR landlord-facing
§ 04 · How it works

11 minutes to 38 seconds.

Before · Manual triage 11 min / msg
  1. Tenant message lands in shared WhatsApp inbox
  2. Associate reads, classifies, opens PMS
  3. Looks up unit, lease, ledger
  4. Drafts reply, sends
  5. Maybe logs a ticket
  6. Escalates if stuck1–3 humans involved · 6 touch points
After · Agent + escalation 38s · 2.4m esc.
  1. Agent reads, classifies, pulls unit + lease + ledger in one call
  2. If in 11 known categories → resolves and logs67% autonomous
  3. If outside → routes to right associate with summary + draft reply
  4. Human approves or edits in 1 clickavg 2.4 min
§ 05 · The numbers

Six metrics. 90 days after live traffic.

Queries handled by AI (autonomous)+67 pts
Before0%
After67%
Avg first response time−98.9%
Before47 min
After31 sec
4-hr SLA hit rate+25 pts
Before71%
After96%
Person-hours / day on repeats−81%
Before9.5 hrs
After1.8 hrs
Weekend on-call associates−75%
Before4
After1
Tenant CSAT (monthly survey)+0.8
Before3.6 / 5
After4.4 / 5

Annualised: ₹11.7L in avoided hires · 1,600+ hours redeployed to landlord retention calls · 2 churned contracts won back in Q2.

§ 06 · The timeline

Five weeks. Then scaled.

Phase
W1
W2
W3
W4
W5
Week 1Audit · tagged 6,200 historical convos · locked 11 categories
AUDIT
Week 2PMS · Razorpay · society portal · vendor APIs
INTEGRATE
Week 3Agent build + escalation routing · dogfood 3 associates
BUILD
Week 4Shadow mode · 100% traffic · 14 edge cases caught
SHADOW
Week 5Go-live · 30% autonomous · scaled to 67% over 6 weeks
LIVE
§ 07 · What they said

The metric: checking WhatsApp at 2 AM.

"

I stopped checking WhatsApp at 2 AM. That's the metric. My wife noticed before my dashboard did.

AD
Aniket Deshmukh
Head of Tenant Ops · Habitat Collective
"

The escalation summary is the part I didn't know I needed. I open a ticket and I already know what to say.

SK
Sneha Kulkarni
Senior Tenant Associate · Habitat
§ 08 · The takeaway

Not a volume problem. A repetition one.

If 60–70% of your inbox is 10–15 question patterns answered against data you already have, an agent with real system access closes the loop.

The rest is good escalation. Whether you manage tenants, dealers, or SaaS tickets, the shape is the same.

One-liner Your support team isn't slow. They're answering the same 11 questions 380 times a day. We fixed that in 5 weeks.
Show us your inbox →