Telegram RegisterThe public register of Telegram
Telegram profile photo for КБ: конструктор CRM/ERP для бизнеса

Channel

КБ: конструктор CRM/ERP для бизнеса

@clientbase

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Cite this entry

456subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001060688845
TypeChannel
Username@clientbase
CreatedBetween 1 May 2016 and 31 January 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/clientbase

Growth

4524564547 August 2026 — 452 subscribers8 August 2026 — 452 subscribers16 August 2026 — 454 subscribers23 August 2026 — 456 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net +4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 451–457 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:58456+2
16 Aug 2026, 06:23454+2
8 Aug 2026, 05:01452no change
7 Aug 2026, 12:55452first reading

Engagement

18 posts held, back to 4 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.2%
avg views ÷ 456 subscribers
Avg views / post
64.7
3 posts measured
Reaction rate
16.5%
reactions ÷ views · ER floor
Posts in window
3
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held18 (4 June 20267 August 2026)
Views total194
Reactions total32
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
2m 05s
Average length
14s

Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

180 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8647.8%
😁3821.1%
👍2715.0%
2212.2%
🤩42.22%
👏31.67%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 180reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 4 June 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
4
of 18 we hold a reading for · 22%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @clientbase. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 4 June 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 13:41 UTC41 views13 reactionsread 8 August 2026
Video

Это судьба 💯 Сегодня хотим познакомить вас с нашей феей тонких настроек-Аллой🧚‍♀️ Не забывайте ставить реакции, нам очень приятно☺️

🔥93👏1

6 Aug 2026, 10:34 UTC54 views5 reactionsread 8 August 2026

🤖 ИИ может не только отвечать на вопросы, но и работать с данными в CRM Продолжаем делиться материалами из нашего будущего курса по работе с ИИ в КБ. В этом уроке разбираем два типа интеграции: ✅ «Текст - добавление строк» - ИИ по вашему запросу автоматически создает новые записи в нужной таблице CRM. ✅ «Текст - заполнение записи» - достаточно написать информацию обычным текстом, а ИИ сам разнесет данные по нужны

🔥3👍2

31 Jul 2026, 14:22 UTC99 views14 reactionsread 8 August 2026
Video

Нужно очень много потрудиться перед отпуском, чтобы потом спокойно отдохнуть😂 В свежем ролике наш верховный интегратор, директор по развитию партнерской программы-Михаил, а также всем знакомый, но от того не менее очаровальный менеджер- Юлия🙌

😁7🔥43

24 Jul 2026, 10:18 UTC138 views15 reactions1 Starread 8 August 2026
Video

И снова пятница, а значит мы подготовили новое видео. Это Вильдан — ваш технический ангел-хранитель😇 Он ещё не разучился улыбаться, хотя видел логи ваших ошибок👾 Желаем хорошего всем вечера!

🔥8👍51😁1

17 Jul 2026, 13:46 UTC160 views13 reactionsread 8 August 2026
Video

Признавайтесь, было?😄 Всем хорошего завершения недели!

😁10🤩21

10 Jul 2026, 11:23 UTC179 views10 reactions1 Starread 8 August 2026
Video

С каждым неотвеченным сообщением в мире грустит один менеджер КБ🥺 Но это не мешает нам заряжать вас на классные выходные с Аязом и Юлей⭐️ А если в субботу и воскресенье вы трудитесь, то желаем вам лёгкой и продуктивной работы! 💪

🔥7😁3

10 Jul 2026, 08:15 UTC131 views2 reactionsread 8 August 2026

🎓 Делимся одним из уроков нашего нового курса по ИИ Сейчас мы готовим курс по работе с искусственным интеллектом в КБ. В нем разберем не только настройку интеграций, но и то, как получать от ИИ действительно качественные результаты. А пока решили показать один из уроков. В этом видео рассказываем: ✅ Как использовать готовые промпты и адаптировать их под свои задачи ✅ Зачем нужны предустановленные ИИ-дополнения ✅

🔥2

3 Jul 2026, 09:26 UTC157 views16 reactionsread 8 August 2026
Video

Вселенная, мы услышали, Юля, записывай! А вы-получайте крутые решения⭐️ Радуем вас пятничным роликом с наши персональным менеджером🌌 Если давно что-то откладывали,и вам нужен был знак,то это он 💯

🔥9👍43

2 Jul 2026, 11:53 UTC139 views6 reactionsread 8 August 2026

📄 Автоматическая выгрузка данных в CSV Если вам регулярно нужно выгружать данные из подтаблиц, этот шаблон поможет полностью автоматизировать процесс. С его помощью можно настроить автоматическое создание CSV-файла при наступлении нужного события или по расписанию. Возможности шаблона: ✅ Выгрузка записей из выбранной подтаблицы в CSV ✅ Сохранение файла прямо в поле таблицы ✅ Экспорт всех полей или только нужных ч

🔥6

26 Jun 2026, 11:06 UTC156 views21 reactionsread 8 August 2026
Video

Закрыл же 🙃 На позитивной ноте завершаем неделю с нашим экспертом по ИИ-Аязом 🕺

😁8🔥64👍3

25 Jun 2026, 08:45 UTC148 views7 reactionsread 8 August 2026

💰 Сколько стоит ИИ в CRM? Разбираемся с токенами Один из самых частых вопросов после подключения Clientbase GPT - сколько будет стоить использование ИИ на практике. В новом видео показываем: • Что такое токены и как они расходуются • Где посмотреть текущий баланс токенов • Как модели влияют на стоимость обработки • Зачем нужны лимиты символов и размера аудио • Как базы знаний влияют на расход токенов • Как заранее

🔥51👍1

24 Jun 2026, 09:05 UTC123 views6 reactionsread 8 August 2026
Photo

За 5 лет работы многое меняется: процессы, задачи, подход к ведению бизнеса. И здорово, когда CRM может меняться вместе с вами. Наш клиент отмечает, что именно в «Клиентской базе» удалось постепенно выстроить систему под свои потребности и адаптировать её под реальные рабочие процессы. Сегодня в системе уже автоматизировано многое: 🔹 заявки с сайта и мессенджеров попадают в нужную таблицу автоматически 🔹 сохраняетс

🔥41👍1

Showing the 12 most recent of 18 posts we hold for @clientbase. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

5 Jun 2026, 12:34 UTCAnonymous Poll17 voters

А вы уже внедрили ИИ?

  1. Да✅41%
  2. Нет🤔47%
  3. Хочу, нужна консультация🤝12%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 4 June 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 23 August 2026 — this entry's latest reading, not the date you are reading this.

“КБ: конструктор CRM/ERP для бизнеса” (@clientbase), 456 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/clientbase.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.