然后第二天在回复一句,您好,您这边还没有添加我们顾问老师吗,这样子就可以了 可以一个视频录制完所有粉聊天页面
Channel
江海项目教学
@jhzhila
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
348subscribers
-25 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 | -1001850907212 |
|---|---|
| Type | Channel |
| Username | @jhzhila |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/jhzhila |
Topic
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 15:19 | 348 | -5 |
| 2 Oct 2026, 09:19 | 353 | -8 |
| 17 Sept 2026, 10:40 | 361 | -4 |
| 23 Aug 2026, 06:24 | 365 | -6 |
| 16 Aug 2026, 18:24 | 371 | -2 |
| 8 Aug 2026, 06:18 | 373 | no change |
| 7 Aug 2026, 18:34 | 373 | first reading |
Engagement
17 posts held, back to 16 January 2025 — 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 17 posts for this entry, the most recent from 7 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 09s
- Average length
- 32s
Measured directly from 4 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
18 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 14 | 77.8% | |
| 👍 | 4 | 22.2% |
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 7 of the 17 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 16 January 2025 to 7 November 2025, 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
钉钉话术单交单第一天发送我给你的一个文字和一个图片 发完成截图交单 客户昵称: 客户号码: 顾问钉钉号: 交单格式 通过下,不聊八卦只聊涨停。 在吗,有事咨询麻烦通过下。 你好,有事咨询你,麻烦通过下。 就这个添加的话术,3选1
❤2
01.02.03. 幼师 美甲师 女大 一个人 个体 可 文字可换
素材 小区楼,两张图片 发布抖音选择两张图片 第一张上面加三个标签 第一个 零二 第二个 女大 第三个 可 标题 ❤️ 话题#日常生活 你们发布。40分钟后能加热就算单。我们会自己检查。然后给你们简介文案。把简介改了就行。 简介文案 不一样的我 @我们得抖音号 50一单。 预付一半。 第二天,我们查单。结算另一半。 (想第二天继续做单得。不要删除视频。)
❤5
头像改上面的👆一定要换头像换微信呢称 微信昵称改:小牛客服 添加好友验证消息话术: 您好,请你尽快通过 我是 小牛客服通 知 员 您好,(数据后面的名字) 您好,有事通知 您好,请你尽快确认 以上话术都可以用, 每加2个人换一下话术【防止微信屏蔽】 必须严格按照添加好友话术,否则算无效单 通过之后发个一张图片一个链接名片就可以 结账前不能换头像昵称删好友 撤回消息直接扣 注意:头像和微信名必须改好,以上发现不对立马改正,不对算无效5-10分钟添加一个,通过后发话术图过去3分钟后录屏交单给我
❤3
左面安卓教程!!右面苹果教程!! 安卓不要显示有qq分享,按照教程去生成收藏链接,不要直接发链接出去!! 看链接生成方法!内容仅供参考
交单模板!录屏必须要点开名片看一下 客户手机号: 客户微信号: 客户微信名: 做单微信号: 点击👆即可复制上面内容
❤1👍1
添加好友教程
❤1
话术单教学
结账时间统一为晚上十一点左右
Channel name was changed to «江海项目教学»
也可以拉群之前 提前把客户信息资料发给 @jhjh44
Showing the 12 most recent of 17 posts we hold for @jhzhila. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“江海项目教学” (@jhzhila), 348 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/jhzhila.
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.