What a custom agent looks like inside a commercial cleaning or janitorial contractor — the ten roles in your language, and what each plugs into in a business running Swept, CleanTelligent or Aspire alongside scheduling and payroll.
last reviewed
Commercial cleaning is a labor business with thin margins and a distributed, high-turnover workforce that works when nobody is watching. That combination makes two things expensive: proving the work was done, and keeping shifts covered. Almost every administrative cost in the business traces back to one of those two, and both are communication problems rather than cleaning problems.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
Purpose-built systems covering inspections, shift tracking, supply requests and client reporting for distributed cleaning crews.
Used where cleaning sits alongside other service lines, covering contracts, scheduling and job costing.
Clock-in from a phone or a site device, frequently geofenced, and the primary control on whether a shift actually happened.
Scored inspections with photographs, which are what a client sees and what a contract renewal usually turns on.
High headcount, high turnover, multiple sites and shift differentials, which makes payroll error-prone and time-consuming.
Ordering against sites and budgets, usually reactive and rarely reconciled against what a contract includes.
Requests, complaints and special cleans arriving by email and text from building contacts.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.