Client accounts with property-level access
Each login sees only the homes or buildings on its contract. Owners, property managers and office staff each get the view their job needs.
A property manager with several buildings and a homeowner with one house want the same thing from a window cleaner: a clear record of each visit, the invoice and a quick way to ask for a fix. A customer portal for window cleaners gives every account a private login built for exactly that.
The operations manager usually asks for a walk through with three test accounts: a homeowner on a recurring plan, a property manager with several buildings, and a storefront owner who needs one fix. Each test asks one question. Does the account see only its own properties, and does a request reach the crew's schedule without anyone retyping it?
The manager will also check the visit record line by line. Each entry should name the building, the areas cleaned, the technician on site and the photos taken on arrival and after the job. If those details are missing, the office ends up answering the same questions by phone.
Finally, the manager will look at money. Invoices should open from the account, link to the visit they cover and show whether they are paid. Card numbers should never be stored in the portal itself.
Most window cleaning clients care first about proof. A homeowner wants to know the upstairs panes were done on the last visit, and a property manager needs dated records to show a board that the work happened. A clear visit history for window cleaning clients answers those questions before anything else is built.
Once visit records work, the fix request is the next feature worth building. A client picks the building, describes the problem, such as streaking on a storefront or a missed sill, and attaches a photo. The request then moves from received to scheduled to done.
The property manager receives an invitation email and sets a password on the first sign in. The account lists the four buildings under her contract, and each one opens to its own visit history, invoices and documents. Nothing from another client's account appears on that screen.
After a Thursday visit, she notices a missed row of windows on the lower floor of one building. She taps New request, selects the entrance area and attaches a photo from her phone. The crew lead sees the same photo on his route the next morning.
The coordinator confirms a return visit that afternoon, and the status changes to scheduled. When the crew marks the job complete, the manager sees the after photos in the visit record and downloads the invoice. The whole exchange sits in one thread on the property.
Each login sees only the homes or buildings on its contract. Owners, property managers and office staff each get the view their job needs.
Every visit shows the date, the technician, the areas cleaned and the photos taken on arrival and after the job.
A client describes the problem, attaches a photo and watches the status move from received to scheduled to done.
Invoices open from the visit they cover, and certificates of insurance show their expiry dates to the office team.
A window cleaning client login holds addresses, gate and key-box instructions, and photos of private homes. The build should restrict every account to its own properties, store gate codes in a field that crews see only on the day of service, and log each login and document download. Password resets should go to a verified email or phone number.
Some rules come from outside the software. Crews working on ladders and high places follow OSHA fall protection requirements, so safety briefings stay internal. Commercial clients often require current certificates of insurance, so each document needs a visible expiry date.
If the portal takes payments, the card processor must be PCI compliant, and the portal keeps only the payment status and the receipt. We confirm these details on the free scoping call, before any build decision.
The most common mistake is building the portal around the invoice and skipping the visit record. Clients log in to see proof of work, and an invoice alone sends them straight back to the phone. Teams also load every property and route into the first release, when a small group of accounts would show whether the design holds.
Another mistake is giving office staff and crew leads the same permissions as the owner. Staff need schedules and open requests, but they rarely need to edit billing or delete a client's history. Set roles on day one.
A portal only works when the crew uses it too. Give each lead a short walk through on their own phone during the first week, and have the office send client invitations the day after a first visit, while the job is fresh. Clients who see their first visit record online usually keep checking it.
Pair the launch with habits you already have. Print a card with the portal link on the next invoice, add it to service email signatures, and have the coordinator mention it on the scheduling call. Watch logins and fix requests in the early weeks, and change the screens clients abandon. Post-launch support is available for those changes.
Website projects range from $300 to $2,200, depending on scope. Logins, property-level access and fix requests are scope items, so the free scoping call sets the exact figure. The final price is confirmed in writing before work starts.
Yes, that is the usual setup, since crews are often between jobs in a van. Entries should be time-stamped and locked after completion. Any later correction goes through the office and leaves a trace.
Homeowners tend to use a portal when the visit record and the invoice live in the same place. A login is only needed once, so the first sign in has to be easy. We test that path with real account types during the walk through.
No. One login can list every building under the contract, and each property opens to its own history and documents. A storefront owner gets a simpler view with a single property. Roles can be changed later.
Each login sees only its own properties, and every access is logged. Gate codes sit in a restricted field that appears only on the day of service. Card numbers are never stored in the portal.
Book a free scoping call with SIZ Group, and we will confirm the scope and price in writing before any build starts.