Software that runs the route and everything the route creates.
Every stop your team completes creates paperwork: a service record, a customer question, a repair to quote, an invoice to send, and a payment to chase. POOLIO connects those pieces so the work you already do turns into billed, documented, answered work without a second system.
- Weekly routes with stop order and proof of service
- Service logs with chemistry, dosages, and photos
- Estimates, approvals, and repair work orders
- Invoices, card payment links, and autopay
The operating loop
From the stop to the deposit, in one thread
POOLIO is organized around the sequence a pool company actually works in, not around modules that never talk to each other.
- Step 1
Plan the week
Build recurring routes by day and tech, set stop order, and lock stops that must not move. Skips and delays are recorded with a reason instead of disappearing.
- Step 2
Document the stop
Techs complete a checklist per body of water, log chemistry and dosages, attach photos, and flag issues. The record is what you send the customer and what you defend later.
- Step 3
Answer the customer
Inbound texts land in a shared inbox tied to the customer record, with the service history right there. AI drafts a reply; you decide whether it sends automatically or after approval.
- Step 4
Quote and approve repairs
Turn a field issue into an estimate, send it for a tokenized approval with signature, and convert the approval into a scheduled work order with parts and labor.
- Step 5
Bill and collect
Monthly service bills from the recurring plan; completed repair work bills from captured labor and parts. Autopay charges saved cards; unpaid invoices enter a follow-up loop.
- Step 6
Catch what slipped
Missed-money workflows surface requested work that was never quoted, completed work never invoiced, and invoices that aged past your threshold.
Operational outcomes
What changes in the office
Fewer unbilled jobs
Completed work orders with captured labor and parts appear in a completed-not-billed queue instead of living in a tech's memory.
Faster answers
Customer texts arrive with the service history attached, so a reply takes seconds instead of a phone call to the tech.
Documented service
Every visit has chemistry, photos, and a timestamp, which settles disputes about whether and when a pool was serviced.
POOLIO organizes the work and the follow-up. Results depend on your pricing, your route, and how your team uses the system — POOLIO does not guarantee revenue outcomes.
Who it is for
Built for pool companies, not generic field service
Route-based service companies
Weekly and biweekly cleaning routes with per-body-of-water checklists, chemistry targets, and dosage logging — not a generic job list.
Repair-heavy operations
Estimate-to-invoice pipeline with change orders, parts tracking, and approvals that hold up when a customer disputes scope.
Owners still doing the office work
Assisted replies, billing follow-up, and missed-money alerts absorb the office work an owner does at 9pm.
Growing teams
Dispatch, tech capacity, and role-scoped access so technicians see operational data only, and owners keep the financial view.
Buyer checklist
Questions worth asking any pool software vendor
These are the questions that separate software that fits a pool route from software that was written for another trade.
- Does a customer record support multiple properties and multiple bodies of water?
- Can a tech complete a stop without signal, and does it sync later?
- Is monthly service billing separate from approved extra work?
- Are customer text consent and opt-outs recorded per customer?
- Can approved repairs become scheduled work orders without re-entry?
- Does the system show completed work that was never invoiced?
FAQ
Frequently asked questions
What does POOLIO replace for a pool service company?
POOLIO is one system for the route, the service record, and the money that follows it: weekly routes and stops, service logs with chemistry and photos, scheduling and dispatch, estimates and repair work orders, invoices with card payment links, autopay for recurring service, past-due follow-up, and customer texting from a company number. Companies typically consolidate a route app, a spreadsheet, a texting thread, and a separate invoicing tool into it.
Do techs need a separate app?
No. Techs sign in to POOLIO on their phone and see only their own day: their stops, the checklist for each body of water, chemistry entry, photos, notes, and any work orders assigned to them. The technician view is offline-capable, so a stop completed in a dead zone queues locally and syncs when signal returns.
Does POOLIO handle both recurring service and repair work?
Yes, and it keeps them separate on purpose. Monthly service billing runs off a recurring service plan, while repairs flow through estimate to approval to work order to invoice. Approved extra work never silently merges into the monthly service charge.
How does POOLIO take payments?
Payments run through Stripe. Customers pay from a tokenized invoice link with a card, and customers on a recurring plan can enroll in autopay with a saved payment method that is charged when the monthly service invoice is generated.
Can I import my existing customer list?
Yes. POOLIO includes a guided import flow for customers, properties, and route assignments from CSV, plus an onboarding wizard that walks through company profile, team setup, imports, and readiness checks before you go live.
Keep reading
Related pages
See POOLIO run your route
Book a walkthrough and we will set it up against a real day on your route — your stops, your service plan, your billing.