InnerWeb
Skip to main content

Alert connectivity test checklist before go-live

An alert connectivity test is an hour of work that saves weeks of explaining why an alarm did not arrive. The list below covers four channels: e-mail, SMS, phone and the team messenger. It is run on test accounts before the system starts handling real permits and trainings.

4
channels in the connectivity test
Source: karta
10
checklist points
Source: checklista

Preparing the test

Prepare test accounts in three variants of data: with an e-mail address, with a phone number only, and with an employee number. Each variant has a different invitation path, so each needs a separate attempt.

The test is carried out jointly by IT and the coordinator, because IT sees the mail and the firewall, while the coordinator judges whether the message is understandable for the recipient.

E-mail channel

E-mail messages go into a queue, and their status has three states: queued, sent and error. The test should confirm that the message reached the sent state and that the recipient sees it.

Also check the sender: messages carry the plant name as the sender, in the subject and in the header, and InnerWeb only in the footer. If the sender looks different, the configuration is wrong.

Checklist points by channel

Checklist points by channelDonut chart: the ten checklist points split into e-mail, SMS, phone, logs and team, and preparation and proof.E-mail: 3 points (30%)SMS: 2 points (20%)Phone: 1 points (10%)Logs and team: 2 points (20%)Preparation and proof: 2 points (20%)10pointsE-mail3 points (30%)SMS2 points (20%)Phone1 points (10%)Logs and team2 points (20%)Preparation and proof2 points (20%)
Source: Number of checklist points on this page

SMS and phone channels

An SMS must fit into one segment. The text is transliterated into the GSM 03.38 alphabet, because a single Polish diacritic letter would switch the message to the 70-character encoding. A warning in the log means the text is too long.

A phone call with a speech synthesiser lasts roughly 25-33 seconds. Call the test number, assess how clear the message is and check the entry in the call log.

Team messenger and link without a session

The team channel is switched on with one setting containing the webhook address. Send a test event and check that it appeared in the channel. Separately, open the SMS link on a phone connected to a mobile network, because the recipient does not have a session yet and the link must work publicly.

If an event does not arrive, the most common cause is blocked outgoing traffic from the application host or a wrong webhook address.

Proof and acceptance of the test

After the test, record who carried it out, when, and with what result for each channel. Sent SMS messages and PBX calls are recorded in the logs, so proof of dispatch already exists; you only add the assessment of clarity and the confirmation of receipt.

Only with such a record can the plant consider the channels ready for production. Without it, the first alert failure becomes a dispute over whether the channels ever worked.

Checklist

Video

Frequently asked questions

How often should the connectivity test be repeated?

After every change to the SMS gateway, the mail rules, the webhook address, or after moving the server.

Can the test be run on real users' accounts?

Better on test accounts, because the test sends messages and should not disturb the employees of external companies.

What to do when an SMS takes more than one segment?

Shorten the template. The log leaves a warning for every message longer than one segment.

Are you preparing a production start?

Book a meeting with InnerWeb. We will go through the connectivity checklist together with your IT team.

Let's talk