Pinga

How Pinga works

From “something’s wrong”
to “I’m on it.”

A practical response layer between the systems raising alarms and the people who can do something about them.

Set up your first monitor ↗
01

Give your messages
a place to land.

Create a monitor for a piece of equipment, a group of assets or a business process. Pinga gives it a unique email address and secure webhook URL automatically.

Need SMS? Attach an inbound number. Several monitors can share it, and known sending numbers can help narrow the match before AI reads the message.

EMAILYour monitor’s own address
WEBHOOKA unique, secure URL
SMS · OPTIONALA number your monitors can share
↳ Your monitor
02

Tell Pinga
what to look for.

Use plain English to describe the messages this monitor should handle, how to identify an asset, and what means fault or recovery. Your instructions belong to the monitor.

Pinga’s AI interprets the message’s meaning: fault, recovery, test, heartbeat or something needing review. Each asset and issue is tracked separately, so one device coming back online doesn’t clear another device’s fault.

See plain-English alarm examples ↗
EXAMPLE MONITOR INSTRUCTIONS
“Alert me if the cool room temperature is below 5°C or above 10°C. Use the room name as the asset ID.”
Clear context. Better matching.
03

Choose the people.
Set the order.

Add your contacts, then choose an existing monitor’s notification settings or create a sequence of your own. Each step specifies who to contact, how, and how long to wait.

SMS and email include a secure response link. Phone recipients press 1 to acknowledge or 2 to reject. An acknowledgement stops the escalation; rejection can move it forward immediately.

Plan a better call-out ↗
1SMS MichaelWait 1 minute
2Call MichaelWait 5 minutes
3Call SamIf nobody has accepted
04

Keep the story
with the asset.

When a matching recovery arrives, Pinga records it against the correct asset and issue. Choose whether to notify everyone in the sequence, only people already contacted, or record it quietly.

Follow the full history in the app. Alarm and recovery emails show the latest ten asset events in your organisation’s timezone, and response pages let recipients load more history.

Pump 04 · Low pressure fault
Michael acknowledges
Pressure recovery reported

Example timeline · one asset, one connected history

Start with confidence

One monitor.
One practice run.
Then build from there.

Create your organisation, sign in securely and add your first contact and monitor. Run a simulated call-out and acknowledge it before enabling monitoring.

You can expand to more assets, contacts and SMS inputs as your needs grow. Organisation data is kept separate, including users, contacts, notification settings and history.

AI helps interpret messages; it doesn’t verify the physical condition of your equipment. Review your instructions and test your complete delivery path.

Bring some order to the alarm.

Make the next
call-out a clearer one.

Get started with Pinga ↗Talk through your setup ↗

Start with one monitor.
Build the response around your team.