Key takeaways
- Run one group per property, or per portfolio for small single-family units.
- Ask for a photo with every maintenance issue; it saves a site visit more often than not.
- Invite vendors and property owners as guests to the groups they need.
- Usernames let staff reach people without sharing their personal phone number.
- Group history can be exported when an owner, insurer or tenant dispute requires it.
Property managers sit between owners who want returns, tenants who want things fixed and vendors who want clear instructions and timely payment. Most of the friction comes from communication: requests that arrive by text to a manager’s personal phone, vendors who never confirm, owners who only hear about a burst pipe when the invoice arrives. A shared messenger built around properties brings order to that without a big software project.
Communication challenges in property management
- Requests come from everywhere. Texts, calls, emails and portal tickets, often to whoever the tenant knows.
- Vendors juggle many clients. Your plumber is also everyone else’s plumber; clear, photo-backed requests get prioritized.
- Owners need visibility. Surprise invoices damage trust faster than slow repairs.
- Staff turnover. When a property manager leaves, their phone leaves with them, along with years of context.
- After-hours emergencies. Leaks and lockouts do not respect office hours.
How property management teams use C Chat
A typical flow for a maintenance issue:
- Intake. The issue arrives through your portal or a call. The coordinator posts it in the property group with the unit, a description and the tenant’s photo.
- Dispatch. The coordinator replies naming the vendor who should take it. The vendor confirms with an estimated time.
- On site. The vendor posts a photo of the problem and, if needed, a quote as a file attachment.
- Approval. For larger work, the manager forwards a summary to the owner’s group for approval.
- Close. The vendor posts a completion photo; the coordinator closes the ticket in your system.
This is the same pattern described in maintenance requests with photos and in more depth in property maintenance requests and vendors.
Recommended group structure
| Group | Who is in it |
|---|---|
| [Property] – Maintenance | Coordinator, property manager, regular vendors (guests) |
| [Property] – Owner | Property manager, owner or owner’s representative (guest) |
| Portfolio – On call | Staff covering nights and weekends |
| Team – Internal | Managers and coordinators only |
For building-wide topics in multi-unit properties managed with a board, the setup in communication for condos and HOAs may fit better. A free C Chat team supports up to 30 groups and 50 members; you can create up to 5 teams per account if you split portfolios.
Guests: clients, contractors and vendors
Vendors are the most frequent guests: plumbers, electricians, HVAC technicians, cleaners and landscapers. Invite each one to the properties they service, not to your whole team. See guest access for contractors and clients and vendor and supplier communication for practical rules. For commercial buildings with multiple service contractors, facility vendor coordination describes a slightly heavier structure, and the wider operational view is in facility management communication.
Owners are guests too. Give them a clear, calm channel: monthly summaries, approvals and photos of significant work.
Security, privacy and audit
Property chats include tenant names, unit numbers, access codes and lockbox locations. C Chat encrypts messages in transit with TLS and at rest with AES-256, using a key dedicated to your organization. Phone contacts are matched using SHA-256 hashes computed on the device, and the server does not store those hashes.
Owners and admins of your team can audit and export group conversations, which helps with insurance claims, deposit disputes and owner questions. Direct messages between people stay private. If an owner or institutional client asks how you protect data, how to evaluate encryption claims and security questions to ask a messaging vendor help you prepare honest answers. As with any platform, avoid posting full access codes in large groups; share them only with the vendor who needs them.
Getting started
Start with your most active property. Create a team at getcchat.com/c, add a maintenance group and an owner group, then invite your regular vendors. Agents working on the sales and leasing side often use a different setup, described in secure chat for real estate teams.
Frequently asked questions
How do property managers communicate with maintenance vendors?
The most reliable setup is one group per property that includes your maintenance coordinator and the vendors who service it. Requests, photos, quotes and completion photos stay in that thread, so anyone on your team can pick up where a colleague left off.
Can property owners see what is happening at their building?
Yes, if you choose. Create an owner group for each property or owner and invite them as a guest. Post summaries, major repairs and photos there, while day-to-day vendor coordination stays in your internal groups.
Should tenants be in the same chat as vendors?
Usually not. Keep tenant-facing communication separate from vendor and staff coordination. Many managers keep tenant requests in their property management portal and use C Chat for the team, vendors and owners.
Do my staff need to share their personal phone numbers?
No. Each person can set an @username, and team members can message each other inside the team. Guests are invited to a group by link or QR, so staff do not need to hand out their own numbers.