To receive reChecker messages in Telegram, first link Telegram to the relevant account, then enable the channel in the site settings. After that, check delivery using a specific event. The status “Account connected” alone is not enough to verify this.
Do not take a live site offline to test notifications. You can wait for a suitable event after configuring the settings and compare it with the message received. If no event has occurred yet, setup is complete, but delivery has not been confirmed.
First, check the account and site
Sign in to the reChecker account where the relevant site is connected. This is especially important if you have personal and work accounts: linking Telegram to one does not configure the other.
In the Site Monitoring dashboard, select the site and open “Settings”. Find the “Where to send notifications” section. The “Telegram” channel indicates whether an account is connected. If it is not, the toggle is unavailable and there is a “Connect Telegram” link beside it.
Decide who will receive the notifications. The recipient should know what to do with a message and have a way to access the relevant information. If an employee will read the notifications, first agree on how tasks will be handed over, as described in the article about notification recipients.
Complete the link in your profile
Click “Connect Telegram”. The link takes you to the Telegram settings in your profile. Follow the linking steps shown there for the Telegram account that will receive the messages.
When you are done, return to the site settings. The text “Account connected” indicates that the link is in place. The profile may also show the status “Sending paused”: in that case, the link exists, but you cannot consider the channel ready to deliver messages. Check its status with support.
If someone else is handling the connection, agree on how they will access it. Do not put linking codes or links in a shared work log. A note such as “Telegram linked to the work account, checked 04.10” is enough; chat-specific personal information is not needed.
Enable the channel for the selected site
In the “Where to send notifications” section, enable “Telegram” and wait for the “Settings saved” message. Make sure you changed the settings for the correct site, not a neighboring connection.
Sending depends on the connection to Telegram, user settings, and whether external sending is permitted in the service. If the status indicates that sending is paused, turning the toggle on again does not resolve the underlying issue.
Do not expect a notification for every word changed on a page. The service generates specific events; a scheduled summary and a problem notification are different cases. If you are expecting a particular type of message, see the “When notifications arrive” explanation and check with support if needed.
Match the event to the message received
Use an event that occurred after you changed the settings. Check whether the Telegram message refers to the same site and time. An older message about a different site does not confirm that the new setting is working.
Example verification record:
| What was checked | Result |
|---|---|
| Site channel | Telegram enabled 04.10 at 09:30 MSK |
| Event | A message about a resolved problem appeared in the dashboard |
| Recipient | Confirmed receiving the same message in the relevant chat |
| Next action | Opened the report and checked the address of the page that was fixed |
This is an illustrative example, not confirmation that a message was actually delivered to your account. Fill in the table with your own information. If you see an event in the dashboard but no Telegram message, record that exact discrepancy. If there is no event, first find out whether there was a reason for a notification to be sent.
If the message did not arrive, prepare a specific question
Give support the site, event type and time with the time zone, connection status, and the time the channel was enabled. Include the date of the last message you actually received, if known.
You can write: “For example.ru, Telegram was enabled 04.10 at 09:30 MSK, and the account is connected. The event about a resolved problem is visible in the dashboard at 11:10, but there is no message in the relevant chat. Please check the delivery of this event.” Do not include your password or connection codes.
Until delivery has been investigated, check the site's status directly in the dashboard. If you see a message that the site is unavailable, start with checking the site's current status. Even a message you receive is only the start of an investigation: it does not explain the cause or fix the site automatically.