field-service-intake
Irrigation leak calls: collect zone and property facts without unsafe shutoff advice
A practical intake workflow for continuous watering, pooling, broken heads, low pressure, and suspected irrigation leaks.
# Irrigation leak calls: collect zone and property facts without unsafe shutoff advice
*October 2, 2026*
Water running across a sidewalk, a sprinkler that will not stop, and a patch of soggy lawn can all produce the same request: "Send someone for a leak." The dispatch value comes from where the water appears, what it affects, whether a scheduled cycle is active, and how a technician can reach the area.
Reception should record those observations without diagnosing a broken main line or directing a caller to operate an unfamiliar valve. The service dispatcher owns priority and field instructions.
Locate the water on the property
Confirm the service address, account or property name, and callback number. Large sites need a more precise location: building side, courtyard, median, athletic field, parking row, or another recognizable area. If the caller knows the irrigation zone or controller name, record it. Do not require it.
Ask what the caller sees. Is water spraying, bubbling, pooling, or flowing steadily? Is the problem at a visible sprinkler head, valve-box area, landscaped bed, or an unknown underground point? Record the description as an observation, not a technical finding.
Useful fields include:
- exact property area;
- zone or station if known;
- observed flow and when it began;
- whether a scheduled watering cycle appears active;
- controller display or status as reported;
- street, sidewalk, building, or neighboring-property impact;
- recent landscaping, excavation, or service reported by the caller;
- gate, parking, pet, or tenant access constraints;
- onsite contact and available hours.
If the caller cannot safely reach the controller or leak area, mark the detail unknown. A complete ticket is not worth asking someone to cross standing water or enter a restricted space.
Route by impact, not by the caller's diagnosis
A broken head during a normal watering cycle may follow a routine service route. Continuous flow outside the schedule, water entering a building, a flooded pedestrian area, or another company-defined trigger may require urgent review. The call script should list observable conditions that change the route.
Reception should not decide that the main line failed, the controller is defective, or a particular repair will stop the loss. Those are field conclusions. Nor should the receptionist promise water savings or estimate the repair scope.
If the caller reports an immediate hazard or a situation covered by an emergency procedure, follow that procedure first. Keep questions short and avoid holding the caller near the affected area.
Do not improvise shutoff instructions
Callers often ask which valve to close or how to stop a controller. Unless the irrigation company has an approved, site-specific instruction that reception is authorized to read, route the question to the dispatcher. A general instruction can affect domestic water, fire protection, another tenant, or equipment the call handler cannot see.
Use a direct boundary: "I have recorded the active flow and sent it to the service dispatcher. I cannot identify or operate the property's valves by phone." Do not suggest excavation, ask a caller to open a valve box, or tell someone to enter a flooded area.
The EPA WaterSense outdoor water-use resources can help the company's policy owner frame conservation and maintenance information. They are not a diagnosis for a particular property. Reception should use the company's approved intake map rather than browsing general guidance during a live leak call.
Treat pedestrian and building effects as separate facts
An apartment manager reports water crossing a sidewalk from a landscaped area when no scheduled cycle should be running. The receptionist records the location, continuous flow, reported schedule status, start time, and pedestrian impact. The note does not call the problem a main-line break.
The sidewalk condition is visible to dispatch as its own field. That matters because a ticket labeled only "irrigation leak" may not show why the property manager requested urgent attention. If the caller also reports water near a building, record the exact area and what the caller observes without deciding whether water has entered the structure.
Dispatch accepts the ticket, chooses the response, and requests any technical follow-up. The caller receives the current status, not an invented arrival time.
Prepare access for the field visit
Irrigation systems may span common areas, tenant yards, locked equipment rooms, rooftops, or public-facing landscaping. Ask who can admit the technician and when. Record gate hours, parking restrictions, controller location as reported, and whether another contractor is working nearby.
Keep gate codes, alarm details, and private tenant information in the approved secure channel. A general ticket needs the access requirement and contact, not every security detail.
If photos or video help dispatch, use the company's approved upload method. Do not ask the caller to step into water, remove a cover, or approach active equipment to obtain media.
Make ownership and timing visible
The system should record when the leak report was created, which queue received it, and who accepted it. A message sent to a technician is not the same as acknowledgment. If the approved response window expires, the backup route should activate.
Use precise states: submitted, accepted, scheduled, dispatched, and completed. Reception can tell the caller, "Dispatch has accepted the active-leak report," only when the system shows that event. A scheduled visit is not yet a completed repair.
When a field technician later identifies the cause, add that finding. Preserve the caller's original observation and any status statements already given.
Test more than broken sprinkler heads
Training should include a normal-cycle broken head, continuous watering after hours, low pressure with no visible water, pooling near a building, runoff into a street, a locked multi-tenant property, and recent excavation near the reported location. Add a case where the caller insists on remote shutoff advice.
Review whether the call team confirmed the site, located the water, separated observation from diagnosis, captured public or building impact, respected the valve boundary, protected access information, and obtained dispatch acknowledgment.
If technicians repeatedly call back for location or controller details, improve those fields. If reception overuses the urgent route, make the observable criteria easier to see. The form should help the call handler make the administrative distinction without pretending to make the repair decision.
Close with the leak record, not the repair forecast
A useful close reads back the property, affected area, observed flow, impact, and contact number. It names the queue that owns the next step. It does not predict the cause, savings, technician arrival, or final repair.
That gives the property contact a clear handoff and gives dispatch enough context to act. The water problem may still be uncertain, but the service record should not be.
Need a phone workflow for irrigation leaks, controller reports, property access, and dispatch acknowledgment? Contact Virtual Assistant Call Center to discuss your field-service intake process.