Secure client accounts
Each client signs in to see only their own properties, visits and invoices, and office staff can use two-step sign-in.
Pool clients ask the same things every month: when is the next visit, what did the technician find, and where is the invoice for the pump repair. A customer portal for pool maintenance companies answers those questions in one secure place, so the operations team stops fielding them by phone and text.
The operations manager carries the most risk if one client sees another household's visits or a technician's note lands in the wrong inbox. Before approving the portal, that person needs to sign in as a test client, see only that account's visits and invoices, and confirm that a logged-out visitor sees nothing except public pages. We run that check on a staging copy before anything goes live.
They also want to see the daily workflow. A request raised in the portal should appear in the dispatch queue with the account's service plan attached, and a crew update should reach the client without a second system. We agree those hand-offs with operations before any screens are designed.
A portal holds names, addresses, gate details and payment history, so privacy rules apply even to a small service company. California's consumer privacy law, the CCPA, gives residents rights to request their data or ask for it to be deleted, and the portal needs a route for handling those requests within the time the law allows.
Account security matters as much as the layout. Require strong passwords, offer two-step sign-in to office staff, and lock an account after repeated failed attempts. Service notes and invoices may also need to be kept for a set period, so the retention rule should be written down before the first document is uploaded.
A portal is only useful once it holds accurate records. The company needs an account list with service plans, the visit history it wants clients to see, and the documents it already emails, such as service agreements, invoices and repair quotes. Check older files for outdated gate codes before they go online.
Decide early who sees what. A homeowner should see one property, while a management firm with twelve pools needs a view across all of them. That split is simple to build when the account structure is agreed first, and painful to change after clients have logged in.
Each client signs in to see only their own properties, visits and invoices, and office staff can use two-step sign-in.
Clients see what was done on each visit, the chemicals used and any follow-up the technician recommends, written in plain language.
Agreements, invoices, quotes and completed service sheets sit in one place, listed by date, so clients stop searching old emails.
A client can ask for a repair or a schedule change and follow its status until the crew closes it, without another phone call.
Managers who look after several pools switch between sites from one login, limited to the properties they are allowed to see.
Requests raised in the portal land in the queue the office already uses, with the account and service plan attached.
A portal that only lists invoices is the usual mistake. Clients log in to ask something, and if the portal cannot take a request, change a visit or flag a pump that is making noise, they go back to the phone. A useful portal earns its place by replacing the most frequent calls.
Another trap is handing the crew a second app they will not open. Technicians work from a truck, so updates should be short, quick to tap and plain. If closing a job takes a paragraph of typing, the client sees nothing for days.
Skipping offboarding is the last one. When a home is sold, the old owner's access should close the same day, and the new owner should start with a clean account rather than someone else's visit history.
Clients only sign in when someone explains why. Send each active account a short email with one sign-in link, the three things they can do in the portal and the phone number for anything else. A mass announcement that reads like a newsletter gets ignored.
Give the office a fixed routine for the first few weeks. Every request that arrives by phone also gets logged in the portal, so the record stays complete and staff learn the screens. Note which questions clients keep asking and add those answers to the portal's help page.
Track the calls about invoices, visit times and service notes each month, and compare them with the same month before launch. A drop in those calls means the portal is carrying the load the phone used to carry.
Also watch how many clients sign in at least once a quarter, how long requests stay open and how many invoices are paid without a reminder. Those figures show whether the portal should be kept as it is, extended or simplified.
No. Each account is separated, and a client sees only their own properties, visits and documents. We test that separation by signing in as a test client before launch rather than trusting the settings alone.
Probably not, and that is not the aim. A green pool two days before a party should still reach a person quickly. The portal takes the routine questions off the phone so the office has time for urgent ones.
Only the roles you approve. Access notes sit outside the general view, clients cannot edit them, and technicians update them from the job screen after a visit.
Websites range from $300 to $2,200, depending on scope. Account roles, document storage and dispatch links drive most of the cost, and the price goes on paper before the build starts.
The number of account types, document types and dispatch links sets the pace. We agree the scope in writing after the free scoping call, so the plan for building it is clear before any work begins.
Begin with a free scoping call, where we will walk the account roles, document types and request flow, and only then the price.