Skip to content
farmsorted
On demandAct with approvalThe everyday

Log the pump service and check the flow came back

A new impeller should bring the flow back. If it doesn’t, the problem is somewhere else, like the suction, a foot valve or the channel, and you only find out when a block falls behind.

The Pump and channel watcher logs the service against the river pump with its hours and parts, pulls the flow meter’s readings from before it and checks the first run after to see the flow came back.

When · On demand
“[mechanic] did the river pump today. New impeller and bearings, hour meter 3,140.”
You get
Service on the river pump’s record with hours and parts; flow before and after from the meter; a flag if it didn’t come back
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
Irrigated cropsOrchards and vinesDairy

What it reads

  • Machinery services: river pump, last service at 520 hours
  • Monitoring: river pump flow meter, start of season and the last fortnight
  • Faults noted on the river pump this season
  • The mechanic’s text or invoice

What you get

  • The service logged on the river pump at 3,140 hours, with the parts
  • Flow at the start of the season and just before the service, from the flow meter
  • Flow on the first run after, with a flag if it’s not back
  • The hours at the next service

When it stops and asks you

  • The hour meter reading is lower than the last one logged
  • The flow meter had gaps around the service
  • Flow after the service is no better

How often

Each pump service, a few times a year

Who uses it

OwnersManagers

What it uses

Live

SMS and voice notes

Text the team, send a voice note or a photo, or forward a message. There’s no new app to learn.

Nothing official leaves the farm without your yes.This job runs at Act with approval: prepares it fully. You tap yes. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Pump and channel watcher

Started 7:12am · On demand

Start to done
3 min
Agent actions
4
Needed you
2×
[AGENT NAME]For the Pump and channel watcher

[mechanic] did the river pump today. New impeller and bearings, hour meter 3,140.

You · 7:12am

Pump and channel watcher

Pulled the river pump’s service history and flow

Log the service on the river pump at 3,140 hours: new impeller and bearings, [mechanic], today? Before it, the flow meter had it down to 74 L/s from 92 at the start of the season. I’ll check it on the next run.

[AGENT NAME] · 7:12am

Approved

Yep, log it.

You · 7:14am

Pump and channel watcher

Logged the service

Pump and channel watcher

Checked the flow on the first run after the service

First run since the service: 90 L/s over 10 hours, near enough back to where it started the season. The impeller was the problem.

[AGENT NAME] · 7:14am

Done · 7:15am4 saved

  • The service logged on the river pump at 3,140 hours, with the partsSaved
  • Flow at the start of the season and just before the service, from the flow meterSaved
  • Flow on the first run after, with a flag if it’s not backSaved
  • The hours at the next serviceSaved

Behind the scenes

  1. 7:12am

    You ask

    “[mechanic] did the river pump today. New impeller and bearings, hour meter 3,140.”

  2. 7:12am+10 sec

    Pump and channel watcher works on it · 2 steps

    Pulled the river pump’s service history and flow

    • records.searchriver pump last serviced at 520 hours, [date]
    • sensors.read_waterriver pump flow meter, 92 L/s at the start of the season, 74 L/s average over the last fortnight
  3. 7:12am+2 sec

    [AGENT NAME] asks for your yes

    “Log the service on the river pump at 3,140 hours: new impeller and bearings, [mechanic], today? Before it, the flow meter had it down to 74 L/s from 92 at the start of the season. I’ll check it on the next run.”

  4. 7:14am+3 min

    You approve

    “Yep, log it.”

  5. 7:14am+7 sec

    Pump and channel watcher works on it · 1 step

    Logged the service

    • records.log_serviceriver pump, 3,140 h, impeller and bearings, [mechanic], [date]
  6. 7:14am+7 sec

    Pump and channel watcher works on it · 1 step

    Checked the flow on the first run after the service

    • sensors.read_waterriver pump 90 L/s over a 10 hour run, [date]
  7. 7:14am+2 sec

    [AGENT NAME] messages you

    “First run since the service: 90 L/s over 10 hours, near enough back to where it started the season. The impeller was the problem.”

  8. 7:15am+3 sec

    Pump and channel watcher Done

    Service on the river pump’s record at 3,140 hours; flow back to 90 L/s on the meter; next service due at [hours]

    • memory.rememberRiver pump 90 L/s after the new impeller, [date]

An example with made-up data. Names and figures in [brackets] are placeholders.

The farm software this job works from

Put [AGENT NAME] to work on your farm.

We’re taking a small number of pilot farms in Australia. Start with one or two agents and add more as you go.

Pilot farms wanted

Want to try it out?

Join the pilot, or book a demo and we’ll walk you through this job on a farm like yours. You text the team from your phone. Some connections are still being built, and we’ll tell you which.

  • SMS and voice notes
  • Nothing to install

Free report

Getting started with AI.

A free practical guide for Australian farms and agribusinesses

Where AI actually helps on a farm, what it needs from you, the risks to watch, and a 90-day plan to start small.

  • Where it actually helps
  • What it needs from you
  • Risks and guardrails
  • Working out the return
Book a demoJoin the pilot