Assign one person to be the first to read website notifications, check the problem, and pass it on to someone who can fix it. This could be the owner, a manager, or a developer. The important thing is to agree in advance on what they should do and who will cover for them when they are away.
Sending notifications to everyone often leaves errors without an owner: each person assumes a colleague will handle them. A small store can use a simple arrangement: the owner checks the event, the developer fixes the site, and the manager confirms that customers can place orders again.
Choose someone based on their working hours
The recipient does not need to understand how the server works. They need to open the address in the message, check the time of the check, and decide whom to contact. Someone who reads work email once a week is not a good choice to handle the initial review of an outage.
Write down the hours when they monitor messages. For example: “Anna checks notifications on business days from 9:00 to 18:00; outside those hours, the owner checks any current problem.” Do not turn this arrangement into a promise of 24/7 support if nobody provides it.
Also check that they can access the relevant information. The recipient should be able to find the right site, open the report, or get it from the account owner. Receiving an email or Telegram message does not, by itself, grant access to a private report. Do not make the report public just to make it easier to forward.
Specify the channel in the site settings
In the “Site monitoring” dashboard, open the relevant site, select the “Settings” tab, and find the “Where to send notifications” section. It contains the “In dashboard”, “Telegram”, and “Email” channels.
For Telegram, first click “Connect Telegram” and complete the connection in your profile. For email, check the listed addresses; the “Change addresses” link takes you to your profile settings. After changing the settings, wait for the “Settings saved” message.
Now ask the recipient to confirm a specific message: which site, what event, and when it arrived. A saved setting does not prove that the message was delivered. If no event has occurred yet, note: “channel configured, delivery not yet verified.” For a detailed guide to email, see instructions for missing email.
Agree on who handles different problems
Not every event needs to be sent to a developer immediately. A new technical issue can be added to the next work plan; for a current outage, first open the site and confirm its status.
| What the recipient saw | What they check themselves | Who they pass it on to |
|---|---|---|
| The site does not respond | Whether the same address opens now | The hosting provider or developer |
| The “Delivery” link leads to an error | Whether the same issue occurs when following the link from the menu | The developer |
| The page shows an old price | What price the company has approved | The editor or manager |
| The summary shows a new issue | The address and audit date, and the page’s importance | The person responsible for the work plan |
Replace the roles with names and contact details. This is your working reference, not an automatic task assignment feature. The recipient chooses who to contact.
Pass on one clear set of facts
Example message to a developer: “On 04.10 at 10:15 MSK, the ‘Delivery’ link in the top menu leads to /delivery-old, which opens an error page. I checked from the homepage and a product page. It should lead to the current delivery terms. After publishing the fix, I’ll check both links again.”
This description is more useful than ten forwarded notifications. For an outage, include the result of your current manual check and the time the site was last updated, if known. Do not blame the hosting provider or new code based on a single message.
The developer task template has fields for the address, expected result, and post-fix check. Add the name of the person who accepted the work and the date of the next update to your own reference.
Arrange a backup before vacation
Give your backup a list of important sites, contact details for the people responsible for fixes, and one saved example. Ask them to open the address, find the date, and explain what to do next. This will show whether they have enough information without deliberately taking the site offline.
If you change the Telegram connection or email addresses, verify delivery again after updating the settings. Forwarding an old chat does not confirm that the new setup works. Until the new channel has been verified, agree to check the dashboard regularly.
A useful note for the vacation period: “From 12 to 18 October, Igor will check messages first. For outages, he will contact the hosting provider; for page errors, the developer. The owner approves paid work. Anna will resume reviewing notifications on 19 October.” It includes a person, dates, and actions; no additional complex rules are needed.