Alarm Notification Settings

Configure how alarms escalate and how operators are notified. The in-app Help Wizard is the setup order. Leave email off until a real alarm is worth a call-out. Alarm mail and alarm texts use the account connected under Tenant Settings → Mail and SMS. Connect that account first. The steps, including Gmail, are in Mail and SMS. If that account is empty, the alarm still shows on the Alarms page and the mail or text is not sent. Signup mail does not use this account. Telegram groups are unchanged.

When mail and messages go out

On Users, the table When mail and messages go out is the plant default when nothing has been saved:

Event	Email	Messages
Critical	Immediately	Immediately
Major	Immediately	Off
Warning	Combined mail	Off
Minor	Combined mail	Off
Clear	Combined mail	Off

The combined mail waits 15 minutes and sends only when something new is in it. A severity step-up notifies again only when the alarm reaches Critical.

Stop mailing a flickering alarm is on by default. If the same alarm comes back 3 times in 1 minute, mail and messages stop. The alarm stays on the Alarms page.

Hold mail and messages at night is off until you turn it on. Times are India time. From 22:00 to 06:00 the alarm still shows on the Alarms page. Mail, Telegram, and messages wait, then go out when the quiet hours end. Change the two times if the plant night is different.

New users start with email and messaging off.

Alarms go to Telegram groups, not to each engineer's personal chat id. Field engineers only install Telegram and join the group that matches their level.

Alarm Escalation Settings

On Users (tenant admin / owner):

• L1 → L2 (minutes)
• L2 → L3 (minutes)
• Stop on Ack
• Stop on Clear

Telegram groups by escalation level

Level	Who is notified	Telegram field
L1	Immediately when the alarm opens	L1 group
L2	After the L1→L2 delay, if still active	L2 group
L3	After the L2→L3 delay, if still active	L3 group

Leave L2 or L3 blank to reuse the L1 group for that level. A clear is posted only to groups that already received that alarm.

Autoconnecto does not create Telegram groups for you. You create them in Telegram, add our bot, then wire the chat ids on the Users page.

Complete setup (first time)

Do this once per tenant. About ten minutes.

1. Create the groups in Telegram

On your phone or desktop Telegram:

1. Open Telegram → New Group.
2. Name it clearly, for example Plant alarms L1.
3. Add at least yourself as a member.
4. Optional for day one: create Plant alarms L2 and Plant alarms L3 the same way. If you skip them, L2 and L3 reuse the L1 group until you fill those fields.

You need one group for a working L1 trial. Extra levels can wait.

2. Add the Autoconnecto bot

1. Open a chat with @autoconnecto_bot and tap Start (required once, or Telegram search may not find the bot).
2. In each alarms group: open the group → Add members → search @autoconnecto_bot → add it.
3. In the group, send any short message (for example hi). The bot must see at least one message before Detect can find the group.

If search does not show the bot, open @autoconnecto_bot first, tap Start, then search again from the group.

3. Put people in the right group

• People who should see every new alarm → L1 group.
• People who only join after the L1 delay → L2 group.
• People who only join after the L2 delay → L3 group.

They do not paste a chat id into Autoconnecto. Membership in the Telegram group is enough.

In Autoconnecto Users, set each person's Escalation Level to L1, L2, or L3 so email digests (if enabled) match the same ladder. Telegram group routing uses the tenant group fields, not the personal messaging destination.

4. Wire the groups in Autoconnecto

1. Sign in as tenant admin or owner.
2. Open Users.
3. Open the Alarm Escalation Settings card.
4. Click Detect groups.
5. Click Use … as L1 (and L2 / L3 if you created those groups).
6. Or paste the chat id by hand (it looks like -5446577673).
7. Click Save Settings.
8. Click Send test alarm. You should see a test message in the L1 group within a few seconds.

If Detect returns no groups: confirm the bot is in the group, you tapped Start on the bot, and someone sent a message in the group after the bot joined. Then Detect again.

5. Optional: alarm sentence

Under Alarm sentence, edit the text that goes to Telegram. Placeholders:

Leave blank to keep the built-in sentence. A device link is added when the sentence does not already include one.

6. Optional: WhatsApp

WhatsApp is optional and uses your Meta credentials. Leave those fields blank to stay on Telegram only. See the short steps on the Users page if you add it later.

What a new user sees on day one

Step	Where	Result
Create group	Telegram app	Group exists
Add @autoconnecto_bot	Telegram group	Bot can post
Detect + Save + Test	Users → Alarm Escalation	L1 chat id stored; test message arrives
Invite field engineers	Telegram group invite link	They receive live alarms

Optional per-user messaging

User edit still has Messaging destination (Telegram chat id or SMS number) for Rule Engine Notify nodes or optional personal delivery. This is not required for the tenant ops-group alarm flow.

Email alarm digests remain available when email notifications are enabled on the user and an email account is connected under Tenant Settings. A phone number on the user is sent through the tenant SMS account. A Telegram group id still uses the platform bot.

Escalation Behavior

• Escalation timing can be configured between levels.
• Escalation can stop on acknowledgment.
• Escalation can stop on clear.
• Tenant Telegram group posts use the same escalation / cooldown rules as other channels.