Pool Service Software

Pool service dispatch may involve routine visits, equipment concerns, seasonal work, and property manager requests. An office might receive a call about a cloudy spa at a home, a pump noise at a community pool, and a scheduled filter cleaning on the same morning. Staff can preserve what each customer reported without presenting an early symptom as a diagnosis or chemical recommendation. Customer intake is a starting point. Water testing, electrical safety, and equipment repairs remain business responsibilities.

Staff create customer records and job entries, separately select the required service location, carefully document the reported scope, and choose relevant notes. Dispatchers then make scheduling, technician assignment, rescheduling, and geographic choices based on their own knowledge and business procedures. Authorized team members can later record job status and completion context based on communication from the field. These are records rather than automated findings. The Roll On Call overview outlines the broader dispatch environment.

Texts to technicians and customers go out from your business number on Team and Pro, which include integrated phone and SMS with one included number. Solo does not include integrated phone or SMS, so a Solo owner works from the job record and calls or texts from their own phone.

Residential homeowners, commercial facilities, and property management companies bring different communication and recordkeeping needs. A homeowner may request service at the house where they live, while a landlord may coordinate care for a distant rental property. A commercial contact might speak for one community pool, and a property manager might report requests for several neighborhood facilities across a large subdivision. Staff create the customer record and enter the specific contact details supplied to the business. They also decide which person should be contacted under the company's own authorization, privacy, and communication procedures.

A customer record provides relationship context, while jobs and separately selected service locations describe individual requests. Staff can keep customer details distinct from property access instructions and current job scope. The business confirms those matters through its own procedures. The field service CRM overview explains how customer context can accompany dispatch records.

One customer record may relate to several physical properties. A property manager might request filter maintenance at a community pool on one street and an equipment visit at a clubhouse spa on another. A residential customer may call about a primary home and later report an issue at a vacation property. Location selection remains an active staff choice.

Staff confirm the address and customer relationship through company procedures before selecting it. Dispatchers can consider selected locations when making their own geographic and schedule choices, but the map context is not a route planning or optimization tool. The multi-location management page provides more context about keeping customer identities and physical worksite records distinct.

Pool service often requires specific access information to reach backyards, community enclosures, or restricted equipment rooms. Customers may report details that affect a visit, including a combination lock code, a specific gate, parking instructions, an on-site contact requirement, free-roaming pets, or an area where work is restricted. Staff can enter these details as notes associated with the relevant record. A dispatcher then chooses which notes or instructions to include for a particular job. Selection matters because a property note may not apply to every visit, and an older instruction might need verification before reuse.

Notes reproduce information selected by staff. They do not verify that a gate code works, parking is permitted, a contact will be present, a pet is secured, or a restricted area is marked. Sensitive or critical instructions may call for direct confirmation rather than reliance on an earlier record. Staff can update the notes when a customer reports changed conditions.

One-off requests can include heater malfunctions, pump noise, leak investigations, storm debris removal, seasonal openings, or a broader system inquiry. Intake staff create a job, select the service location, and record exactly what the customer reported. They can add notes about access, the relevant equipment area, a contact at the property, or timing requested by the caller. Neutral attribution is highly useful for office communication.

A record can state that the customer reported a leaking pump rather than presenting that report as an assessment of a plumbing seal. The business handles inspection, feasibility, electrical safety, pricing, and approval. Staff can create and schedule a repair visit while keeping its scope attributed to the customer. Related administrative uses appear on the solutions overview.

Recurring weekly cleaning, chemical balancing, and seasonal maintenance work require active decisions by the pool service business. The company decides what an agreement requires, whether another visit should be created, who may perform it, and when it fits the seasonal workload. Staff can use Roll On Call to create the customer and job records that represent those decisions. They select each service location, choose a schedule, assign a technician, and revise the record when plans change.

Staff review the calendar and customer communication through their own processes. If weather or another issue affects a plan, people decide whether and how to reschedule. The customer management section explains related record practices. Recurring agreements, customer notices, and missed-visit follow-up remain business responsibilities outside the dispatch board.

Routine service may produce chemical readings, water condition notes, equipment observations, and other service notes. Staff can enter selected details as job notes based on customer or field communication. A note can distinguish a customer report about algae from an observation.

The business decides who may make technical findings, how chemicals are handled, and what records its work requires. Neutral attribution keeps a recorded reading or observation from being presented as an automated prescription. Safety, chemistry, dosing, diagnosis, licensing, and compliance remain business responsibilities.

Rain, wind, temperature changes, and storms can affect pool service plans. Customers may report leaves, high water, or frozen pipes. Staff can create a job, select its location, preserve the reported scope, and add relevant access or contact notes. Dispatchers review those records under company procedures.

People decide which jobs to schedule, assign, defer, or reschedule based on conditions they assess outside the product. Weather review, site assessment, safe access, equipment decisions, and follow-up remain business responsibilities.

Dispatchers can review jobs and their selected service locations, including location context shown on the dashboard map. They apply their own knowledge of the service area, route density, seasonal workload, customer commitments, travel considerations, and constraints. A person chooses the schedule and technician assignment for each job. If circumstances change, a person also decides whether to move the job, change the technician, contact the customer, or take another action. Geographic awareness serves as context for the dispatcher, not as an automated routing engine.

They also do not confirm that a technician can reach or complete a pool service job within a particular period. Dispatch remains a human decision informed by sources and procedures outside the platform as needed. The dispatch management overview explains how recorded locations, schedules, and assignments fit into this staff-led process.

Managers consider availability, qualifications, safety, equipment, and authorized scope through company procedures. A dispatcher then records the selected technician assignment. The entry reflects a person's choice, not a recommendation that a worker is suitable.

If availability changes, staff review the situation and update the assignment or schedule manually.

An authorized user can send a job brief containing job context chosen by staff. That context may include the selected service location, reported scope, and notes or instructions such as a backyard access point, gate code, parking direction, property contact, pet warning, or restricted area. Staff decide what is relevant and appropriate to include. They should follow company privacy and communication procedures when handling sensitive access details.

The business decides when direct voice contact or confirmation is necessary, especially for schedule changes, urgent equipment issues, or safety information. The technician communication overview discusses standard briefs as one part of staff-led coordination rather than a substitute for company communication procedures or guaranteed field acknowledgment.

A repair or other customer request may involve more than one visit. Staff can create distinct job records for those visits. For each one, a person selects the service location, chooses a schedule, records reported or selected service context, and assigns a technician. Staff decide how the records relate and what context belongs with each visit.

Staff create, schedule, assign, and reschedule each record when the business decides to proceed. They can also create a follow-up job when further work is needed. Agreements, approvals, material and site readiness, and follow-up decisions stay with the business. The field workforce management page provides more context for scheduling across separate jobs.

Staff can review prior jobs associated with a customer and selected service location. Earlier records may show reported scope, the schedule and technician that staff selected, access notes chosen for a visit, status, or completion context. That history can inform questions during intake. For example, staff might ask whether a previously reported gate issue, dog instruction, parking limitation, or restricted patio area still applies. History remains a collection of earlier human entries, not verified current property information.

Staff confirm important details through the business's normal communication and site procedures, then update or select notes for the new job. Office staff must treat past information as a reference point that requires fresh validation from the customer or the assigned technician.

Authorized team members can record a job status based on information available to the team. They can also enter textual completion context reported through field communication. If a technician reports unfinished work or the need for a follow-up repair visit, office staff can preserve that context and decide what action to take. Scheduling or rescheduling remains a staff choice rather than an automatic response to the entry. Status and completion context are human-recorded administrative information.

The pool service business handles field supervision, review, customer communication, and any follow-up. See the job management overview for more about job records and human-entered updates across the dispatch workflow.

When the visit is done, the office or the crew lead turns the job into an invoice. The customer, service address and line items come straight from the job, so nobody retypes them.

Customers can pay the invoice by card through Stripe, and the job shows whether it is sent, paid or overdue. The office sees which finished work is still open without checking a separate spreadsheet.

Roll On Call covers invoicing and collection for the work itself. Bookkeeping, payroll and tax stay in the accounting software the business already uses.

Staff can preserve reported scope and service notes. The business handles estimates, pricing, authorization, and procurement outside the product.

Qualified staff determine requirements and handle purchasing, inventory, and chemical ordering through the business's own procedures.

Roll On Call's pool service use is centered on records and deliberate staff actions. Staff create customer and job records, separately select service locations, preserve reported scope, and choose notes or instructions relevant to a visit. People make schedule, technician assignment, rescheduling, and geographic decisions.

Teams considering adjacent use cases can visit the industries directory, the landscaping page, the plumbing dispatch guide, or the field service management software overview.