Swimming Pool CRM
In the pool business revenue flows at two different speeds: a construction project takes months, while maintenance and chemical resupply repeat every week. When April comes, opening requests all pile up at once, and which estate's contract is still running gets hunted down in the middle of that rush.
Every pool is a separate record; volume, equipment model and installation date are its fields, and service visits and the chemicals used build up under the same card.
- Keep every pool in a separate record with its volume, equipment models and installation date, and link it to the estate or hotel account
- Hold the scope and end date of annual maintenance contracts as fields and run approaching renewals from a single list
- Plan season opening, periodic maintenance and chemical resupply as tasks; see that the technician has reached the site through location verification
- Move the construction process of survey, quote and revisions along on a single opportunity record, and tie the breakdown call to the pool record
| Pool Record | Every pool is a separate record; the volume, the equipment model, the installation date and the linked account are in its fields, and the whole service history builds up under this record. |
|---|---|
| Seasonal Pool Agreement | The season agreement tied to the estate or hotel account is a record; whether opening and closing jobs fall within scope, the visit frequency and the season end date are in its fields; those nearing their end drop into the renewal list. |
| Service Visit | Maintenance and season opening are each a task; the technician, the date and the pool are in fields, the job is closed from the mobile app, the location is verified, and the customer signs on the signature screen in the mobile app. |
| Chemicals and Readings | The chemical used and the reading taken are lines on the visit record; the same pool's past values are compared from the record. |
In a firm that builds and maintains pools, two jobs run intertwined. One is the project: a survey is done, measurements are taken, a quote is prepared, revisions come in, and permits and ground conditions delay the work. The other is service: every pool has its pump, its filter and its dosing system; it needs opening at the start of the season, maintenance and chemical resupply through the season, and closing at the end. Estate managements and hotels work on annual contracts, while an individual customer only calls when something breaks. When these two flows are kept in separate ledgers, April turns into a pile-up: which pool's contract was renewed, which one had which pump fitted last season, which technician went where that day — all of it is asked on the same morning and the answers are gathered over the phone.
In Rapitek CRM every pool is its own record; its volume, equipment models, installation date and the estate or hotel account it belongs to sit in fields. The maintenance contract is tied to the account; because the scope, the visit frequency and the end date are fields, approaching renewals drop into a list. Season opening and periodic maintenance are each a task; the technician closes the job on site from the mobile app, their location is verified, the chemical used and the reading taken are written to the same visit record, and the customer signs on the signature screen in the mobile app. On the construction side, the survey, the quote and the revisions move along on a single opportunity record; and because a breakdown call is a request tied to the pool record, the history of the same equipment builds up in one place.
The scope of the plans and the separately priced items are written on the pricing page.
