Channel
@close_academy
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
27subscribers
+0 since we began measuring on 16 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004309860342 |
|---|---|
| Type | Channel |
| Username | @close_academy |
| Created | 1 August 2026 — measured — dated from the channel’s first post |
| First recorded | 16 September 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/close_academy |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 15:20 | 27 | -1 |
| 17 Sept 2026, 23:00 | 28 | +1 |
| 16 Sept 2026, 15:22 | 27 | no change |
| 16 Sept 2026, 14:47 | 27 | first reading |
13 posts held, back to 1 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 6 September 2026. An engagement rate over an empty window would be a number about nothing.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 1 of the 13 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 1 August 2026 to 6 September 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.
❌ «هر جور شما راحت باشید.» به‌ظاهر محترمانه‌ست. اما در فروش، خیلی وقت‌ها ترجمه‌ش میشه: «من دیگه نمی‌دونم قدم بعدی چیه؛ خودت تصمیم بگیر.» فروشنده حرفه‌ای قرار نیست مشتری رو تحت فشار بذاره؛ اما قرار هم نیست رهبری مکالمه رو رها کنه. به‌جاش بگو: ✅ «با توجه به چیزی که گفتید، پیشنهاد من اینه که اول این گزینه رو بررسی کنیم.» احترام ≠ منفعل بودن فروشنده باید محترم باشه، اما هدایت‌گر هم باشه. @close_academy
❤2
Photo, posted without a caption
🎯 اگر فروشنده نرم‌افزاری، اینجا قراره به کارت بیاد! فروش نرم‌افزار فقط بلد بودن محصول نیست؛ باید بلد باشی سؤال درست بپرسی، نیاز واقعی مشتری رو پیدا کنی، دمو رو درست برگزار کنی و در نهایت قرارداد رو ببندی. من در Close Academy قراره از تجربه‌های واقعی فروش بگم؛ از دموهای بی‌نتیجه تا مذاکره، اعتراض قیمت، پیگیری و بستن قرارداد. بدون تئوری‌های تکراری؛ فروش واقعی، بدون شعار. 🎯 📌 برای آموزش‌ها و محتواهای جدید، از اینجاه…
Channel name was changed to «Close_academy»
نکته آخر و مهم‌ترینش: ۳. دمو را بدون «قدم بعدی» تمام نکن! یکی از بدترین پایان‌های دمو: «خب، اگر سوالی داشتید در خدمتیم.» یعنی توپ رو انداختی زمین مشتری و منتظر موندی خودش برگرده! دموی حرفه‌ای باید با قدم بعدی مشخص تموم بشه: «اگر این راهکار مورد تأییده، قدم بعدی رو برای قرارداد و اجرا مشخص کنیم.» یادت باشه: دمو پایان فروش نیست؛ شروع تصمیم مشتریه. @close_academy
نکته دوم: ۲. قیمت را با ترس اعلام نکن! وقتی قبل از گفتن قیمت مکث می‌کنی و می‌گی: «البته قیمت ما یکم بالاتره ولی...» خودت داری به مشتری می‌گی: «قیمت بالاست!» قیمت رو شفاف و محکم بگو؛ بعد ارزشش رو بفروش. 🎯 @close_academy
نکته اول: ۱. قبل از دمو، درد مشتری رو پیدا کن! 🎯 اشتباه رایج فروشنده اینه که قبل از فهمیدن مشکل مشتری، می‌ره سراغ نمایش امکانات. مشتری نمی‌پرسه «چند تا قابلیت داری؟» می‌پرسه: «کدوم مشکل منو حل می‌کنی؟» @close_academy
3 نکته قبل از جلسه دمو که حتما باید بدونی! @close_academy
اگر این ۳ نکته رو زودتر می‌فهمیدم، احتمالاً خیلی از قراردادهایی که از دست دادم، امروز بسته شده بودن. نه به خاطر اینکه محصولم بد بود؛ نه به خاطر اینکه مشتری پول نداشت. اشتباه از جایی شروع می‌شد که فکر می‌کردم فروش یعنی معرفی بهتر محصول. اما فروشنده حرفه‌ای می‌دونه: مشتری امکانات نمی‌خره؛ مشتری نتیجه می‌خره. این ۳ نکته، ساده به نظر میان؛ ولی می‌تونن تفاوت بین یک دموی بی‌نتیجه و یک قرارداد بسته‌شده باشن. از اینجا …
دمو می‌دی، اما درد مشتری رو نمی‌فهمی! مشتری دنبال امکانات نرم‌افزار نیست. دنبال اینه که بدونه: «این نرم‌افزار کدوم مشکل من رو حل می‌کنه؟» اگر قبل از نمایش امکانات، درد مشتری رو نشون ندی، دموت فقط یک معرفی محصوله؛ نه یک جلسه فروش. 💡 قاعده طلایی: اول مشکل، بعد راه‌حل. ما رو در اینستاگرام https://www.instagram.com/close.academy?igsh=MWJzbDVkMTN4M2lvbw%3D%3D&utm_source=qr در بله https://web.bale.ai/chat?uid=524…
Channel name was changed to «Close.academy»
Channel photo updated
Showing the 12 most recent of 13 posts we hold for @close_academy. 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.
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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Close_academy” (@close_academy), 27 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/close_academy.
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.