Identify equipment from a photo
Photograph the pad and the AI reads the pump, filter, heater and salt cell — make, model and serial where it can see them. It lands in a review queue so a person confirms before it becomes the pool's record.
Photograph the pad and the AI reads the pump, filter, heater and salt cell — make, model and serial where it can see them. It lands in a review queue so a person confirms before it becomes the pool's record.
Hold the strip to the camera and the readings come back filled in — free chlorine, pH, alkalinity, hardness, cyanuric acid. The tech confirms or corrects. No squinting at a colour chart, no typing seven numbers.
The AI recognises the filter type from the photo and logs the clean against a cadence you set. When it's due for replacement, one tap emails the owner a quote with an approval link.
The report writes itself from what was actually logged: readings, tasks completed, chemicals added, and the photos. You approve; the customer gets it before the truck leaves the driveway.
Plain-language questions against your own data — which customers are unbilled, whose pool is trending high, what a route earned last month. Answers cite the records they came from.
Type an inquiry address and Lucci says which tech, which day and which point in the route it belongs to, based on the drive you already run — before you quote the job.
The AI will never state a chemical dose. It reports what was measured and what your technician recorded.
A route belongs to a technician, not to a day of the week. Change who runs Tuesday and the whole day moves with them.
Half the pools in this business sit behind a house with one bar of signal. Every write is saved on the phone first and synced when the network comes back.
Photos, GPS and timestamps attach themselves to the visit, so a disputed service call is answered in seconds rather than argued.
Generate a month of invoices in one pass, priced on the visits actually scheduled — a customer who started mid-month pays for the visits they got.
The most common reason a pool customer cancels is silence. Lucci closes that gap automatically.
Roles are enforced in the database, not hidden in the interface. A tech simply cannot see what a customer is charged or what another tech is paid.
The truck is part of the route. Lucci tracks it alongside the work.
Run Lucci beside your current software with Parallel Run: everything is recorded, nothing is sent, and you reconcile daily until the numbers agree.