Skip to content

Telegram notifications, digests and quiet settings

Once your Telegram account is linked, the bot forwards your Mesy notifications to the chat, and can send a morning digest. You choose which types push to Telegram in Settings under the Notifications tab, and you can mute the bot from either side.

Each notification arrives as a message with its title and body. When it concerns a record, the bot adds the record’s name, plus its stage and value where those exist, and buttons:

  • Mark Read marks it read in Mesy as well.
  • Open in Mesy opens the record, read-only, in the mini app.
  • Show details replies with the record’s fields.

A notification about a pipeline record also offers Show pipeline, and a task notification offers My tasks. These buttons read data only; none of them changes a record.

Telegram only carries notifications that exist in the app. A type you switch off in-app never reaches Telegram either.

The Notifications tab in Settings lists every notification type with an In-app column and, once you’re linked, a Telegram column. Everything is on by default. To quiet one type on Telegram while keeping it in the app:

  1. Open Settings and select the Notifications tab.
  2. Find the row, for example Task assigned.
  3. Untick the box in the Telegram column.
  4. Check the row: the In-app box stays ticked and the Telegram box is clear.

The rows you can control on both columns are Note on your record, Task overdue, Task assigned, Record assigned and Workflow proposals. If your workspace has a pipeline type, two more rows appear for that type: its stage changing, and a new record being created (managers only).

Under AI & system alerts, three types always land in-app and show Always on in that column: AI proposals, Auto-linking paused and AI limit reached. You can still untick them in the Telegram column. Before you link Telegram, the page shows only the In-app column and a link to Integrations. The AI & system alerts rows appear once you’re linked.

The Telegram checkbox in the column header is the master switch. Unticking it mutes every push, and each row’s Telegram box greys out until you tick it again. Sending /mute to the bot does the same thing, and /unmute restores it; the bot replies Telegram notifications muted or unmuted. The setting is shared, so a change on either side shows on the other.

Muting affects Telegram only. Notifications keep arriving in the app.

/digest sends today’s briefing on demand. To have the bot send it every morning:

  1. Send /digest on to the bot.
  2. Read the reply. It confirms the digest is on and that it arrives daily at 8am Singapore time when there’s something to report.

The bot sends the digest only when there’s news: overdue tasks, stalled deals, pipeline movement this week or unread notifications. On a quiet day it sends nothing. Because the digest is an ordinary notification, /mute silences it too. Send /digest off to stop the morning push; /digest on demand keeps working.