PUBLIC WATER & IRRIGATION

AI phone agents for
irrigation &
water districts.

Water-order intake. Service requests. Work moving forward — during business hours and after hours, within your defined process.

Book an irrigation workflow demo Get started

30-minute demo · Bring one routine call and one exception.

IN USE ATOrange Cove Irrigation District

Full-time phone operations and phone orders.

LACY.AI PHONE AGENTSLacy.ai phone assistant mascot
ILLUSTRATIVE CALL

“I’d like to request water
for my delivery point.”

THE CUSTOMER RELATIONSHIP

Real use.
In irrigation.

Orange Cove Irrigation District

Orange Cove Irrigation District in California uses Lacy.ai full time for phone operations and phone orders.

That use case is the starting point for a conversation about your district’s own calls, rules and staff handoffs.

Read the customer brief

BUILT AROUND THE REQUEST

Irrigation calls.
Clear operational next steps.

01

Water-order intake

Define the caller, delivery point, requested timing and district-required units. Give staff the information needed for review.

02

Service requests

Capture the location, issue and callback details. Define the right queue and the point where a person takes over.

03

After-hours calls

Set the routine intake path, approved on-call escalation and fallback when a person cannot be reached.

Lacy.ai multilingual voice support

MULTILINGUAL PHONE SUPPORT

Meet irrigation callers
in their language.

Support conversations in English, Spanish and other configured languages. Keep the required request details, district terminology and next steps consistent.

Confirm supported languages, local terms and human handoff rules during setup. Read back critical details before routing the request. Explore multilingual support →

BEYOND THE CALL

Move the work forward.

A conversation is the starting point. Connect the captured request to the people, records and follow-up your district needs.

  • Route a complete request to the responsible team.
  • Update the agreed system after successful acknowledgement.
  • Send configured confirmations and keep exceptions visible.

System connections and messaging are scoped and tested for your deployment. Explore workflow automation →

Lacy.ai connecting voice conversations with operational workflows

SEE YOUR PROCESS IN ACTION

What happens in your demo?

Walk through water-order intake, an after-hours exception and the next staff handoff. Discuss your systems and the right starting scope.

Book your 30-minute demo ↗

EXPLORE A DISTRICT WORKFLOW

From irrigation phone call
to documented request.

Select a scenario and step through the proposed process. This interactive example uses fictional data. It does not place an order or depict OCID’s configuration.

    WORKFLOW EXAMPLE01 / 07

    Sample Valley Irrigation DistrictFICTIONAL DATA

    District authority stays explicit.

    Request receipt, order acceptance and water delivery are different states. Your authorized process governs availability, allocations and scheduling. Connections and controls are scoped and tested before deployment.

    Download the workflow

    A DEFINED STARTING SCOPE

    Begin with one call type.

    01

    Map the process

    Bring a routine call and an exception. Identify the required fields, rules and staff owner.

    02

    Review the fit

    Assess the proposed handoff, system connections, security evidence and purchasing requirements.

    03

    Test before deployment

    Agree on the scope and acceptance criteria. Test normal requests and the failure paths your team needs.

    FOR YOUR TEAM

    Take the conversation
    into your next meeting.

    Irrigation & water overviewOne-page introduction · PDFOrange Cove customer briefThe confirmed use case · PDFIrrigation request workflowIntake, handoff and review · PDF

    COMMON QUESTIONS

    What your team will want to know.

    Can this work with our current systems?

    We first review your available interfaces, required fields and access rules. Direct updates require technical validation. A staff-reviewed handoff may be the right starting scope.

    Does receiving a request approve a water order?

    No. The proposed workflow distinguishes receipt from acceptance. Your district defines who can accept an order and what status the caller should hear.

    What happens after hours?

    Coverage, on-call routing and unsuccessful-transfer behavior are agreed and tested before deployment. An urgent escalation only counts as acknowledged when the responsible person or process confirms it.

    Can IT and procurement review it first?

    Yes. Bring your evidence and purchasing requirements into the initial discussion. Security controls, data handling, support and commercial terms need review for the actual deployment.

    YOUR DISTRICT. YOUR PROCESS.

    Bring one routine call
    and one exception.

    Let’s work through what your callers need
    and what your staff needs next.

    Book an irrigation workflow demo