Tenant support bot for property managers and housing societies

Updated 2026-09-19 · 5 min read · By the Convo360 team

The problem with WhatsApp groups for society management

Most housing societies already run on WhatsApp, but usually through large, noisy groups where a genuine complaint gets buried under festival wishes and unrelated chatter within minutes. Residents lose track of whether their complaint was even seen, and the secretary or facility manager has no structured record of what's pending.

A dedicated bot number for the society, separate from the social group, gives every request a trackable path. It also helps to think of residents as three separate segments, owners, tenants and household staff or visitors, since each needs slightly different handling: an owner cares about dues and long-term maintenance, a tenant mostly wants complaints resolved fast, and a visitor or delivery only needs a gate notification, not access to the full society directory.

On Convo360, a dedicated number also solves a quieter problem: accountability. When a complaint sits inside a 200-member group, no single person feels responsible for it. A one-to-one bot conversation, logged against a flat number, makes it clear whose turn it is to act.

Complaint categories that route themselves

Replace free-text complaints with a List Menu: Plumbing, Electrical, Security, Common Area, Parking, Other. Each category routes to a different handler or maintenance vendor and is logged with a category tag in the CRM pipeline, so nothing depends on someone manually reading and categorising every incoming message.

Ask two or three quick follow-up questions per category, flat number, description, urgent or routine, before confirming the complaint is logged, so the maintenance team has what they need without a back-and-forth. A typical confirmation reads: 'Thanks, logged as Plumbing for B-302, marked urgent. Our maintenance team will be notified.'

A simple routing table keeps expectations clear for residents and staff alike:

Maintenance dues reminders on a fixed monthly calendar

Store each flat's maintenance due date and amount as custom fields, updated monthly or per your billing cycle. A predictable calendar, run the same way every month, is what actually reduces the secretary's manual phone follow-ups:

1. T-5 days: a Utility template reminder with the amount due and a Razorpay payment link: 'Maintenance for Flat B-302, ₹3,500, due 5th. Pay here: [link].'
2. Due date: a same-day nudge only if unpaid, keeping the tone plain rather than urgent.
3. T+3 days overdue: a second reminder worded more firmly but politely, mentioning any late-fee policy the society has published.
4. T+10 days overdue: escalate to the committee list rather than repeating the same message to the resident a third time.

Log payment confirmation automatically once the payment link is used, updating the flat's record so the next cycle's reminder logic knows this flat is clear.

Notice broadcasts, segmented by audience

Use broadcast campaigns for society-wide notices: a scheduled water cut, an AGM date, a festival celebration, a security advisory. These go out as a template message to the relevant contact group, reaching everyone reliably instead of depending on people scrolling past a busy chat.

Not every notice needs to reach everyone. Tag contacts into groups such as Owners, Tenants and Ground-floor residents (useful for parking or garden notices), so an AGM notice, which owners legally need, tenants don't, only goes to the relevant segment. A water-cut notice, by contrast, should reach the full building regardless of ownership status.

Keep broadcasts to genuinely important notices; overuse trains residents to ignore them, which defeats the purpose the first time a real emergency notice needs attention.

Escalation to the committee

Set a resolution-time expectation per complaint category, for instance, 48 hours for non-urgent plumbing, same-day for security issues, and use a Wait / Delay block to check status after that window. If still unresolved, the flow automatically notifies the management committee or facility manager with the complaint details, rather than relying on the resident to escalate themselves by calling repeatedly.

Give residents a way to reopen a complaint too: a reply like 'still not fixed' against an existing complaint thread should route straight to escalation rather than creating a fresh, unlinked ticket that loses the original history.

Visitor, delivery and gate alerts

The same number can handle a lighter, separate use case: gate notifications. When the security desk logs a visitor or a courier at the entrance, either by messaging a keyword like 'VISITOR B302' or through a simple gate-register app connected as an inbound webhook, the flow sends the flat's resident a short alert with an Approve / Deny button pair, and relays the response back to the gate.

Keep this flow entirely separate from complaints and dues, since it runs far more frequently and needs to stay fast and simple, without the category questions a complaint needs.

Building it on Convo360 and measuring results

This runs comfortably as a Guided (no-AI) bot for the menu, complaint logging, dues reminders and gate alerts, with an optional AI Reply fallback for general questions about society rules or amenities, answered from an uploaded knowledge base such as the society's bylaws or FAQ document. See /docs/guided-bots/ and /docs/crm/.

To know whether it's actually working, check Flow Logs and the CRM pipeline monthly for three things: average time-to-resolution per complaint category, the share of dues collected before versus after the due date, and how many complaints needed committee escalation versus resolving within the vendor's own window. A rising escalation count in one category usually points to a vendor problem worth addressing directly, rather than a bot problem.

Step by step

1. Build the complaint category menuCreate a List Menu covering the common complaint types with a short follow-up per category.
2. Log complaints to the CRM pipelineRoute each logged complaint into a stage-based pipeline so status is trackable.
3. Set up maintenance dues remindersStore due dates as custom fields and send Utility template reminders on a T-5, due-date and T+3 cadence with a payment link.
4. Create notice broadcast templatesDraft templates for common society notices and send via segmented broadcast campaigns (owners, tenants, all residents).
5. Add escalation timingUse Wait/Delay to auto-notify the committee if a complaint stays unresolved past its window.
6. Add a visitor/gate alert flowConnect the security desk's keyword or gate-register webhook to send Approve/Deny alerts to the resident.
7. Review Flow Logs monthlyCheck resolution times by category and dues collection rate to see where the bot or a vendor needs attention.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.