InnerWeb
Skip to main content

Plant notification channels: choosing the right one

A safety manager designing the notification matrix before the pilot must assign events to channels: e-mail, SMS, PBX phone calls and team messenger. Each channel has a different role and a different cost. Below are seven recommendations that help match a channel to an event, not the other way round.

4
notification channels in one plant matrix
55 min
aggregation window of the missing-training alert per company

Who these recommendations are for

We address the recommendations to the safety manager, the security manager and the IT department, who before the pilot decide who, when and how is to be notified. The system sends notifications through three channels: e-mail (invitations, links to permits and trainings), SMS and phone calls from the PBX. A fourth channel, the team messenger, shows reception events in the plant channel.

Sent SMS messages and PBX calls are recorded in the registers, which gives the plant an audit trail and usage statistics. This is an important argument when choosing a channel: the more critical the event, the more important the proof that the message went out.

Recommendations

Seven recommendations arranged from the simplest to those that require demanding decisions.

First recommendation: e-mail for everything that needs content and a link. Invitations and links to permits and trainings carry more information than fits in an SMS, and e-mail allows full context to be attached. For a user with an e-mail address the welcome message goes by e-mail and switches off the welcome SMS, so there is no duplication.

Second: SMS for a short prompt with a link. SMS works well when only a phone number is known, because an invitation with just a phone number produces an SMS with a link. The text must fit in a single segment, which we describe on a separate page about 7-bit encoding.

Third: a phone call with a voice message for reminders that require a reaction within the hour. One call with a speech synthesiser lasts roughly 25 to 33 seconds, so the message must be short. A phone call makes sense where the e-mail and SMS have already been sent and there is still no reaction.

Fourth: the team messenger for events that the whole plant team sees. The channel shows reception events, such as a registered guest, a group in training and a guest entry, and it is enabled with a single setting containing a webhook address.

Fifth: a grouped alert to the coordinators of contractor companies, not to everyone. A missing-training notification goes to the company's coordinators by phone, e-mail and team messenger, with a 55-minute aggregation window.

Sixth: do not send one event on all channels at once without a reason. Each additional channel brings cost and noise. A non-critical event is enough to record in the team messenger.

Seventh: test the connectivity of each channel before the pilot. The IT team checks whether SMS messages and calls arrive, whether the messenger receives the webhook and whether the registers record the entries.

Approximate duration of one voice message call

Approximate duration of one voice message callHorizontal bar chart: an approximate call with a voice message lasts from 25 to 33 seconds.010203040sLower boundLower bound: 25 s25Upper boundUpper bound: 33 s33
Source: InnerWeb

Decision table: event and channel

The matrix below is a starting point for your own version, not a ready standard. The plant adapts it to the number of people, shift times and its noise policy.

  • invitation with full information: e-mail
  • invitation for a person known only by phone number: SMS with a short link
  • reminder about training not completed after one day: phone call with a voice message
  • reception event visible to the team: team messenger
  • missing training at the gate: grouped alert to the company coordinator, three channels
  • audit trail: SMS and PBX call registers

Pitfalls when designing the matrix

The most common mistake is assigning all four channels to every event, because it seems safe. In practice this leads to noise, and coordinators start ignoring the messages. The second mistake is having no channel owner: someone in the plant must be responsible for ensuring the messenger webhook has a valid address and that phone numbers are up to date.

The third mistake concerns costs. SMS messages and phone calls are charged for every message and every call, while e-mail and the messenger practically cost nothing. The plant sets the specific rates with the operator, and we show their structure on the page about the costs of training campaigns.

How to check the matrix before the pilot

A good practice is a trial on test accounts: for each event in the matrix we run the scenario and check whether the message reached the right person through the right channel. Then we compare the registers with the expectation. If an SMS went out but has no entry in the register, the register needs fixing, not the matrix.

It is worth saving the trial results together with the matrix. During an audit this is a document showing that the channels were designed and tested, not merely switched on.

Video

Frequently asked questions

Does every user have to have an e-mail address?

No. An invitation can be sent to a phone number alone, and then an SMS with a link is sent. For people without any contact data, the activation link is handed over by the operator.

Where will the plant see that an SMS went out?

In the SMS and PBX call registers, which provide an audit trail and usage statistics.

Does the team messenger require integration with our IT?

It requires one setting with the webhook address of the team channel. The rest on the messenger side is channel configuration.

Design your notification matrix

We will go through your plant's events with you, and select the channels and connectivity tests before the pilot.

Let's talk