Channel
@dujiaoshouaiscrmy
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
7,670subscribers
-21,568 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003778009262 |
|---|---|
| Type | Channel |
| Username | @dujiaoshouaiscrmy |
| Created | Between 1 February 2026 and 3 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/dujiaoshouaiscrmy |
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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 |
|---|---|---|
| 26 Sept 2026, 04:38 | 7,670 | -4,340 |
| 17 Sept 2026, 09:40 | 12,010 | -80 |
| 15 Sept 2026, 09:56 | 12,090 | -92 |
| 13 Sept 2026, 18:01 | 12,182 | -119 |
| 11 Sept 2026, 20:17 | 12,301 | -188 |
| 9 Sept 2026, 12:40 | 12,489 | -3,483 |
| 6 Sept 2026, 08:41 | 15,972 | -3,619 |
| 4 Sept 2026, 02:22 | 19,591 | -81 |
| 2 Sept 2026, 16:48 | 19,672 | -77 |
| 1 Sept 2026, 16:44 | 19,749 | -44 |
| 31 Aug 2026, 15:05 | 19,793 | -44 |
| 30 Aug 2026, 13:04 | 19,837 | -71 |
| 29 Aug 2026, 10:12 | 19,908 | -79 |
| 28 Aug 2026, 10:32 | 19,987 | -2,210 |
| 27 Aug 2026, 07:34 | 22,197 | -5,760 |
| 26 Aug 2026, 06:26 | 27,957 | -93 |
| 25 Aug 2026, 04:04 | 28,050 | -191 |
| 23 Aug 2026, 22:17 | 28,241 | -140 |
| 22 Aug 2026, 04:18 | 28,381 | -67 |
| 20 Aug 2026, 19:57 | 28,448 | first reading |
23 posts held, back to 3 June 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 57 pages 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 23 posts for this entry, the most recent from 29 August 2026. An engagement rate over an empty window would be a number about nothing.
1,419 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎉 | 305 | 21.5% | |
| 😁 | 295 | 20.8% | |
| 🔥 | 285 | 20.1% | |
| ❤ | 278 | 19.6% | |
| 👍 | 256 | 18.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 13 of the 23 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 1,419 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 3 June 2026 to 29 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.
🔔 独角兽SCRM系统维护通知 由于 Cloudflare 官方将进行服务维护，维护期间可能对独角兽SCRM部分服务造成影响。 维护时间： 8月29日 17:00–18:00（北京时间） 预计时长： 约1小时 可能影响： 独角兽SCRM部分服务可能暂时无法正常使用 无需操作： 维护完成后相关服务将自动恢复，无需手动操作 📌 建议有重要业务安排的用户提前做好工作安排，避免维护期间影响正常业务。 感谢您的理解与支持！ 👩💼24小时人工客服：@dujiaoshouaiscrmservicer
😁23🔥15❤14🎉11👍10
🚀 独角兽SCRM 1.22.3 版本更新： 修复以下问题： 💡客户端WS粉丝昵称同步异常 💡客户端WS编辑图片后发送异常 💡客户端TG搜索聊天记录跳转异常 💡客户端LINE未读数显示及通知异常 优化及新增功能： 🔥客户端群发同步账号备注 🔥客户端顶部显示邀请码备注 🔥用户后台IP分组增加全部分组选项 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐唯一频道： https://t.me/dujiaoshouaiscrmy 🎁新用户注册后联系客服，可开启惊喜优惠！ ⚠️认准官方唯一频道页，谨防假冒诈骗!
🎉30😁18👍16🔥15❤12
🚀 独角兽SCRM 1.22.2 版本更新： 修复以下问题： 💡工单偶现账号在线状态异常 💡聊天监控偶现导出记录报错 💡客户端LINE未读数统计异常 💡客户端偶现LINE没翻译直接发送中文 优化及新增功能： 🔥邀请码工单及分享工单页面排版优化 🔥用户后台敏感行为监控增加日期筛选功能 🔥用户后台套餐IP列表支持备注及二维码连接 🔥多邀请码分享工单支持编辑已分享的社交账号 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐唯一频道： https://t.me/dujiaoshouaiscrmy 🎁新用户注册后联系客服，可开启惊喜优惠！ ⚠️认准官方唯一频道页，谨防假冒诈骗!
🔥17🎉14👍14😁14❤12
🚀 独角兽SCRM 1.22.1 版本更新： 修复以下问题： 💡LINE偶现发送中文问题 💡TG偶现启动会话失败问题 💡FB平台部分场景下无法翻译问题 💡账号异常下线，在线状态不准确问题 优化及新增功能： 🔥客户端安全及稳定性升级 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐唯一频道： https://t.me/dujiaoshouaiscrmy 🎁新用户注册后联系客服，可开启惊喜优惠！ ⚠️认准官方唯一频道页，谨防假冒诈骗!
🎉22😁19👍16❤13🔥11
🚀 独角兽SCRM 1.21.7 版本更新： 修复以下问题： 💡TG翻译发送emoji表情异常 💡偶现TG编辑消息无法发送 💡工单明细粉丝昵称显示异常 💡偶现客户端提示邀请码错误 💡LINE Business在线状态异常 💡偶现WS开启问候消息时不统计进粉 💡LINE Business工单进粉明细统计异常 优化及新增功能： 🔥客户端上线聚合翻译功能 🔥聊天监控优化在线账号排序 🔥多邀请码分享显示邀请码分组 🔥敏感词监控支持一键跳转聊天监控 🔥新用户后台UI优化工单明细选中颜色 🔥线索列表支持查看所有进粉明细及导出 🔥客户端翻译线路区分标准线路及专享线路 🔥分享工单支持自定义开关显示工单进粉总数/移除主号进粉总数 🌐 唯一频道： https://t.me/dujiaoshouaiscrmy 👩💼24小时人工客服: @dujiaoshouaiscrmservicer
🔥43🎉41❤40😁36👍24
🚀 独角兽SCRM 1.21.6 版本更新： 修复以下问题： 💡偶现工单在线状态异常 💡客户端群发对象数量异常 💡敏感词监控大小写匹配异常 💡客户端TG文字+链接消息翻译异常 优化及新增功能： 🔥分享工单二级页面增加返回按钮 🔥客户端实时翻译新增重新翻译功能 🔥后台邀请码管理页面增加数据统计栏 🔥后台客户列表增加跳转聊天监控功能 🔥后台账号管理页面增加搜索与重置按钮 🔥后台邀请码工单与账号管理页新增手机号字段 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐访问官网：https://dujiaoshouai.com 💻官网下载：https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册后联系客服，可开启惊喜优惠！ ⚠️认准官方唯一频道页，谨防假冒诈骗!
🎉34🔥32❤25👍23😁19
🚀 独角兽SCRM 1.21.5 版本更新： 修复以下问题： 💡聊天监控发送消息失败 💡客户端TG无法发送消息 💡客户端WS语音翻译失败 💡客户端TikTok偶现无法翻译 💡分享工单在线账号数量显示异常 优化及新增功能： 🔥后台新增社群列表功能 🔥客户端支持备注群昵称 🔥后台增加多工单分享功能 🔥后台IP分组支持自定义编辑 🔥聊天监控新增会话删除标记 🔥聊天监控增加消息已读状态 🔥敏感行为监控支持LINE平台 🔥客户端右侧增加粉丝统计功能 🔥敏感行为监控列表优化字段显示 🔥多用户后台账号关联底粉去重功能 🔥自定义底粉单次上传上限调整为5M 🔥工单移除主号新粉支持查看并导出详情 🔥分享工单链接【注释】支持编辑及搜索 🔥底粉管理页面单页条数上限调整为一千条 🔥敏感行为监控支持跳转聊天监控具体消息位置 🔥自定义底粉支持分组并支持工单指定底粉分组去重 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujia…
😁33👍26🔥25🎉23❤21
🚀 独角兽SCRM 1.21.4 版本更新： 修复以下问题： 💡WhatsApp工单偶现卡粉 💡客户端LINE偶现消息延迟 💡客户端部分场景下翻译失效 💡客户端TG偶现无法发送消息 💡客户端TG偶现在线状态不同步 💡客户端WhatsApp偶现自动登出 💡收款监控开启后部分场景不生效 💡聊天监控页面自动刷新会重置备注搜索项 优化及新增功能： 🔥粉丝活链增加IP访问限制功能 🔥客户端增加ALT+T反向翻译功能 🔥聊天监控增加未读消息提醒功能 🔥管理后台IP列表支持复制及导出IP 🔥客户端/管理后台客户画像功能优化 🔥工单自定义导出增加筛选时间点导出功能 🔥客户端快捷回复支持发送音频/文件等消息 🔥客户端LINE Business增加重粉标记功能 🔥客户端LINE Business所有页面内嵌客户端 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐访问官网…
👍25🎉22🔥22😁17❤16
🚀 独角兽SCRM 1.21.3 版本更新： 修复以下问题： 💡客户端WS无法复制图片 💡客户端TG输入框内容自动删除 💡客户端LINE图片窗口无法放大 💡客户端偶现登录WS初始化失败 优化及新增功能： 🔥后台邀请码管理新增数据脱敏功能 🔥自定义底粉增加批量删除功能 🔥LINE Business增加自定义底粉导入功能 🔥后台账号管理支持账号信息搜索功能 🔥客户端社媒账号平台增加一键跳转未读会话功能 🔥后台邀请码管理增加分组功能 🔥后台工单去重范围支持指定激活码去重功能 🔥后台工单去重范围支持激活码分组去重功能 🔥敏感行为监控群聊及频道名称显示优化 🔥聊天监控支持监控粉丝编辑/删除消息 🔥聊天监控支持按日期筛选聊天记录 🔥分享工单优化-支持一键复制邀请码 🔥工单移除主号后粉丝信息保留 🔥聊天监控优化-支持实时查看最新聊天记录 🔥客户端账号备注同步后台聊天监控 🔥客户端禁止发送中文开关支持独立配置 🌟新用户注册享受旗舰版 3个端…
❤28👍26🎉24😁21🔥20
🚀 独角兽SCRM 1.21.2 版本更新： 修复以下问题： 💡客户端跟进记录丢失 💡谷歌翻译线路偶现翻译乱码 💡客户端快捷回复添加图片异常 💡WhatsApp聊天监控不显示对方消息 优化及新增功能： 🔥AI翻译线路增加美式英语语种 🔥AI翻译线路增加北黎凡特阿拉伯语语种 🔥客户端顶部增加显示目前登录邀请码 🔥后台创建邀请码计数器功能默认开启 🔥分享工单页首次入粉主号信息不脱敏 🔥工单进粉详情增加重粉来源邀请码显示 🔥工单当日丝数据重置时间支持自定义设置 🔥WhatsApp敏感行为监控支持查看图片、视频等类型消息 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐访问官网：https://dujiaoshouai.com 💻官网下载：https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册后联系客服，可开启…
❤21😁18🔥17👍15🎉10
🚀 独角兽SCRM 系统安全升级通知 近期假期期间，网络环境风险有所增加，为进一步保障用户使用安全与系统稳定性，独角兽SCRM 已对系统安全防护能力进行全面升级。为用户的使用安全保驾护航。 💡 温馨提示 为了获得更稳定、流畅的使用体验，建议用户在安装或更新独角兽SCRM前，先对设备环境进行基础安全检查，并定期清理异常文件，确保客户端在安全稳定的环境下运行。 🌐 官网下载： https://dujiaoshouai.com/dujiaoshou-download 👩💼 官方客服： @dujiaoshouaiscrmservicer ⚠️ 请认准官方唯一频道页，谨防假冒诈骗！
👍15❤12🎉12😁12🔥9
🚀 独角兽SCRM 1.21.0 版本更新： 修复以下问题： 💡部分消息翻译不准确 💡聊天监控导出记录异常 💡客户端FB平台翻译失效 💡客户端WS主题切换异常 💡客户端启动TG会话加载缓慢 💡客户端TG无法点击机器人/开始按钮 优化及新增功能： 🔥后台增加社媒账号管理模块 🔥后台内控管理增加收款地址监控功能 🔥敏感行为监控支持TGA平台 🔥客户端AI回复增加开关按钮 🔥账号活链新增is.gd短链域名 🔥客户端对话管理可直接进行群发 🔥聊天监控导出HTML本地文件格式 🔥后台工单账号活链增加是否锁定IP功能 🌟新用户注册享受旗舰版 3个端口免费24小时 👩💼24小时人工客服：@dujiaoshouaiscrmservicer 🌐访问官网：https://dujiaoshouai.com 💻官网下载：https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册后联系客服，可开启惊喜优惠
🎉36😁31🔥30❤29👍23
Showing the 12 most recent of 23 posts we hold for @dujiaoshouaiscrmy. 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 24 registered channels — 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“独角兽SCRM | 翻译器 · 工单计数 · 出海社交引流” (@dujiaoshouaiscrmy), 7,670 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dujiaoshouaiscrmy.
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.