Telegram RegisterThe public register of Telegram
Telegram profile photo for VP of sales

Channel

VP of sales

@vpofsales

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,741subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001211769068
TypeChannel
Username@vpofsales
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/vpofsales

Growth

1,7401,7421,7417 August 2026 — 1,742 subscribers7 August 2026 — 1,742 subscribers10 August 2026 — 1,740 subscribers13 August 2026 — 1,741 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -1. 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 1,740–1,742 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 14:081,741+1
10 Aug 2026, 16:381,740-2
7 Aug 2026, 09:461,742no change
7 Aug 2026, 09:341,742first reading

Engagement

20 posts held, back to 1 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.1%
avg views ÷ 1,741 subscribers
Avg views / post
229
6 posts measured
Reaction rate
2.11%
reactions ÷ views · ER floor
Posts in window
7
of 20 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 6 August 2026
Posts held20 (1 June 20266 August 2026)
Views total1,372
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:38 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.

Reaction mix

115 reactions across 19 posts, in 15 distinct kinds. The most used accounts for 41.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4841.7%
👍2420.9%
119.57%
💯97.83%
🤣76.09%
👾32.61%
🍾21.74%
👏21.74%
👨‍💻21.74%
🙊21.74%
💔10.87%
😍10.87%
🙏10.87%
🤷‍♂10.87%
🫡10.87%

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 19 of the 20 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 115reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 June 2026 to 6 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.

Recent posts

6 Aug 2026, 09:33 UTC100 views3 reactionsread 7 August 2026
Photo

От простого к сложному, то есть наоборот Мы начинали со сложного дашборда: Каждое движение менеджера и лида оценивается по 10-20 параметрам, потому что от них зависит исход сделки. Звучит солидно. На практике мерить всё - это не глубина, а отсутствие гипотезы. РОП открывал экран и не понимал, за что хвататься первым 🤯. Process Mining на 100 тыс сделок, про который мы писали выше, дал ответ. Из нескольких десятков

1💯1🔥1

1 Aug 2026, 07:56 UTC172 views6 reactionsread 7 August 2026
Photo

Как наши клиенты прожили июль Что изменилось за месяц: 📈 система держит рост нагрузки ×2, надёжность потока 99,1% (в июне докупили карт - не зря); 📈 видимость звонков была ~3%, стала 100% — не выборка РОПа, а каждый разговор; Опережающие метрики пошли вверх: 📈 следующий шаг +1,3 п.п., 📈 квалификация +0,9, 📈 работа с возражениями +0,7 за месяц. Но самое интересное - где течёт. Возражение слышат на 86%, а диагност

👍41🔥1

31 Jul 2026, 14:12 UTC197 views3 reactionsread 7 August 2026

Вялый казахский DDoS/pentest [email protected] Дайте больше, чего так вяло? Мы хотим сами найти слабое звено 🤷🏽‍♂️ Хороший знак: кому-то еще перешли дорогу)

👾2🤣1

28 Jul 2026, 12:13 UTC266 views8 reactionsread 7 August 2026

https://axoftglobal.ru/news/salesai_zaregistrirovala_sistemu_upravlyayemogo_rosta_prodazh_i_raskryla_sem_zakonomernostey_iz_analiza_20_000_b2b_zvonkov

🔥5🍾2👍1

23 Jul 2026, 08:50 UTC360 views5 reactionsread 7 August 2026
Photo

Спросите свою CRM, почему вы теряете сделки. Она уверенно ответит: «нет потребности» и «дорого» Мы сверили два независимых источника – что менеджер записал причиной отказа и что клиент на самом деле сказал в звонке. На массиве в десятки тысяч сделок картина оказалась зеркально перевёрнутой. Цена звучит примерно в каждом третьем разговоре, а в CRM попадает втрое реже. Претензии к продукту звучат в четверти разговоро

🔥3👍1💯1

17 Jul 2026, 14:42 UTC277 views4 reactionsread 7 August 2026

10 способов эффективно зафейлить пилот «Либо он даёт эффект на бизнес, либо фиксируем неуспех». Так мне написал клиент про наш пилот. Пять месяцев работы, и вот такое сообщение в чате. Он прав. Дальше так продолжаться не может. Я разобрал этот пилот тем же методом, которым мы разбираем чужие сделки. Получилось десять причин. Ни одна не техническая: конвейер держал пики, ошибки закрывались ретраями, шесть новых мо

🔥2👍1💔1

16 Jul 2026, 07:58 UTC244 views4 reactionsread 7 August 2026
Photo

Почему обвязка не панацея от галлюцинаций Есть четыре самых популярных способа поднять точность и консистентность LLM, не трогая саму модель: - Промпт-инжиниринг. Дёшево, но хрупко: новая формулировка вопроса, и результат поплыл. - Self-consistency. Генерируем пять ответов, берём большинство. Точность растёт. Счёт за токены тоже, в пять раз. - Структурный вывод с валидаторами. JSON-схема гарантирует формат, но не

👨‍💻2👍1🔥1

13 Jul 2026, 12:47 UTC266 views4 reactionsread 7 August 2026

«А чем вы отличаетесь от Битрикс24?» Слышу этот вопрос на каждой второй встрече. Ключевое: у нас GTM>>Product - прямая неразрывная связь Поэтому могу привести пару фактов из разбора 20 000+ звонков за июнь: Звонок, где менеджер зафиксировал следующий шаг с датой, доходит до следующего этапа в 80 случаях из 100. Без договорённости - в 60. Полтора раза на ровном месте. Разве Битрикс покажет вам эту разницу по каждо

🙊2👍1🤣1

9 Jul 2026, 15:10 UTC307 views4 reactionsread 7 August 2026
Photo

Проклятие последней минуты Мы оценили 20к+ B2B-звонков за июнь. Менеджеры неплохо открывают разговор: цель звонка проговаривается в 51% случаев, следующий шаг фиксируется в 52%. А финализация, когда менеджер резюмирует договорённости и проговаривает итог, есть только в 37% звонков. Ни в одной компании из выборки показатель не поднялся выше 40%. Звонок умирает в последнюю минуту. Клиент вешает трубку без общей карт

🔥2👍1🤷‍♂1

4 Jul 2026, 09:45 UTC383 views9 reactionsread 7 August 2026
File

🤣🤣🤣 Спасибо читателю за немедленное выполнение задачи)) Вопрос: "кто кого блеймил?" - остался открытым)) Есть пара фиксов, которые сделаем асап.

🤣5🔥3😍1

3 Jul 2026, 18:50 UTC326 views8 reactionsread 7 August 2026

Наш электроник сегодня обработал звонок, к которому его никто не готовил Звонит интегратор Битрикс24. Сходу ломает сценарий: цены не интересуют, я партнёр, рассказывай, есть ли у вас партнерка? Обычно на этом месте живой менеджер плывёт и начинает зачитывать заготовку или выдумывать. Электроник не поплыл. Перестроился на ходу, отработал два возражения («я вам два дня назад на почту писал, мне никто не ответил»), и

🔥42👍2

Showing the 12 most recent of 20 posts we hold for @vpofsales. 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.

Citation-graph rank

Citation-graph rank — 1,135,696 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“VP of sales” (@vpofsales), 1,741 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vpofsales.

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.