Releases
New in Entergram: Rebuilt Analytics, a Ticket Kanban Board, and Themes

A few things shipped this month that are actually worth your time. Everything else was cleanup.
💬 We announce releases in our Telegram group first, and a good share of what is below started as a message from someone in it. Join the group →
Analytics, rebuilt
If you run more than one Telegram account in a workspace, analytics used to show them to you one at a time. Now it adds them up.

One overview across every connected account — messages, sent versus received, active chats, files, deleted messages — with a donut showing which account is carrying the load. If the same account was connected twice, you were seeing inflated numbers. That is fixed.
The metrics that tell you whether a team is keeping up sit at the top, each with its movement against the previous period:
- Average response rate — the share of conversations you are actually replying to
- Average first reply — how long someone waits for a human
- Messages per active chat — whether your load is spread or concentrated
- Peak hour and busiest day — when to staff up
A 6-minute first reply means something different when it is down 40% from last month. That context was the main thing missing before.
Below the headline numbers there is a highlights row: most active operator, fastest reply, best coverage, most new chats this week. There is also a split by chat type — private, groups, channels — per account, and Top Chats is now searchable instead of scroll-only.
More on what the reports cover: Telegram analytics.
A Kanban board for tickets
A list tells you what exists. A board tells you what is stuck.
The board is not locked to ticket status. Point it at any single-select custom column and the lanes rebuild — priority, owner, deal stage, region, whatever your team actually uses. Tickets with nothing set go in a "No value" lane, which is usually where the forgotten work lives.
Lane order and your chosen grouping save per view, so the board looks how you left it. You can assign a team member straight from the card without opening the ticket.
Tickets also have short numbers scoped to your workspace now, so you can say "42" in a standup instead of pasting an identifier.
Background on why boards beat lists for support work: Kanban board for Telegram support tickets.
Views, filters and sorting that behave
If you live in the chat table, this is the part you will notice.
Clearing a filter or dropping a sort now happens in the column header itself, instead of hunting through a menu. Views show a changes pill whenever you have unsaved edits — a filter you added, a sort you changed, a column you moved — so you can see exactly what has drifted from the saved view and revert it in one click. No more wondering whether you are looking at your view or an accidental variation of it.
Custom filters are also namespaced per chat window now, so a filter you apply in one place no longer bleeds into another, and exclude-only custom column filters actually apply on their own. New group-by controls let you regroup chats on the fly and act on a selection in bulk, including bulk chat exclusion.
Themes, text size, and chat backgrounds
You can now pick a variation for light and dark mode independently — Paper, Cool White, Gray and Slate for light, Gray, Blue and Purple for dark. They theme the whole surface set, not just the background, and apply before first paint so there is no white flash on load.
There is also a proper interface text-size control with four steps in Profile → Text size (not browser zoom — spacing scales with it), and three chat background patterns: Doodles, Bubbles and Stars.
And it is faster
Chats and comments now open from local cache instead of waiting on the network, so conversations feel immediate. The realtime engine was rebuilt: messages, reactions, custom column values and unread counts stay converged across the workspace without flicker. Duplicate messages in chats where two of your accounts share a conversation are gone, and unread counts recover correctly when you switch chats.
We also retired SLA notifications. They generated more noise than signal, and the response-time metrics above answer the same question better.
Open Entergram and have a look at analytics first — it is the closest thing to a rewrite here.
And if you want to tell us what to build next, we are in the Entergram Telegram group every day.
Ready to Upgrade Your Telegram Workflow?
Don't waste another lead. Don't lose another message.
Get Started with Entergram


