Show your customers the pool got serviced, every time

Send the service report from the visit. It lists the chemical readings taken and the tech's notes with a timestamp, so the customer sees exactly what was done instead of taking your word for it. That single document answers the question before the customer thinks to ask it - no follow-up call, no back-and-forth, just a record that shows up in their inbox after the tech leaves. PoolBoss builds the report automatically from what the tech logged during the visit, so nothing falls through the cracks because someone forgot to write it up. If a dispute ever comes up later - a customer saying the pool was neglected or the water was off - the timestamped visit history with readings and notes is already on file. You are not relying on memory or a paper logbook. The proof is attached to the visit that created it, stored per pool, and available any time you need to pull it up. Customers who receive reports consistently tend to ask fewer questions and raise fewer complaints, because the work is visible. That is the practical value of the report: it makes the service something the customer can see, not just something they have to trust.

The visit date and time, the chemical readings taken, what the tech did and noted, and ideally a photo. PoolBoss builds the report from the readings and notes logged during the visit, so the content comes directly from what happened rather than being written up separately after the fact. A complete report gives the customer the full picture: when the tech was there, what the water looked like when they arrived, what was done to bring it into balance, and what it looked like when they left. The before-and-after reading option lets you show both sets of numbers in a single report, so the customer is not just seeing a snapshot - they are seeing the change the visit produced. Photos add another layer. Techs can capture images during a visit, and PoolBoss does not cap how many. A photo of cloudy water on arrival and clear water at the end tells the story more plainly than any written note. The combination of readings, notes, timestamps, and photos turns the report into a record that is useful both for the customer relationship and for your own file if the work is ever questioned.

When a tech completes a visit, PoolBoss assembles the report from the logged readings and notes so you can send it to the customer by email. The proof goes out tied to the visit it documents, which means the customer receives the record while the visit is still fresh rather than getting a generic summary at the end of the week or month. The report is built from what the tech actually logged - the chemical readings, the notes, the timestamp - so you are not relying on anyone to write something up separately. The tech does their job, marks the visit complete, and the report is ready to go. Sending it consistently after each visit is the habit that pool service owners most often credit for reducing customer questions. When the customer knows a report is coming, they look for it instead of sending a message asking if anyone came by. Over time, that pattern builds a kind of quiet trust: the customer sees the work, sees the readings, sees the water improving or staying balanced, and the service relationship stops being a source of friction. The report does that work without adding a separate administrative step for you or your techs.

Keep a timestamped record of the readings and work for each visit. PoolBoss stores that per pool, so if a customer claims the pool was neglected, you have the chemical history and visit notes to show otherwise. Every completed visit produces a record tied to that specific pool: the date and time the tech was there, the readings logged, and any notes they left. That history accumulates over time, so you are not looking for a single report - you are looking at a timeline of what the water looked like at each visit and what was done. If a customer disputes that service was performed, or claims the water was consistently off, the logged visit history is what you point to. The readings are not self-reported summaries; they are the actual numbers the tech entered during the visit, attached to a timestamp. That is a different kind of documentation than a handwritten log or a spreadsheet that could be edited after the fact. Having that record on file also changes the nature of customer conversations when something goes wrong. Instead of a dispute about what happened, you have the data from the visit in question. That shifts the conversation from he-said-she-said to a documented timeline, which is a much stronger position to be in.

Yes, though the proof does most of its work before the bill arrives, not stapled to it. Each visit sends the customer a service report with the readings, the notes, and the timestamp, so over a month of weekly or biweekly service they have already seen the work several times. By billing day the question behind most slow payments - did the service happen, was the pool cared for - is already answered. The invoice then itemizes the visits it covers, so the charge lines up with reports the customer recognizes, and for accounts that want it consolidated a monthly statement puts the period's visits and the invoice on one page. The customers most likely to slow-pay or dispute an invoice are the ones who did not see the work happen and are not sure what they are paying for. Steady per-visit proof plus an invoice that names its visits removes that friction. It is not a guarantee of immediate payment in every case, but a customer who has already seen the service is a customer who approves the bill without a back-and-forth.

Techs can capture photos during a visit, and PoolBoss does not cap how many. Photos plus readings make the report a clear record of the visit. A photo shows what the tech saw when they arrived and what the water looked like when they left, in a way that a set of numbers alone cannot. Customers who are not familiar with pool chemistry may not immediately know what a free chlorine reading of 0.5 means, but a photo of murky green water followed by a photo of clear blue water communicates the same thing without any translation needed. Photos also serve a documentation function. If there is ever a question about equipment condition, visible algae, or something the tech flagged but did not have time to address, a photo from that visit is a record that speaks for itself. The tech does not need to write a detailed description - they take the photo, it attaches to the visit, and it shows up in the report. Because there is no cap on photo count, a tech can document as thoroughly as the job requires. A straightforward maintenance visit might warrant one or two photos. A visit where they found the pool in bad shape and brought it back might warrant several. The report holds all of it.

Yes. A tech can log the water as found and as left, so the report shows both. The customer sees the before-and-after instead of a single set of numbers, which makes the value of the visit clear. A service visit changes the water - that is the whole point - and the before-and-after format lets the report show that change explicitly. A customer looking at a report that shows chlorine at 0.4 on arrival and 2.8 at departure, with pH brought from 8.0 down to 7.4, is looking at the outcome of the visit in plain terms. They do not need to know what those numbers mean in the abstract. They can see that the tech found the water off and left it balanced. That is what a pool service company is selling, and the before-and-after report makes it visible. Techs log the as-found reading when they arrive, do the work, and log the as-left reading before they go. The report presents both together. This also creates a more useful record for your own reference. When you look back at a pool's history and see that the water is consistently arriving off in the same way, that is information about the pool's conditions between visits - information that affects how you service it going forward.

Yes. A tech can tap to mark they're on the way and PoolBoss emails the customer, which cuts down on the "when are you coming" messages and makes the service feel professional. For a customer who is home or wants to make sure the gate is unlocked, knowing the tech is fifteen minutes out is genuinely useful. For the service company, sending that notification automatically - from a single tap in the app - removes the back-and-forth that takes up time throughout the day. The "when are you coming" message is one of the most common friction points between pool service companies and their customers, especially on routes that run longer or shorter than expected. The on-the-way notification does not eliminate every variation in schedule, but it means the customer has current information instead of waiting and wondering. It also changes how the service is perceived. A one-person shop that sends a heads-up notification looks like an operation with a dispatcher and a scheduling system, not someone working from a paper list. That professional impression is built into the workflow at the cost of a single tap from the tech, with no separate communication step required from the office.

Yes. Service reports are included on every plan, including Free. The only difference between plans is how many pools you manage. The Free plan covers up to 20 pools with one admin account. Startup at $29 a month covers up to 100 pools with unlimited users. Pro at $79 a month covers up to 250 pools with unlimited users. Fleet at $249 a month is uncapped - no pool ceiling. Every feature in PoolBoss, including service reports, the before-and-after reading format, photo capture, and the on-the-way customer notification, is available on all four plans. There is no version of the software where service reports are locked to a higher tier. The decision to move to a paid plan is driven entirely by how many pools you are managing, not by which features you need access to. A company on the Free plan using PoolBoss to manage 15 pools has the same service report capabilities as a company on the Fleet plan managing several hundred. If your pool count grows past your plan's ceiling, the upgrade prompt will appear before you hit the limit so the transition is not disruptive.