Resident Communication: Slack, Telegram, Teams for Property Managers
A tenant once emailed her property manager about a dripping tap. Then she followed up on the portal. Then she called the office, was put on hold, and gave up. Eleven days later a plumber appeared. By then she had posted photos of the leak in the building's Facebook group, where three neighbours chimed in with their own grievances, and the manager found out about the thread from her own mother.
Eleven days. One tap. That's the whole case for fixing communication — no slide deck needed.
Most managers don't have a communication problem in the abstract. They have a channel problem: requests scattered across phone calls, WhatsApp, email, a portal nobody opens, and the occasional note taped to a radiator. Nothing is threadable, nothing is searchable, and "did anyone deal with this?" has no answer.
The honest solution that's emerged over the past couple of years is to stop inventing your own channel and meet residents where they already are. Which, increasingly, means Slack, Telegram, or Teams.
Meet residents where they already live (on their phones)
Here's the uncomfortable data point: a purpose-built resident portal might see 20–30% of residents log in during a normal month. Telegram, in Latvia and much of Eastern Europe, is simply where people are — often several times a day.
The trick is realising the tool follows the audience, not the other way round:
- Telegram is the default consumer messenger across the Baltics and much of Central and Eastern Europe. Building announcement channels, quick tenant chats, photo-documented repair requests — it fits like a glove. A Riga manager I know runs her entire operation through one Telegram chat per building, and tenants thank her for the response times.
- Slack suits professional and commercial tenants — co-working operators, office buildings, student housing run by universities. These people live in Slack from nine to five; a facilities channel there gets faster responses than any portal.
- Microsoft Teams is the corporate estate case: enterprise landlords, property management companies, anywhere the maintenance dispatchers and account managers already sit in Teams all day. Wiring building notifications into the same window means issues get triaged during the workday, not whenever someone checks a mailbox.
None of this means portals are dead. Documents, formal notices, payment records — those belong somewhere structured and legally reliable. But the conversation shouldn't be trapped behind a login nobody remembers.
Why messenger channels beat email for building matters
Group email has four failure modes, and you've met them all.
Reply-all storms. The one resident who replies to the sender instead of the group. Attachments that bounce because someone's mailbox is full. And the archive nobody can search when a dispute shows up two years later.
Messengers fix these structurally. Every request becomes a thread with a photo attached and a timestamp. Everyone sees the same announcement, so the "I never got that email" defence quietly dies. And the history is searchable — which matters more than people think until the day a tenant claims they were never told about the water shutoff.
There's a noise-management angle too. The classic complaint about resident chats is that they turn into an unusable firehose. The counter to that is channels, not silence:
- One announcements channel, read-only for residents, for official notices.
- One issues/repairs channel per building, where every message is a ticket in disguise.
- Direct messages for anything sensitive — arrears, neighbour disputes, personal circumstances.
Three channels per building, not one chaotic super-chat. The discipline lives in the setup, not in residents' restraint.
Scenario: a burst pipe, handled
Say a washing machine hose lets go on the fourth floor on a Tuesday morning. In the email-and-phone world this becomes a chain of phone calls, one missed, one voicemail, and a tenant who photographs the ceiling for the insurance claim while the damage spreads.
On Telegram: the tenant sends a photo into the building's issues channel at 08:41. The manager — who sees it over her coffee because the message is in the app she already has open — replies at 08:47, forwards it to the plumber with two taps, and posts an update to the announcement channel: "Water off between 10:00–12:00, fourth floor, plumber confirmed 09:30."
Eleven neighbours read it before they leave for work. Nobody knocks on the wrong door. The plumber's invoice later references the timestamped thread, and when the downstairs neighbour asks about damage to their ceiling, the answer is a link, not a memory exercise.
That entire story is the difference between "we have communication" and "we have responsive communication."
What Urbaneta does with this
This is where our own work comes in, so a bit less anecdote and more substance: Urbaneta sends notifications into Slack, Telegram, and Microsoft Teams directly. You connect your workspace once and the building's communication runs through channels your residents and your team already use.
What gets pushed:
- New maintenance requests — arriving in the building channel with tenant name, unit, and the attached photo, ready to triage.
- Status updates — request accepted, plumber scheduled, resolved. Residents stop asking "any news?" because the news arrives on its own.
- Payment reminders and receipts — polite, automatic, and sent where tenants will actually see them within minutes.
- Announcements — water shutoffs, winter heating schedule, building meeting notices, published to the read-only channel without printing a single paper notice.
The principle we kept coming back to while building this: notifications are not a feature, they're a behaviour. A notification system that dumps everything into one undifferentiated stream gets muted within a week, and then you've gained nothing. So each channel and each notification type stays configurable — important things break through, routine things wait in their lane.
Ground rules that keep it humane
A few boundaries worth setting on day one, before habits form:
Response-time honesty beats speed theatre. If maintenance requests get answered within hours but rent questions take three days, residents learn to route everything through whatever channel is fastest. Publish simple expectations — issues channel: same working day; payments: 2–3 business days — and people adapt surprisingly well.
Emergencies get a phone number, not a chat. No building should depend on someone watching a Telegram channel at 3 a.m. Put the emergency line in the channel description and repeat it in every announcement that touches utilities.
Personal matters go private. Arrears, complaints about neighbours, health-related requests — move them to DMs immediately, kindly. The tone you set in the first weeks determines whether the channel feels safe.
Keep the formal record parallel. Messenger threads are evidence of good service but not a legal archive. Service notices, rent adjustments, lease changes still go through the formal channel — email or portal — where dates can't be disputed.
How you'll know it's working
One more thing before the anecdotes end and you go build channels: measure something, or the whole initiative drifting back into the mailbox within a quarter is a real risk. Three numbers tell you almost everything.
Median time to first response in the issues channel. Not average — median, because one 3 a.m. emergency will wreck the average and teach you nothing. In a healthy building this sits at a couple of hours during the day.
Share of requests resolved without a single phone call. If it's above 70%, the channel is doing its job. Below half, people are probably reporting things in the chat and phoning, which means they don't trust the chat yet.
Announcement reach, if your platform shows it. Telegram channels display view counts — for a 40-flat building, 30+ views of the water-shutoff notice is the difference between an empty corridor on Tuesday and seventeen confused door-knocks.
A quiet aside about water heaters and trust
Every long-experienced manager has one story about an announcement that nobody read. Mine involves a scheduled hot-water shutoff in a Grīziņkalns building, announced properly by letter, ignored by nearly everyone, and then a full evening of doors and kettle jokes. The following year the same notice went to the building's Telegram channel and got seventeen "👍" reactions before lunch.
Same information. Different pipe. Utterly different outcome.
That's the whole thesis of this post, honestly. The content of your communications was probably never the problem. The delivery pipe was.
Getting started without a Big Bang
Don't launch this across forty buildings on a Monday. Pick the noisiest building you manage — the one with the broken-lift Facebook group, if it exists. Create the three channels. Connect the notifications. Spend two weeks being extravagantly responsive there. Then let the rest of the portfolio ask for it, because they will; residents in the quiet buildings hear about the fast one faster than you'd think.
Try Urbaneta free — 14 days, no credit card. Connect Slack, Telegram, and Teams in minutes and find out what your buildings sound like when communication actually flows.
