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 a Free 30-Minute Demo →

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

IN USE ATOrange Cove Irrigation District

Full-time phone operations and phone orders.

Lacy captures a grower's water request and prepares the details for irrigation district staff review.

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

Explore the Orange Cove customer story →

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.

A complete request for staff review

A grower requests water; Lacy captures caller details, delivery point and requested timing for district review.
02

Service requests

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

Useful context for the right team

Lacy captures the location and details of an irrigation gate issue for district staff.
03

After-hours calls

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

A clear next step after the office closes

Lacy saves an after-hours irrigation request and follows configured on-call routing.
Lacy confirms a Spanish-speaking grower’s request details for district staff.

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 prepares a water request for district staff review and communicates the configured status.

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 a Free 30-Minute Demo →

HOW THE HANDOFF WORKS

A caller asks for water.
Your district gets a clear request.

Lacy captures the call and prepares the next step. Your district keeps control of review, acceptance and scheduling.

  1. 01
    THE CALLER → LACY

    Capture the request.

    Lacy asks for the caller, delivery point, timing and district-required units, then reads back the details.

    Example caller
    “I need water at delivery point T-07 tomorrow morning.”
    Caller + location + requested timing
  2. 02
    LACY → DISTRICT STAFF

    Prepare it for review.

    The request goes to the responsible team through your configured handoff. Staff can see the details and any missing information.

    Staff receive
    Request
    Water order
    Delivery point
    T-07
    Status
    Awaiting district review
  3. 03
    YOUR DISTRICT → NEXT STEP

    Keep the status clear.

    Your district decides acceptance and scheduling. Lacy communicates the approved status and updates connected records as configured.

    The caller knows
    “Your request has been received for district review.”
    Received does not mean approved.

Example only. The delivery point and request are fictional. Your district defines the required fields, handoffs and caller messages.

Your district remains in control.

A captured request is not an accepted order or a promise of water delivery. If a system update fails, the saved intake stays available for review.

View the detailed 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 a Free 30-Minute Demo →