Resident Requests in Property and Facility Management: From the WhatsApp Group to a Real Record
Short answer: In property and facility management, requests live almost entirely in WhatsApp groups. The group is fast, but it cannot do three things: assign a request to a person, measure time, or hand history over when the management changes. The fix isn't banning the group; it's turning the incoming message into a record.
Why the group isn't enough
A building management group carries all of this in a day: a parking complaint, a lift fault, a dues question, a noise report, a concierge request, a delivery note. All in one stream, none of them owned.
The result is familiar:
The same fault is reported three times by three residents; the manager answers three times.
A request scrolls up the feed; nobody takes it, so it drops.
"What was done this month?" is answered by scrolling message history.
When the management changes, the group remains but institutional memory doesn't, because it never
formed.
Turning a request into a record
Tixenta pools requests from email, WhatsApp, web forms and API into a single queue. Residents don't have to change their habits; they keep writing on WhatsApp; what changes is that the message becomes a record, gets assigned to a person, and produces an outcome.
There is also a guest ticket flow: a resident opens a request with an email address and a tracking code and follows it with the same code. Nobody has to install an app or create an account.
Who should see what?
Authorization is granted through the combination of role, organization, department and record ownership (RBAC + ABAC). In building management, this design ends most disputes before they start:
The technical team sees only maintenance records, not dues or debt information.
Accounting sees only financial requests.
Board members see summaries and reports without needless access to personal complaint content.
A resident's complaint is not visible to the neighbor they complained about.
Time: a date instead of "we'll take care of it"
Tixenta tracks first-response and resolution times; it warns before the clock runs out and raises an instant alarm on breach. What gets discussed in the monthly meeting becomes a number rather than a perception: how many requests arrived, how many closed, which topic is waiting.
The management handover: the critical moment
In building management, terms end and teams change. Without records, the incoming management starts from zero; it doesn't know which fault is chronic or what was agreed with which supplier.
In Tixenta every state-changing action is logged automatically and the record cannot be edited afterwards. The handover isn't a folder delivery; it's the continuation of the system. It is also the most concrete form of transparency toward residents.
Managing more than one building or site?
Professional facility management companies run dozens of sites at once. Tixenta hosts multiple organizations under a single URL and isolates each site's data: a site manager sees their own site, headquarters sees the whole portfolio. Signing a new site means defining a new organization, not running a new installation.
Supplier and team coordination
Lift company, cleaning contractor, security; most of the work comes from outside. With internal staff chat (one-to-one, group and channel messaging, file sharing, read receipts), coordination runs inside the platform; the fault photo a technician sends stays next to that fault's record.
Resident data and privacy
Resident information is personal data, and complaint content can be sensitive. A Türkiye-based, KVKK/GDPR-compliant structure with logged access also protects the management itself.
A two-week rollout
Week | Action |
|---|---|
1 | Name your request types (maintenance, dues, complaint, suggestion, security); write down who handles which |
1 | Put the guest request link on the notice board and in the group description |
2 | Set a target time per request type |
2 | Share the first monthly report with residents; this is where the benefit becomes visible |
Frequently asked questions
Residents won't give up WhatsApp; is that a problem? No. The goal isn't changing the channel, it's turning the message into a record.
Does it handle dues and accounting? No; financial software is a separate domain. Tixenta manages the request and connects over API where needed.
Is it overkill for a small building? Even with few requests, the need for transferable records and transparency is the same; the setup can stay small.
Related reading
Tixenta combines omnichannel ticketing, a guest request flow, multi-organization isolation and an immutable audit log in one platform.