Skip to content
PIAGOGO! Site Ready

Alerts & notifications

The chasing does itself.

Expiry alerts set against the credential so the chasing runs itself, email and SMS to a tagged group when something will not wait, and every message kept on the file, sent by the system or sent by you.

Book a Demo

Watch the chasing do itself.

An expiry alert in GO! Site Ready, set against named medical credentials ninety days ahead

Working with PIAGO

  • Frontline Equipment Maintenance
  • BRW Transport
  • Hydrapower
  • Kerembla
  • Premier Plant Repairs & Fabrication
  • Whiteman Welding
Customer stories

How it works

From a date on a record, to somebody actually booking it.

The alert, and the messages it sent

Step 01

The system notices before you do

Expiry alerts are configured against the credential rather than the calendar, with the lead time set by you, so the first to know a ticket is running down is the software rather than the client's gatehouse.

Want to see what would be alerting across your people in the next ninety days?

The full list

Everything in alerts and notifications.

In the app itself this sits under Communications, alongside the mailbox and the SMS log.

Expiry alerts

Set against the credential, as far ahead of the date as you want. Ninety days on the medicals above. The administrative burden of reminding people to renew stops being a person's job and becomes a setting.

Mailbox

Email one person or a whole tagged group, with attachments, from inside the system rather than a personal account, so the send is on the record either way.

SMS

Broadcast what will not wait to people who are not at a desk: a site change, a shutdown call, a credential that lapses this week.

Correspondence history

A complete record of what was sent, to whom and when, held against the person or the job it concerned. Auditable rather than recoverable.

Recipients from the register

The list is drawn from the records themselves, so who gets a message follows from who holds the credential or the job rather than from a contact list somebody maintains.

Roster schedules by email

Send people their own schedule from the job scheduler, so the roster reaches them in a form they can keep rather than a screenshot in a chat.

Bulk without the mail merge

Tag people by project, team or ticket, then message that group and nobody else. Somebody has left a tool on site and every fitter needs to know: one message, no spreadsheet, and no texting the whole company.

Evidence you told them

Where a lapse becomes a question later, the record shows the worker was notified and when, which is a different conversation from taking somebody's word for it.

The difference

What changes when the reminding is not a person's job.

How it usually goes

  • Chasing renewals is somebody's recurring calendar reminder.
  • The reminder goes to a group chat and everyone assumes someone else acted.
  • Proving you told a worker means going through a personal inbox.
  • The list of who to contact is rebuilt in a phone each time.
  • The one person who does the chasing takes leave.

With GO! Site Ready

  • The alert is set against the credential and fires on its own.
  • It is addressed to the person who has to book it, by name.
  • The message sits on the record with the date it was sent.
  • The list comes from the register, so it is right without being rebuilt.
  • It keeps running while they are away, because nobody is running it.

Questions about alerts and notifications

We already remind people. Why does this need to be in the software?
Because reminding is only reliable while the person doing it is available and not busy, and the weeks it fails are the weeks you are flat out, which are the weeks a turnaround costs you most. Moving it into the system means the reminder fires on the credential's own date rather than on somebody remembering, and it keeps firing while they are on leave.
Does the worker get told, or just us?
Both, and it is worth setting it that way. The person who has to book a coal mine workers' health assessment is the one who needs the notice, and the coordinator who has to cover the shift needs it too. Sending only to the office means the office chases; sending to both means some of them are already booked before anyone chases.
Can we prove a worker was notified?
Yes. Messages are kept as correspondence history against the record they were sent from, with the date. That matters when a lapse turns into a question about who knew what. An inbox is a personal artefact. A record on the file is not.
Is SMS actually useful, or is email enough?
Email is right for detail and for the record. SMS is right for people who are on a site, in a truck or between jobs, which is most of a contracting company's workforce for most of the day. The two are not alternatives. A shutdown call goes by text and the confirmation goes by mail.
How far ahead should we set the alerts?
Far enough that the renewal is bookable. Thirty days is fine for an online refresher and nowhere near enough for a health assessment in regional Queensland, where appointment waits run to weeks. Set the window per credential to how long it actually takes to arrange, not to one number for everything.

See it against your own renewal windows.

Bring the credentials your people actually hold and we will set the alert windows to how long each one really takes to arrange.

Start a free trial

14 days, no credit card needed. Or book a demo with Carl

Not the person who signs it off?

Send it to your GM