Which zone, and what it is doing — in either language.
An irrigation call carries two facts and everything depends on the second one. The first is easy — a zone number is a number, and it survives any language. The second is not: not coming on at all, coming on and never shutting off, running at a trickle, or throwing water across the sidewalk are four different visits, and in a second language they collapse into "the sprinkler is not working right". That collapse is the difference between a valve on the truck and a return trip.
The symptom is the whole diagnosis
A zone that will not start points at a wire, a solenoid or the controller. A zone that will not stop points somewhere else entirely, and it is also the one wasting water by the hour. A caller who cannot find the words for the difference gives you the least useful version of a call they were trying to be helpful on.
The same questions, either language, one written record
Neuron follows whichever language the caller opens in and asks what the system is doing: which zone, whether it starts, whether it stops, what the water looks like where it comes out, and what the controller is showing. It also asks the compliance question plainly — whether they are calling about a backflow test that is due — because almost nobody volunteers that in any language. What comes back is one note against the property, in a form you can read.
Nothing is diagnosed on the call
The call is captured, not solved. No cause is named and no repair is priced over the phone, so nobody is told a valve is the problem before anybody has opened the box. If the caller could not describe the symptom clearly, it arrives marked unclear instead of tidied into a certainty you would have driven out on.
Bilingual answering — FAQ
Which languages does it answer in?
English and Spanish, following whichever the caller starts in — no menu, no asking them to pick first.
Most callers do not know irrigation terms in either language. Is that a problem?
No — the questions are about what the system is visibly doing, not about part names, which is what decides the visit anyway.
Will it catch a backflow certification call?
It asks whether the call is about a test that is due, so a compliance deadline is not filed as a general repair request.
What if the caller switches languages mid-explanation?
It follows the caller rather than pulling them back, which is how most bilingual households actually explain a problem.