Pool service software for the route, the chemistry, and the recurring bill — on one record.

01  The pool service data model

Property → Body of Water → Equipment — plus the chemistry log, plus the service plan.

FieldCamp ships a pool layout: the customer record holds the property, and the property holds a Body of Water for each pool and spa. Each Body of Water holds typed equipment records — pump, filter, heater, salt cell, automation panel.

Per-visit chemistry lives on a Chemicals record, the weekly plan on a Service Agreement . The route-led architecture mirrors the pest-control data model — Body of Water reuses the primitive behind Bait Stations — on the same Customer → Job → Visit chain. Open one record and see the pool, the spa, last week's readings, and the plan status — with a purple-accented AI summary card on top.

02  The recurring weekly route

Every pool, every week — auto-generated visits, stacked by neighborhood, not by who called loudest.

Pool is route-led, not call-led. A recurring weekly Job per pool auto-generates Visits on the cadence the homeowner picked at booking time. The Tuesday route is every Wexler-shaped customer on Marco's day, in order.

Behind it sits the Service Agreement with the Active / Lapsed / None status — a workflow watches it, so a lapse triggers a win-back text the same hour. Same playbook the cleaning and lawn routes run, tuned for pool.

03  The mobile checklist

Skim, vacuum, brush, backwash, test, dose, log — on a phone, in the sun, with one hand.

The tech opens the visit on the mobile app, taps the Weekly Pool Service form, and works through the physical tasks, the seven chemistry readings, and the dose. The mic icon on every numeric field is speech-to-text — readings go in without typing.

Each chemical applied is a Chemicals record . Photos auto-attach to the customer file and the visit log , and Finish Work fires a workflow that emails the homeowner a service report with this visit's photos and readings. No LSI dial, no AI-prescribed dose — the tech makes the call, FieldCamp captures what was done.

04  Dispatch & live ETA

AI-routed by skill, by zone, by stops left in the day — the homeowner sees Marco's truck on the way.

Built-in route optimization auto-reorders Marco's 22 Tuesday stops by real drive distance — no add-on, no per-vehicle fee. The AI Dispatcher respects your service-area zones and per-tech hierarchical skills , so the commercial-HOA pool only ever lands on a Certified Pool Operator route.

Capacity rules cap stops per day on Live Dispatch. The moment Marco taps In Transit, an Uber-style live ETA link goes to Sarah — his name, photo, three stops away.

05  Repair & upsell

Salt cell, pump motor, heater — three options on the truck, e-signed before the tech leaves.

Repair is where the pool route earns its margin — the drifting salt cell, the screaming pump motor, the heater that won't fire in October. FieldCamp ships 2–4 options per estimate — repair, replace, upgrade — and Sarah approves one with an e-signature from her phone.

Salt-cell and pump-swap bundles live in the price book as one sell price, the estimate carries line items, markup, and tax, and a deposit can be required at approval. The moment Sarah taps Approve, that option converts to a Job with the parts and the visit time.

06  Seasonal jobs

Different season, different job type — same record as the weekly visit.

A pool service business runs four overlapping calendars — the weekly route, the spring opening run, the fall close run, and green-to-clean recoveries. FieldCamp models each as a Job Type with its own Job Form — Spring Opening, Winterization, Acid Wash, Green-to-Clean Recovery.

Stage gates enforce photo-at-uncover and signature-at-sign-off per phase. The 28-day plaster startup and the 7-day green-to-clean rebalance are multi-visit recurring jobs the Command Center creates from a sentence — and every one lands on the same Wexler record as the weekly Tuesday visit.

07  Get paid

Monthly plan bills on the 1st, chemical line items pass through, the salt-cell invoice tags onto the same customer — one ledger, not two.

The pool trade bills in halves — flat monthly plan, chemical pass-through, the twice-yearly stabilizer surcharge, a repair invoice on top. FieldCamp assembles that from documented primitives: AutoPay on the recurring job charges the default card on the 1st.

Chemicals applied this month become line items on the recurring invoice, and the salt-cell repair flows through job-to-invoice with the deposit already applied . Stripe rails handle the online card — cash and check recorded manually — and one click syncs paid invoices to QuickBooks Online, Xero, or Wave . The recurring-revenue view is a saved analytics dashboard.

08  Win-back & sellable route

When a plan lapses the win-back text drafts itself — and your sellable route is one export away.

Every pool service business is one day for sale, and FieldCamp treats it that way. Service Agreements hold the plan terms and the Active / Lapsed / None status; a workflow watches it, and a lapse drafts the win-back SMS three days later.

Pre-built workflow examples cover the common patterns, and everything a route broker prices — plan history, AutoPay record, the chemistry log, the route map — is already exportable, in their format, on day one.

09  Capabilities

Everything else FieldCamp ships for a pool service company, on one platform.

Built around the recurring weekly route, not bolted on. The capability surface is the same that runs HVAC, pest control, lawn care, and cleaning — labeled in pool vocabulary.

The core records — Customer, Request, Job, Visit, Estimate, Invoice, Payment — carry the full lifecycle, plus two-way text messaging for the homeowner layer. Every tile links to its docs.

10  Why it matters

Where the SERP leaders draw the line — and where FieldCamp keeps going.

Pool service is a head-on FSM competition — buyers compare Skimmer, Pool Brain, GorillaDesk, ServiceTitan, and Jobber on the same query. FieldCamp keeps the three things the leaders each own — chemistry-aware service reports, operational depth, FSM polish — on one platform, at one price.

Migration in one onboarding call; the lead-to-payment lifecycle and Command Center AI chat carry the load — with Property → Body of Water → Equipment underneath.

11  The other trades we run

Same platform. Every recurring-route trade you touch.

Property → Body of Water → Equipment is one shape of the same FieldCamp vertical-agnostic core — every trade below sits on the same typed records, vocabulary flipped. Pool's route-led economics sit closer to lawn, pest, and cleaning than to HVAC's diagnostic-led model.

12  FAQ

Pool service software — answered.

Honest answers to the questions pool service operators ask when comparing FieldCamp to Skimmer, Pool Brain, GorillaDesk, or a wall calendar. If we don't ship something — auto-LSI, live Pentair telemetry, Tap-to-Pay — we say so.