Key takeaways
- One site group: crew, supervisor and the client's facility contact as a guest.
- Three posts per visit: arrival, issues during the shift and a completion report with photos.
- Client requests go into the site group, never to a cleaner's personal phone.
- Pin the site's scope of work and access instructions at the top.
- Owners and admins can export the group when a client disputes a visit.
Most complaints in contract cleaning are not about cleaning quality. They come from missed information: a request the crew never received, a change in schedule nobody confirmed, or no proof that an area was done. This page lays out a concrete workflow that puts crews and clients in the same conversation without losing control of it.
Why cleaning crews at client sites break down without a system
Client communication in janitorial work usually flows through three or four people: the client emails the account manager, who calls the supervisor, who texts the crew lead. Each hop adds delay and distortion.
The symptoms are familiar:
- Requests arrive after the crew has already left the building.
- The client calls a cleaner’s personal phone, and the supervisor never hears about it.
- A complaint arrives on Monday about Friday’s visit, and nobody can show what was done.
- Access instructions live in a notebook in the supply closet.
A shared site group removes the middle hops. The general case for it is covered in client communication in a dedicated group; this page is the cleaning-specific version.
The workflow in C Chat
- Create the site group inside your team, named “Site – [Client] – [Building]”.
- Add the crew and supervisor, then invite the client’s facility contact with guest access by link, email or WhatsApp.
- Pin the scope of work: areas, frequency, special instructions and access notes.
- Arrival post: the crew lead posts when the team is on site.
- During the visit: issues are reported with a photo (broken fixture, leak, missing supplies).
- Completion post: a short checklist and photos of key areas.
- Client requests are posted in the same group; the supervisor replies to confirm and assigns them.
Group setup and message template
Ask crews to use the same two posts every visit. Pin both templates so new staff can copy them.
Arrived – [time] · Team: [names or count] · Notes: [anything unusual at arrival]
Completed – [date] Done: restrooms ✓ · lobby ✓ · offices floor 3 ✓ · kitchen ✓ Pending: [item] – reason Issues: [item] – photo attached Supplies needed: [list]
Photos go as replies to the completion post, so each visit stays grouped together. For tips on taking useful photos, the approach in before-and-after job photos transfers directly to cleaning.
Roles, oversight and records
| Role | Responsibility in the group |
|---|---|
| Crew lead | Arrival and completion posts, photos, issues |
| Supervisor (admin) | Confirms requests, assigns tasks, handles complaints |
| Client contact (guest) | Requests, feedback, building information |
| Account manager | Watches for patterns, handles scope changes |
Messages are encrypted in transit with TLS and at rest with AES-256 using your organization’s key. Owners and admins can audit and export the team’s group conversations, which turns the site group into a service log you can share when a client questions a visit. Direct messages between staff stay private. Residential buildings with front desks often need a parallel channel with security; see condo front desk and security in sync.
Common mistakes to avoid
- One group for all clients. Clients would see each other. Always one group per site.
- Letting the client become the dispatcher. Requests should be confirmed by the supervisor, not acted on by whoever reads them first.
- Skipping photos on easy days. The visit you didn’t document is the one that gets disputed.
- Leaving former cleaners in the team. Remove them on their last day; they lose access to every site.
- Using a customer-facing tool for crews. Tools built for marketing to customers are a poor fit for internal crews; see C Chat vs WhatsApp Business.
Hotels run a similar loop between housekeeping and front desk in hotel housekeeping coordination, and construction teams apply the same guest model in subcontractor coordination. For the bigger picture on janitorial companies, see cleaning and janitorial teams.
Getting started
Pick one client who regularly sends requests, create their site group at getcchat.com/c and run the workflow for two weeks before rolling it out. It’s free for now, within the limits on the pricing page.
Frequently asked questions
Should cleaners talk to the client directly?
For day-to-day requests, letting the client post in the site group works well, because the crew and the supervisor see the same message. The supervisor should still own replies on scope, pricing or complaints, so agree on that rule before inviting the client.
What if the client doesn't want to install another app?
C Chat runs in the browser at getcchat.com/c, so a facility manager can join from a computer without installing anything. Mobile apps for iOS and Android are coming soon.
How many photos should a crew post after a visit?
Enough to show the areas the client cares about most, usually three to six: restrooms, entrance, kitchen or break room, and any area named in a recent request. Consistency matters more than volume.
Can the client see my other sites or staff conversations?
No. A guest only sees the group they were invited to. Your other site groups, supervisor discussions and direct messages are not visible to them.