Pump trips & pressure faults
Route fault messages from pumps, drives and irrigation controllers to your local operator, then a backup or contractor.
Irrigation, pumps & water
The pump has stopped.
Who’s getting it going?
Keep your irrigation controls. Add a response plan that reaches the operator, follows up when nobody answers and records who is handling the fault.
Illustrative call-out
An overnight pressure fault
Pump 4 reports low pressure. The first operator misses the message. Pinga calls, then moves to the next contact if there is still no acknowledgement.
Choose the contact, notification method and wait time for every step. AI interprets the message; your configured plan controls the response.
- 02:14
Fault received
Pump 4 · low pressure. Its message arrives by SMS, email or webhook.
- 02:15
Next step: call
The operator has not acknowledged. Pinga follows the wait time you configured.
- 02:16
Responsibility accepted
Sam accepts. Remaining escalation stops; the equipment fault stays open until recovery or manual closure.
Practical tools for your team
From a controller message to a clear call-out
Flow & tank-level readings
Describe what should trigger an alert in plain English. Pinga evaluates the readings contained in incoming messages against those instructions.
Equipment that goes quiet
Configure a heartbeat check for a monitor expected to report regularly. A missing report can then trigger a notification.
Different people, different hours
Use monitor schedules for daytime operators and after-hours contacts, with an All other times plan covering the gaps.
Safer, smarter call-outs
Heading out to a remote pump shed?
The responder can start Working Alone, choose an expected finish time and receive welfare checks. Missed check-ins follow a separate escalation plan, with the latest shared location available to help the team follow up.
Welfare checks stay separate from equipment faults. Accepting a job does not confirm the equipment has recovered—or that a worker is safe.
Working Alone & team location ↗Start with one useful alarm
Connect a message.
Test the response.
Each monitor has an email address and secure webhook URL. Equipment can also send SMS to Pinga’s shared number after you verify its sending number, or to an optional dedicated number.
Send a real example message, check the interpretation and test your escalation plan before relying on it alongside your existing arrangements.
Explore the setup →Does Pinga control the irrigation system?
No. Pinga receives supported messages and coordinates notifications. Your irrigation controller, local protection and operating procedures remain responsible for controlling equipment.
Bring some order to the alarm.
Make your next call-out
safer and smarter.
Get started with Pinga ↗Talk through your setup ↗
Start with one monitor.
Build the response around your team.