Seasonal reminders
Opening, closing and storm follow-ups go out by property, timed from the season and the last visit.
SIZ Group would build a pool maintenance retention app that sends the right reminder at the right time, shares water care tips drawn from real visits and lets clients request repeat service with one tap. The goal is to keep weekly accounts from quietly drifting to a competitor after a green pool turns cloudy.
Most pool maintenance accounts run on a weekly route. A technician tests the water, adds chemicals, skims, brushes and empties baskets, then logs the visit on a paper sheet or a basic field app. The client hears from the company mainly when an invoice arrives, so the relationship stays quiet until something goes wrong.
Drift happens at predictable points. A seasonal closure in winter ends a contract without anyone calling. A green pool after a storm sends a client searching for a new company, and the reviews they find often decide the call. Repeat requests, such as a filter clean or a liner check, tend to stay in a text thread that nobody reads in time.
Each lost account looks small on its own, but across a route the losses add up. Retention work is about making the next visit feel planned, not about discounting the current one.
The first release should cover the reminders and requests that keep a route full. A client receives a note before a seasonal opening, a prompt when a filter clean is due and a message after a storm asking whether the pool needs an extra visit. Each message links to one request button rather than a phone number.
Water care tips come next, kept short and tied to the client's own pool. A note on balancing chemistry in summer heat, or on reading a test strip, reflects what technicians already explain on site. Loyalty rewards, referral programs and a full resident portal can wait until the reminders have proven themselves.
Pool companies often run pool-specific service software next to Jobber for scheduling and QuickBooks for accounting. The retention app should read client and visit data from those systems wherever an interface exists, and it should never ask a technician to type the same visit twice.
Where no clean link exists, the honest answer is a scheduled export, not a promise of live sync. Email and text tools handle the sending. The app decides who receives which message, so the logic lives in one place and the marketing manager can review it.
Opening, closing and storm follow-ups go out by property, timed from the season and the last visit.
A client taps once to ask for a filter clean, a liner check or an extra visit, and the request lands in the office queue.
Tips come from what the technician wrote on the last visit, so the advice matches the pool in front of the client.
Weekly accounts receive a short renewal message before a contract term ends, with the option to change visit days.
A client leaving for a season can pause service with one tap, and reminders restart on the chosen return date.
The office sees reminders sent, requests received and renewals completed for each route, every week.
The biggest cost driver is the number of triggers. Seasonal reminders, visit-based prompts and storm follow-ups each need rules, testing and copy. A basic set of three triggers costs far less than a full engine with segments for every route. A build of this size opens at $4,500; the written scope names which triggers are included.
Timeline depends on the content review cycle as much as on engineering. Water care tips need a technician to check accuracy, and seasonal messages need approval from the operations lead. Plan that review time before the build starts, not after the first send.
To keep scope under control, we would define the first release as a fixed list of triggers and content types. Anything else, such as referral rewards or a client login, becomes a numbered item with its own estimate.
Start with a small group of clients on a single route. Send the first reminders to them only, and read the replies with the office manager. Pool owners notice a generic message quickly, so the first copy should sound like the technician who visits their yard.
Staff need a clear role. Technicians add visit notes in the field, which feed the tips, and office staff review the request queue every morning. If nobody owns that queue, repeat requests will sit unread and the feature will fail quietly.
Once the pilot route runs smoothly, extend the reminders across the book. Post-launch support covers timing changes and any client who reports a reminder arriving at the wrong hour.
Take a baseline before the first reminder goes out, then measure the same figures every month. The numbers that matter are the renewal rate on weekly accounts, the number of seasonal clients who return after a closure and repeat requests converted into booked visits.
Track how many clients open a reminder and how many tap through to a request. High opens with few requests point to weak copy or the wrong offer. Low opens point to timing, or to a message that reads like spam.
Compare the results with the same period last year, adjusted for the start of pool season. Share the summary with the marketing manager and the operations lead together, so retention and route planning work from one set of numbers.
It can help where churn comes from silence, such as a seasonal closure nobody remembers to restart. It will not fix poor service. We would measure renewals and repeat requests before the first reminder, so any effect shows up in your own numbers.
Not if each message names their pool, the service and the next step. Clients can set quiet hours and choose which types of message they receive. We would review the copy with your technicians before anything goes out.
No. We would start with a short set of tips your technicians already give on site, check each one for accuracy, then add new tips as the seasons change. Content tied to real visits is what makes it useful.
It reads the service calendar and the last visit date from your scheduling system, then applies the rules you approve. Each trigger has an owner and a log, so a marketing manager can see why one client received a message and another did not.
Post-launch support covers message changes, new seasonal rules and client questions the team cannot answer from the dashboard. We would also review the route summary with you to decide which triggers to tune first.
Book a free scoping call. We will go through your renewals, seasonal closures and the messages clients already receive, then confirm scope and price in writing.