Every Brazilian condominium communicates via WhatsApp, and almost none communicate well. The superintendent’s personal cell phone is listed on the building description, the residents’ group mixes official notices with garage spot discussions, and maintenance requests get lost among three hundred messages. The problem is rarely the volume — it’s that three completely different types of communication are happening in the same place, and none of them work well there.
In this article
- The three channels that must exist separately
- Why the residents’ group doesn’t solve it
- The superintendent’s cell phone can’t be the central hub
- Maintenance requests need a number
- Official notices are broadcasts, not conversations
- Assembly, summons, and the record that protects
- Delinquency collection, with care
- LGPD in the condominium, more serious than it seems
- An administrator’s account
- Five communication mistakes in the condominium
- The numbers to track
- Frequently Asked Questions
The three channels that must exist separately
Almost all communication disorganization in condominiums comes from treating as one thing what are actually three activities with opposite natures.
Channel 1 — official notice. From management to residents. Maintenance notice, scheduled water cut, summons, rule change, financial report. One-to-many, does not allow public response, and requires proof of sending.
Channel 2 — request and service. From resident to management. Apartment leak, burned-out garage light, second copy of boleto, fee question, moving authorization. One-to-one, requires protocol, deadline, and responsible party.
Channel 3 — resident coexistence. Neighbor talking to neighbor. Furniture sale, lost and found, housekeeper recommendation, noise complaint. Not management’s responsibility and should not go through them.
When all three share the same group, each spoils the other two. Official notices get lost in conversation. Requests turn into public debates. And coexistence generates conflicts that the superintendent has to manage.
Why the residents’ group doesn’t solve it
The group seems like the obvious solution but creates four predictable problems.
Important notices disappear. A notice about a water cut posted at nine in the morning is forty messages away by eleven. Anyone joining the group at night won’t scroll back that far.
Discussion replaces decision. Matters that should be handled in assembly, with quorum and record, are debated in the group with fifteen people giving opinions — the result has no validity but creates expectations and resentment as if it did.
Conflict becomes public and permanent. A noise complaint made in the group creates a neighbor dispute lasting years. The same complaint made as a request is resolved discreetly.
Everyone sees everyone’s phone number. This has privacy consequences that almost no one considers, and for which management is responsible.
Groups work well for only one thing: voluntary coexistence among residents, managed by a resident and not by management, with management explicitly outside it. Everything official needs another channel.
The superintendent’s cell phone can’t be the central hub
This is the most common and most unsustainable setup. The superintendent’s personal number is on the building door, in the group, on paper stuck in the elevator — and the consequence is predictable: messages at eleven at night, on Sundays, during vacations.
Three problems go beyond inconvenience.
No record. When the superintendent leaves, the entire condominium history leaves with them — requests, authorizations, agreements with suppliers, all inside a personal cell phone that no one else accesses.
No continuity. The superintendent travels, gets sick, or leaves office, and service simply stops because no one else has access to the channel.
No protection. A dispute that becomes a lawsuit, an authorization that becomes a conflict, a collection that becomes a complaint — all need records, and the records don’t exist.
The solution is a condominium number, not a person’s. It remains when the superintendent changes, can be accessed by multiple people with different permissions, and keeps the history where it belongs: with the condominium.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
Maintenance requests need a number
The biggest source of dissatisfaction in condominiums is not the problem itself: it’s not knowing if someone is taking care of it. A resident reports a leak and gets no response in two days, reports again, then complains in the group, then approaches the superintendent personally in the elevator.
A well-structured request has five elements, none of which require expensive software to exist:
- Protocol. A number given to the resident at the time of opening. This alone drastically reduces repetition because the person has something to refer to.
- Category. Maintenance, finance, gatehouse, moving, complaint. Defines who handles it.
- Named responsible party. A person, not management in the abstract.
- Declared deadline. It’s not always possible to resolve quickly, but almost always possible to say when.
- Closure feedback. The most neglected step. A resolved request without notice is indistinguishable from an ignored request.
An operational detail that changes the perception of the entire building is worth mentioning: intermediate feedback. "Your request 342 has been forwarded to the maintenance company, expected service on Thursday" is a ten-second message that avoids three follow-ups and a complaint at assembly.
Official notices are broadcasts, not conversations
Notices need to reach everyone, be recorded, and not generate debate in the same place. Three precautions make this work.
Individual sending, not group. Each resident receives the message directly, ensuring it appears at the top of the conversation and not buried. This requires a contact database organized by unit, which the condominium should have anyway.
Prior authorization. Sending mass messages to those who have not authorized is problematic legally under LGPD and practically because it causes blocks that reduce number quality. Authorization is collected when the resident moves in or in a one-time opt-in campaign and recorded.
Proof of sending. In assembly, someone will say they were not notified. Having the date and time of sending for each unit settles the matter in seconds, and is exactly the kind of thing a WhatsApp group does not provide.
For content, the rule is simple: subject, what changes, when, and what the resident needs to do. Long notices are not read, and notices without clear action generate ten questions that could have been avoided.
Assembly, summons, and the record that protects
Assembly summons have form and deadline requirements set in the condominium’s bylaws and legislation, and WhatsApp usually does not replace the required form — it complements it.
In practice, what works is using the channel to increase attendance without replacing the formal procedure: send the summons also by message beyond the required form, remind two days before, remind on the day, and make the agenda and documents accessible. An assembly with quorum decides; one without quorum is the problem returning in sixty days.
A warning that avoids conflict: voting by message is not voting, except when the bylaws and applicable legislation allow the format and the procedure meets requirements. Informally consulting the group and treating the result as a decision is one of the most frequent causes of later disputes.
Delinquency collection, with care
Collection by message works well and is where the condominium is most legally exposed. Three rules avoid almost all problems.
Always individual, never public. Naming a delinquent in a group, published minutes, or any collective channel is improper exposure with real consequences. The Civil Code prohibits coercion in collection, and case law on exposing delinquent residents is consistent.
Informative tone, not coercive. Amount, reference, due date, payment methods, and negotiation channel. No threats, irony, or mention of consequences not foreseen.
Reasonable frequency. Spaced reminders, not daily messages. Persistent collection is coercion regardless of message content.
Done this way, collection by message is remarkably effective, because much condominium delinquency is not refusal — it’s lost boleto, passed due date, resident who changed banks. A reminder on the channel the person actually uses solves a large part before it becomes debt.
LGPD in the condominium, more serious than it seems
The condominium handles personal data in volume and often unknowingly: name, unit, phone, vehicle plate, camera images, visitor entry records, financial status.
Four practical precautions matter more than any written policy. Contact database with recorded authorization, not an informally assembled list over the years. Controlled access, so that doorman, janitor, administrator, and superintendent see only what they need, not everything. Never disclose a resident’s financial status in a collective channel. And history that remains with the condominium, not with the person who held the position — because personal resident data inside a former superintendent’s personal cell phone is a problem no one can solve later.
An administrator’s account
Administrator with 19 condominiums, about 2,100 units, four-person service team.
Initial situation: service by phone and corporate cell phones without centralized history. Notices sent in groups created by building. Requests recorded in spreadsheets, no protocol given to residents. The team estimated 40% of received messages were repeats of already addressed topics.
What changed: one number per condominium, centralized, with the team serving from a single panel. Notices sent individually with recorded authorization, no more groups. Protocol given at every request opening, with mandatory intermediate and closure feedback. And coexistence groups formally handed over to a volunteer resident in each building, with the administrator leaving them.
Six months later: message volume dropped 34%, almost entirely by eliminating repetition. Average request closure time dropped from 6.2 to 2.8 days. And the team started ending the day with zero inbox, which never happened before.
In hours: reducing repetition and eliminating history search returned about 62 hours per month to the four-person team — just over half a full-time position, recovered without hiring anyone. The administrator used this capacity to take on three new condominiums without expanding the team.
Five communication mistakes in the condominium
- Using the group for official notices. The notice disappears and residents rightly say they didn’t get it.
- Leaving the superintendent’s personal number as the building’s channel. No record, no continuity, no protection when the term ends.
- Opening requests without protocol. Guarantees repetition because residents have nothing to refer to.
- Naming delinquent residents in collective channels. It’s improper exposure with real legal consequences and zero benefit.
- Treating group consultation as a decision. Has no validity and causes later disputes.
The numbers to track
Five indicators show if condominium communication is organized. Average request closure time, by category, which residents actually perceive. Percentage of requests with recorded closure feedback, usually the most neglected step and the one that most reduces complaints. Repetition rate, measured as messages about ongoing topics, the best gauge of protocol effectiveness. Notice reach, comparing units that received it with total units, since a notice that didn’t arrive causes half of assembly conflicts. And delinquency recovered before the second installment due date, measuring if reminders act while it’s still cheap to resolve.
Frequently Asked Questions
Does a WhatsApp group work for condominiums?
It works well for only one thing: voluntary coexistence among residents, managed by a resident and with management explicitly outside it. For official communication, it creates four predictable problems. Important notices disappear because a notice posted at nine in the morning is forty messages away by eleven and newcomers at night don’t scroll back that far. Discussion replaces decision, with matters that should go to assembly debated by fifteen people with no validity but generating expectations and resentment as if valid. Conflict becomes public and permanent, since a noise complaint in the group creates a neighbor dispute lasting years, while the same complaint as a request is resolved discreetly. And everyone sees everyone’s phone number, which has privacy consequences management is responsible for.
Why shouldn’t the superintendent use their personal cell phone for the condominium?
Besides the inconvenience of messages at eleven at night and on Sundays, there are three structural problems. No record: when the superintendent leaves, the entire condominium history leaves with them — requests, authorizations, agreements with suppliers, all inside a personal cell phone no one else accesses. No continuity: the superintendent travels, gets sick, or leaves office, and service simply stops because no one else has access. No protection: a dispute that becomes a lawsuit, an authorization that becomes a conflict, or a collection that becomes a complaint all need records, and the records don’t exist. There’s also a data protection issue, because personal resident information inside a former superintendent’s personal device is a problem no one can solve later. The solution is a condominium number, not a person’s.
How to organize maintenance requests in a condominium?
With protocol, because the biggest source of dissatisfaction is not the problem itself but not knowing if someone is taking care of it — a resident reports a leak and gets no response in two days, reports again, complains in the group, then approaches the superintendent in the elevator. A well-structured request has five elements: a protocol number given to the resident at opening, which alone drastically reduces repetition by giving the person something to refer to; a category defining who handles it; a named responsible party, not management in the abstract; a declared deadline, since it’s not always possible to resolve quickly but almost always possible to say when; and closure feedback, the most neglected step, because a resolved request without notice is indistinguishable from an ignored one. Intermediate feedback also prevents repeated follow-ups.
Can you collect overdue condominium fees via WhatsApp?
Yes, and it works well if three rules are respected — it’s where the condominium is most legally exposed. Always individual, never public: naming a delinquent in a group, published minutes, or any collective channel is improper exposure with real consequences, and the Civil Code prohibits coercion in collection, with consistent case law on exposing delinquent residents. Informative tone, not coercive, providing amount, reference, due date, payment methods, and negotiation channel, without threats, irony, or mention of unprovided consequences. Reasonable frequency, with spaced reminders instead of daily messages, because persistent collection is coercion regardless of message content. Done this way, it’s effective since much delinquency is lost boleto, not refusal to pay.
Can assembly summons be made via WhatsApp?
Summons have form and deadline requirements in the condominium bylaws and legislation, and messages usually do not replace the required form — they complement it. What works is increasing attendance without replacing the formal procedure: sending the summons also by message beyond the required form, reminding two days before, reminding on the day, and making agenda and documents accessible, because an assembly with quorum decides and one without quorum is the problem returning in sixty days. An important warning: voting by message is not voting, except when bylaws and applicable legislation allow the format and the procedure meets requirements. Informally consulting the group and treating the result as a decision is a frequent cause of later disputes.
Should the condominium’s history be on one person’s cell phone?
VeyloCRM provides one number per condominium, with the entire team serving from the same panel, protocol per request, individual notices sent to the authorized base, and complete history by unit that remains with the condominium when the superintendent changes.