Key takeaways
- Use one group per building or portfolio for internal requests and one per vendor or trade.
- Every request carries a photo, a location in the building and a priority.
- Vendors join as guests to their own group, never to internal building groups.
- Before-and-after photos give you proof of work for invoices and owner reports.
- Owners and admins can audit and export group history; direct messages remain private.
Maintenance in residential and commercial buildings is mostly coordination: someone notices a problem, someone decides who fixes it, someone lets the vendor in and someone checks the result. When each of those steps happens on a different phone call or a personal chat, jobs stall between steps and nobody can say what was done in Unit 4B last month.
Why property maintenance breaks down without a system
The usual failure points are predictable:
- Requests arrive everywhere. Calls to the manager, texts to the superintendent, notes under the office door.
- Vendors get the wrong information. A plumber shows up without the access code or the unit number.
- No proof of work. An invoice arrives for a repair nobody photographed.
- Old vendors keep access. A contractor from two years ago is still in a group that shares gate codes.
For the broader sector view, see property management communication and facility management team communication.
The workflow in C Chat
- Report. The superintendent or a staff member posts the issue in the building group with a photo and location. The approach mirrors maintenance requests with photos.
- Assign. The property manager replies with who handles it: in-house staff, or a vendor.
- Brief the vendor. The manager forwards the details into that vendor’s group, with access instructions and a time window.
- Do and document. The vendor posts a before photo on arrival and an after photo when finished, plus any notes on parts or follow-up visits.
- Close. The manager or superintendent checks the work and replies “closed” in the original request thread.
Recurring vendors, such as a landscaping company or an elevator technician, can keep a standing group where the schedule and the site rules stay pinned.
Group setup and message template
| Group | Members | Notes |
|---|---|---|
| [Building] – Maintenance | Manager, superintendent, in-house techs | Internal requests and status |
| [Vendor] – [Building] | Manager, superintendent, vendor (guest) | Briefs, access notes, photos |
| Portfolio – Managers | Property managers only | Escalations, budget questions |
Vendors join through guest access: they are invited to a specific group and see nothing else in the team. The general practice is covered in vendor and supplier communication, and larger campuses can follow facility vendor coordination.
Pin this request format in each building group:
[Priority: urgent / this week / routine] – [Unit / area] – [What’s wrong] – [Photo attached] – [Access: tenant home? key at desk?]
Roles, oversight and records
Property managers should be admins; the portfolio director can be the team owner. Admins add superintendents and vendors and remove them when they leave or the contract ends.
Messages are protected in transit with TLS and stored with AES-256 encryption using keys specific to your organization. C Chat’s auditable model lets owners and admins audit and export group conversations, which turns chat history into evidence when an owner questions an invoice or a tenant disputes when a repair happened. Direct messages between individuals are private. Before you put access codes or tenant details in any chat tool, it is worth reading how to evaluate a vendor’s encryption claims and the security questions to ask a messaging vendor.
Common mistakes to avoid
- Adding vendors to internal groups. They see every other job, every tenant complaint and every code. Use separate vendor groups.
- Permanent codes in chat. Share temporary access where possible, and pin it only for the job duration.
- Requests without location. “Leak on the 3rd floor” sends someone searching. Name the unit or room.
- No close-out message. Without an explicit “closed”, the request looks open forever.
- Mixing tenants into staff groups. Keep tenant communication separate from vendor coordination.
Buildings with a front desk and a security company add one more layer; see condo front desk, security and board for that setup.
Getting started
Create a team, set up a maintenance group for each building, invite your superintendents, then add each regular vendor to their own group by link or SMS. C Chat is free for now with up to 50 members and 30 groups per team and 25 MB per attachment; check pricing and limits and open the web app at getcchat.com/c.
Frequently asked questions
How should a maintenance request be reported by chat?
Post one message per issue in the building group with a photo, the exact location (unit, floor, room), what is wrong and how urgent it is. One issue per message makes it easy to reply, assign and close without confusion.
Can vendors see our other buildings or internal discussions?
Not if you set it up correctly. Invite each vendor as a guest to a group created for their work, and keep internal building groups for staff only. Guests only see the groups they were invited to.
Is C Chat a work order system?
No. C Chat is a messenger with groups, photos, files, pinned messages and search, not a ticketing tool with work order numbers or due dates. Many small property teams coordinate by chat and keep a simple spreadsheet or their existing software as the record of jobs.
How do I stop a former vendor from seeing building information?
Remove them from the group when the contract ends. Because the group belongs to your team, the history of the work stays with you after they leave.