Manage your techs and see what got done in the field

Add each tech, assign them their routes, and they see their stops on their own phone. Every paid plan includes unlimited users, so you can bring on as many technicians as your operation needs without it affecting your bill. Each tech logs in with their own account and sees only the routes assigned to them, which keeps the app focused and straightforward on their end. On the admin side, you get a single view of the day's progress across your whole crew - which stops are done, which are in progress, and what's still ahead. That means less time calling around to check on people and more time running the business. Routes and stops are managed from the dashboard, and any change you make shows up on the tech's app right away. There is no limit to how many technicians you can add on any paid plan. Because the technician view and the admin view draw from the same records, what a tech logs in the field is exactly what you see from the office, with nothing to reconcile between the two.

The route view shows each tech's day in progress: which stops are done, the one currently in progress, and what is still ahead on their schedule. Each completed stop logs a timestamp and the chemical readings the tech entered, so you have a record of exactly when the work was done and what conditions were found at the pool. You do not need to call techs to get a status update - the admin dashboard reflects the current state of every route in real time. If a tech marks a stop complete, you see it. If they log readings, those appear on the customer's pool record immediately. This log is permanent, so even if you later deactivate a tech who has moved on, every visit they completed and every set of readings they recorded stays in your history. The point is that you can see the day unfold from a screen instead of a string of phone calls, and the record it leaves behind is built as a byproduct of the tech doing their normal logging.

Assign a route to a tech and every stop on that route becomes theirs. The tech is notified and the change shows up on their phone right away - they do not need to do anything to receive it. If you need to move work, you can reassign the route to a different tech or adjust a single day without affecting the rest of the schedule. Pools are organized into routes, and routes are what you assign to technicians, which makes it straightforward to manage a crew that covers different areas or different days of the week. When a tech opens their app, they see the stops assigned to them in order, along with the customer name and address for each one. Any update you make on the admin side is reflected on their app immediately, so there is no lag between a schedule change and the tech knowing about it.

No. Pricing is by pool count, and every paid plan includes unlimited users. Adding a technician - or ten - does not raise your bill. The plans are Free at no cost (up to 20 pools, 1 admin), Startup at $29 per month (up to 100 pools), Pro at $79 per month (up to 250 pools), and Fleet at $249 per month with no pool ceiling. None of those tiers puts a limit on how many technicians you can add. This is the opposite of per-seat tools, where every hire means a higher monthly cost. With PoolBoss, the only number that drives your plan tier is how many pools you are servicing. If your crew grows because your route count grows, you may move up a plan tier based on pool count, but the number of technicians themselves is never the factor. So a busy season that means hiring extra hands costs you nothing more in software, which is exactly the situation where per-seat pricing tends to punish a growing pool company.

Techs see their own assigned routes and stops. Nothing else. When a technician logs in on their phone, the app shows them their schedule for the day - the stops on their routes, in order, with the customer name and address for each. They do not have visibility into what other technicians are working on, and they cannot access the full crew view or any other tech's assignments. The full cross-crew view belongs to the admin. That separation keeps the technician's app focused on the work directly in front of them, which makes it faster to use in the field. Admins see everything across all routes and all technicians. Technicians see only their own work. That is the division of access, and it applies consistently regardless of how many technicians are on your account. That keeps each technician moving quickly through their own stops without the distraction of information that is not theirs to act on, while the owner keeps the complete picture.

Add the tech from the admin dashboard and send them an invite. They receive the invitation, set their own password, and log in on their phone. Once they are in, they immediately start seeing the routes you assign them - there is no manual setup required on their end beyond creating their account. The whole process is designed to be fast, because in practice you are often adding someone right as they are starting work. Every paid plan includes unlimited users, so adding a technician does not require upgrading your plan or any additional cost. After a tech is added and has their account, you assign routes to them from the dashboard, and those assignments appear on their phone right away. From that point, they operate from the app in the field and you see their progress from the admin side. In practice that means you can onboard a new hire the same morning they start, hand them a phone, and have them running assigned stops without any office setup beyond the invite.

Yes. Deactivate the tech from the dashboard to remove their access. Once deactivated, they cannot log in and they no longer have any access to routes, stops, or customer information. The service history they logged while they were active stays exactly where it is - every completed visit, every set of chemical readings, and every timestamp remains in your records. Your history does not depend on the technician's account staying active. This matters because the visit log is also your documentation of service to customers, and that record needs to be intact regardless of staff changes. Deactivating a tech is also reversible if someone returns or if you made a mistake, but their historical data is preserved either way. Removing their access is a single action from the admin dashboard. That combination - cut access immediately, keep the history permanently - is what protects both your accounts and your documentation when someone moves on.