Analytics

Analytics turns your Telegram activity into numbers you can act on: how much you send and receive, how fast you reply, when your audience is active, which chats dominate your time, and — in a workspace — how the team is performing.

What Analytics shows

Everything is driven by two inputs: which accounts you’re viewing and which time range. The main cards and charts:

Headline stats — total messages, response rate, active chats, outgoing messages (with period-over-period deltas on short ranges).
Message volume — daily incoming vs outgoing.
Activity heatmap — a 7×24 grid of messages by weekday and hour; click a cell for the exact count.
Response stats — response rate, average response time, and total conversations. A “trigger” is any incoming DM, or an @mention/reply in a group; replies within 1 hour count.
Media stats and Top chats — file/reaction breakdowns and your busiest 20 chats.

Access & sync

Analytics is Pro-only (and the 3-day Pro trial). It’s wired up automatically when you connect a Telegram account — there’s no separate step.

The first sync runs in the background; accounts show Syncing (blue) then Synced (green). Initial sync can take minutes to tens of minutes depending on history.
Time ranges: Today / 3d / 7d on any Pro-tier access; 30d / 1y / All time and custom ranges on paid tiers (hidden on the trial).
On Basic, the page falls back to a Custom Fields Analytics view — field coverage, value distribution, and change history for your contact database.

Personal vs workspace mode

Switch modes from the sidebar:

Personal — one of your own accounts; metrics are about your messages.
Workspace — aggregates across selected members’ accounts, grouped by member.

Owners and admins always see every member’s data. Members see everyone’s data only if “Members can see all analytics” is on; otherwise they’re locked to their own accounts.

Team performance & tickets

In workspace mode you also get:

Team performance board — one row per member: incoming/outgoing counts, response rate and time, unread chats, and activity from the audit log (field changes, comments, files).
Ticket analytics (if tickets are enabled) — created vs closed, average resolution time, SLA compliance and state mix, and per-member SLA. See Tickets.