Pool service software for Arizona pool companies

Arizona has some of the highest residential pool density in the country - the Phoenix metro alone has more than 300,000 residential pools. Most routes run year-round because pool season never fully ends in a desert climate, though the chemistry demands shift dramatically between the brutal May-to-September stretch and the milder winter months.

For an Arizona pool company, that means a route that runs 52 weeks a year, chemistry that moves fast in the summer and more slowly in the winter, and a spread-out metro where route efficiency makes a real difference in how many accounts you can serve in a day.

The biggest challenge in Arizona is what the desert sun does to chlorine and cyanuric acid. Intense UV burns off free chlorine fast in the summer months. CYA climbs over the season as you add stabilized chlorine. When CYA gets too high, chlorine stops working effectively - and in a Phoenix summer, that's when algae wins.

PoolBoss logs the full reading set at each visit: free chlorine, combined chlorine, pH, total alkalinity, calcium hardness, and cyanuric acid. Each reading saves to that pool's history, so you can watch CYA build on specific accounts over the season and catch the ones trending toward the point where chlorination stops being effective. The chemical record is per-pool, not averaged across your route.

Arizona's monsoon season (July through September) adds a different challenge: heavy dust loads, debris, and rain events that dilute chemistry and drop pH. After a dust storm, pools that were in range need re-treatment. After a significant rain event, the readings shift.

Every post-monsoon visit has its own reading record and notes field. When a customer asks why the pool required extra treatment after the storm system in August, the visit record has the before and after readings, the notes you added, and the date. That documentation protects you and gives the customer something concrete.

Phoenix metro sprawl means stops can be far apart if the route isn't organized. PoolBoss keeps your stops in the order you set them - you optimize the drive once, and that's the order the route runs until you change it. If you have three techs on three different parts of the metro, each one sees only their own route in the mobile app.

When coverage changes - a tech is out, you add a new cluster of accounts on the west side - you adjust in the dashboard and the change shows up in the tech's app immediately. No paper sheet, no text chain to communicate the update.

Arizona field techs work in conditions that make anything fiddly impractical. The PoolBoss mobile app is designed to be fast in the field: today's ordered stops, pool specs and last readings visible before you start, a chemical form that captures the full reading in one pass, and a mark-complete that puts the visit in the record.

When a tech finishes the route, the admin can see every completed visit and reading from the web dashboard without calling anyone. If a pool was flagged with a note, it's visible. If a stop was skipped, that's visible too.

At the end of the week, you create invoices from the visits your techs logged and send them with an online payment link. Customers pay by card from their inbox. No separate invoicing app, no double-entry from field notes.

For Arizona companies running a year-round route, consistent invoicing matters. Slow billing means slow payment; professional invoices with an easy payment path get paid faster.

The Free plan covers your first 20 Arizona accounts at no cost, no trial expiration, and every feature included: routes, chemical tracking, invoicing, and the mobile app. When you pass 20, you move to Startup at $29. The pricing is the same for an Arizona operator as it is anywhere else in the country.