WhatsApp for Property Management Teams
A tenant's geyser stops working at 9pm. They don't open a portal or file a form — they message the building WhatsApp. So does the tenant whose lift is stuck and the owner chasing last month's maintenance receipt. By morning, three requests sit unread in one manager's personal chat, two are buried in a society group, and nobody can say which got handled. That's WhatsApp for property management in its raw form: the right channel, run the wrong way.
The channel isn't the problem. Tenants and owners already live on WhatsApp and expect a reply there. The problem is that a maintenance request on WhatsApp has no ticket, no owner, no deadline and no paper trail — so things fall through, and "did anyone fix the parking complaint?" becomes a recurring question.
This guide is for property managers, facility teams and managing agents who run buildings on WhatsApp. It shows how to turn that messy chat into tracked tickets with SLAs, route requests across multiple properties without chaos, and keep a record that survives staff turnover. It's a close cousin of our WhatsApp CRM for real estate guide — same channel, but the job here is service, not sales.
Why WhatsApp breaks for property teams
The free WhatsApp Business app is built for one person on one phone. The day you manage more than one building — or more than one staff member touches the inbox — it stops holding up:
- Requests have no status. A "lift is down" message and a "fixed it" reply look identical to a pending one. Nothing tells you what's open, in progress or closed.
- No one owns the request. If a tenant messaged the building number, everyone assumes someone else picked it up. Often nobody did.
- No deadline. Urgent and trivial requests get the same treatment — none — because there's no clock on anything.
- Society groups swallow complaints. A genuine maintenance issue posted in a 100-member society group scrolls past in minutes, untagged and unowned.
- History walks out the door. When a site manager quits, every tenant chat leaves on their phone.
The common upgrade — the WhatsApp Business API (WATI, AiSensy, Interakt and similar) — is a poor fit here. It's built for templated broadcasts and per-message billing, not the live back-and-forth of maintenance. And it structurally cannot access WhatsApp groups — the exact place society and building complaints appear. You can read why in our WhatsApp groups for business guide.
Turn tenant requests into tickets, not lost messages
The single biggest shift for a property team is treating each tenant request as a ticket with a status — not a message that may or may not get answered. A WhatsApp support desk does this on top of your existing number. When a tenant messages, the chat becomes a ticket you move through states your team agrees on:
- New — just arrived, unassigned.
- Assigned — owned by a specific person (the plumber's coordinator, the accounts clerk).
- In progress — work or follow-up underway.
- Resolved / Closed — done, with the history attached.
Because every request has a status, "what's still open across the estate?" is a view, not a guess. The geyser, the lift and the receipt request each become a line item somebody is accountable for. This is the same ticketing model covered in our WhatsApp helpdesk and ticketing guide, applied to buildings.
Internal notes keep coordination off the tenant's screen
Most maintenance work involves a third party — a vendor, an electrician, the accounts team. With internal notes and @mentions on a ticket, your staff can coordinate ("@Ravi the plumber's booked for 11am, confirm with flat 402") without sending anything to the tenant. The tenant only sees the clean updates you choose to send. See internal notes on WhatsApp.
Set SLAs so nothing sits for days
A ticket without a deadline still drifts. SLAs (service-level agreements) put a clock on each request so urgent issues get pulled forward and routine ones don't get forgotten. The practical move is to tier your requests and attach a target response and resolution time to each. A simple property SLA grid:
| Request type | Example | Target first response | Target resolution |
|---|---|---|---|
| Emergency | Gas leak, no water, lift trapping | Minutes | Same day |
| Urgent | Geyser dead, AC failure, leak | Within an hour | 24–48 hours |
| Routine | Repaint, fitting, minor repair | Same day | A few business days |
| Admin | Receipt, NOC, document request | Same day | 2–3 business days |
With SLAs in your support desk, tickets nearing or breaching their target surface to the top, so a "my water's been off since morning" never quietly ages into "I've messaged three times" — the kind of escalation that ends up in the owners' association group. For how to define these, see setting SLAs for WhatsApp support.
The point of an SLA isn't to punish staff. It's to make the invisible visible: your team can see what's at risk before a tenant has to chase.
Route requests across multiple properties
Most property teams run a portfolio, not one building. The hard part isn't answering a request — it's getting it to the right person for the right property, fast. A shared WhatsApp workspace handles multi-property routing a few ways:
- One inbox, many sources. Whether each building has its own number or your tenants reach a central line, every chat lands in one shared inbox your whole team works — no juggling devices. See multi-number WhatsApp inbox.
- Tag and segment by property. Custom fields and tags mark each contact and ticket with its building, tower or unit, so a request is instantly filterable to "Tower B" or "Green Acres".
- Assign to the on-site owner. Route a request to the manager responsible for that property, so it's never "whose building is this again?". See assigning WhatsApp chats.
- Work the society groups too. Your building and society groups sit in the same inbox as DMs, so a complaint posted in a group can be assigned, noted and turned into a ticket like any other — something the official API simply can't reach. If resident groups are a big part of your day, our WhatsApp for community management guide goes deeper, and managing groups without chaos covers keeping them under control.
The result: a request for Flat 402, Tower B reaches the person who covers Tower B, carries its building context, and sits in a queue you can audit per property.
Keep an audit trail tenants and owners trust
Property management runs on accountability. Owners want proof a complaint was handled; tenants want a record of what was promised; you want defensibility when a dispute lands in the AGM.
When every request is a ticket in a workspace, you get a per-contact and per-ticket timeline that stays in the business — every message, status change and resolution, attached to the unit and the property. When a site manager leaves, that history doesn't leave with them. This is also where a real WhatsApp CRM earns its keep for owner and tenant relationships.
Where Tenashi fits
Tenashi is the WhatsApp workspace for teams, and property management is squarely the kind of operation it's built for. You link your existing WhatsApp number with a QR scan — no new SIM, no porting — and within minutes your whole team works one shared inbox that includes tenant DMs and society/building groups, with a real support desk underneath.
For a property team, that means tenant requests become tickets with SLAs, routed to the right person for the right building, with internal notes so vendor coordination never reaches the tenant. Custom fields tag each request by property and unit, tickets move through your states, and the full history stays in the business when staff change. Because it's your own number — not the API — you keep group access and pay a flat price from $18/mo instead of per-message fees or template approvals.
If you also send notices — maintenance schedules, dues reminders, AGM dates — those go out through ban-protected broadcasts: human-paced, warmed up, with duplicate and burst patterns paused before they ship, so the number that runs your estate stays safer (risk reduction, not a guarantee). On Growth and Scale plans, AI can draft replies, translate a tenant message, summarize a noisy society-group thread into action items, and OCR a photographed receipt.
There's a 3-day Growth trial, no card.
Start your free trial → · See every feature
FAQ
Can I use WhatsApp for property management requests?
Yes, and most tenants already prefer it. The gap is structure: raw WhatsApp has no tickets, owners or deadlines. A WhatsApp workspace like Tenashi adds a support desk on top of your existing number, so each tenant request becomes a tracked ticket with a status, an assignee and an SLA instead of an unread message.
How do I set SLAs for tenant maintenance requests on WhatsApp?
Tier your requests — emergency, urgent, routine, admin — and attach a target response and resolution time to each. In a support desk like Tenashi, tickets nearing or breaching their SLA surface to the top, so urgent issues get pulled forward and routine ones don't quietly age into a complaint.
How do I route WhatsApp requests across multiple properties?
Use one shared inbox with tags and custom fields for building, tower and unit, then assign each ticket to the manager who covers that property. Tenashi brings every number and group into a single inbox, so a request for one building reaches the right person carrying its full property context.
Can a property team work WhatsApp society groups together?
Yes, with a workspace. Tenashi puts your society and building groups in the same shared inbox as DMs, so a complaint posted in a group can be assigned, noted and turned into a ticket. The official WhatsApp Business API can't access groups at all, which is why API-only tools fall short for buildings.
Will sending tenant notices on WhatsApp get my number banned?
It can if you blast them without pacing. Tenashi sends broadcasts at a human pace, warms up numbers gradually, and pauses duplicate or burst patterns before they ship — which reduces the risk, though no tool can guarantee against WhatsApp's policies. Always send to tenants who expect to hear from you.
Do I need a new number to manage tenants in Tenashi?
No. Tenashi links your existing building or office WhatsApp number with a QR scan — no new SIM and no porting. Tenants and owners keep messaging the same number they already have, and your team goes live in minutes.
Stop losing tenant requests in the chat scroll. Start a free trial and turn every WhatsApp message into a tracked ticket — with SLAs and per-property routing built for how property teams run.