Telegram RegisterThe public register of Telegram
Telegram profile photo for 独角兽SCRM | 翻译器 · 工单计数 · 出海社交引流

Channel

独角兽SCRM | 翻译器 · 工单计数 · 出海社交引流

@dujiaoshouaiscrm

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

5,925subscribers

-5,873 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001820882228
TypeChannel
Username@dujiaoshouaiscrm
Description🦄 独角兽SCRM唯一官方频道:支持 WhatsApp/TG/LINE等12+平台多开聚合聊天,集成200+语种实时双向翻译。内置 AI智能客服、工单数据分析、粉丝计数器及多维度引流分流系统;实现全球私域流量高效转化 ✔️ 全球实时翻译 ✔️ 多账号聚合管理✔️ 粉丝计数统计 ✔️工单数据分析✔️AI 驱动私域营销 🌐 唯一官网: https://dujiaoshouai.com 💳 官方客服(唯一付款渠道): @dujiaoshouaiscrmservice 💰官方交流群: @DJSSCRMCH
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/dujiaoshouaiscrm

Topic

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 29% 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 the other topics.

Growth

5,92511,7988,861.57 August 2026 — 11,798 subscribers7 August 2026 — 11,798 subscribers8 August 2026 — 11,759 subscribers9 August 2026 — 11,723 subscribers10 August 2026 — 11,686 subscribers11 August 2026 — 11,649 subscribers12 August 2026 — 11,606 subscribers13 August 2026 — 11,588 subscribers14 August 2026 — 11,545 subscribers16 August 2026 — 11,498 subscribers17 August 2026 — 11,457 subscribers18 August 2026 — 11,412 subscribers19 August 2026 — 11,360 subscribers20 August 2026 — 11,339 subscribers21 August 2026 — 11,326 subscribers23 August 2026 — 11,301 subscribers24 August 2026 — 11,280 subscribers25 August 2026 — 11,261 subscribers26 August 2026 — 11,240 subscribers27 August 2026 — 11,211 subscribers29 August 2026 — 11,135 subscribers30 August 2026 — 11,074 subscribers31 August 2026 — 10,858 subscribers1 September 2026 — 10,713 subscribers2 September 2026 — 10,612 subscribers3 September 2026 — 10,403 subscribers4 September 2026 — 10,103 subscribers7 September 2026 — 9,675 subscribers11 September 2026 — 9,054 subscribers15 September 2026 — 8,472 subscribers27 September 2026 — 7,306 subscribers5 October 2026 — 7,085 subscribers12 October 2026 — 6,924 subscribers15 October 2026 — 6,807 subscribers18 October 2026 — 6,755 subscribers21 October 2026 — 6,735 subscribers24 October 2026 — 6,690 subscribers26 October 2026 — 6,627 subscribers29 October 2026 — 6,574 subscribers1 November 2026 — 6,088 subscribers4 November 2026 — 5,925 subscribers7 August 20264 November 2026
41 measurements spanning 89 days, net -5,873. 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 5,044–12,679 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
4 Nov 2026, 08:255,925-163
1 Nov 2026, 17:106,088-486
29 Oct 2026, 16:086,574-53
26 Oct 2026, 23:306,627-63
24 Oct 2026, 05:586,690-45
21 Oct 2026, 05:396,735-20
18 Oct 2026, 14:056,755-52
15 Oct 2026, 21:106,807-117
12 Oct 2026, 12:566,924-161
5 Oct 2026, 12:417,085-221
27 Sept 2026, 07:417,306-1,166
15 Sept 2026, 18:388,472-582
11 Sept 2026, 18:219,054-621
7 Sept 2026, 10:429,675-428
4 Sept 2026, 16:1510,103-300
3 Sept 2026, 00:2310,403-209
2 Sept 2026, 01:0410,612-101
1 Sept 2026, 03:0410,713-145
31 Aug 2026, 02:3410,858-216
30 Aug 2026, 00:5711,074first reading

Engagement

36 posts held, back to 15 April 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 41 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.56%
avg views ÷ 5,925 subscribers
Avg views / post
448
7 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
7
of 36 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. It is computed over the 1 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 October 2026
Posts held36 (15 April 2026 – 28 October 2026)
Views total3,135
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 13:05 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

Photos
149
Videos
11
Links
131

Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

12 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤650.0%
👍433.3%
🔥216.7%

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

Measured over the 36 most recent posts we hold, published 15 April 2026 to 28 October 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

Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

28 Oct 2026, 09:41 UTC333 viewsread 4 November 2026
Photo

🚀 独角兽SCRM 1.22.9 版本更新: 修复以下问题: 💡MAC客户端偶现不翻译 💡WhatsApp无法发送消息 💡TikTok部分场景下翻译失效 💡Telegram偶现计数统计异常 💡WhatsApp客户画像昵称丢失 💡WhatsApp聊天监控消息不同步 💡客户端WhatsApp账号显示错乱 💡客户端TG界面语言无法自定义设置 💡客户端WhatsApp发送消息输入框残留 💡WhatsApp无法发送图片、视频、文件 优化及新增功能: 🔥设备锁增加白名单模式 🔥客户端翻译优化标点符号 🔥客户端新增单设备登录功能 🔥用户后台修改密码支持符号输入 🔥用户后台购买套餐支持余额抵扣 🔥客户端Facebook增加前进后退按钮 🔥邀请码管理支持重粉标识自定义开关 🔥LINE账号活链更改为分享个人名片链接 🔥用户后台工单明细优化-支持隐藏主号备注及移除主号新粉数 🌟新用户注册享受旗舰版 3个端口免费24小时 👩‍💼24小时人工客服:@…

26 Oct 2026, 08:16 UTC319 viewsread 4 November 2026
Photo

⚠️ 独角兽 SCRM 旧版本停用通知 尊敬的独角兽 SCRM 用户: 为保障系统的稳定性与正常使用体验,自 2026 年 11 月 1 日起,独角兽 SCRM 将不再支持 1.22.5 及以下版本。 请您尽快将客户端更新至最新版本,以免影响您的正常使用及日常工作安排。 📥 最新版本下载: https://dujiaoshouai.com/dujiaoshou-download 💬 官方在线客服: @dujiaoshouaiscrmservice 对于此次版本调整给您带来的不便,我们深表歉意,感谢您的理解与支持! 如有任何疑问或遇到更新问题,请及时联系官方在线客服,我们将竭诚为您提供协助。 ❤️ 感谢您一直以来对独角兽 SCRM 的信任与支持!

12 Oct 2026, 06:15 UTC669 viewsread 4 November 2026
Photo

🚀 独角兽SCRM 1.22.8 版本更新: 修复以下问题: 💡分享工单导出数据无反应 💡客户端跟进记录显示异常 💡LINE business进粉统计异常 💡客户端WS无法发送图片、文件 🌟新用户注册享受旗舰版 3个端口免费24小时 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice 🌐访问官网:https://dujiaoshouai.com 💻官网下载:https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册后联系客服,可开启惊喜优惠! ⚠️认准官方唯一频道页,谨防假冒诈骗!

12 Oct 2026, 03:03 UTC550 viewsread 4 November 2026

✅ 独角兽SCRM维护结束通知 尊敬的用户: 本次系统紧急维护已完成,服务已恢复正常,感谢大家的耐心等待与理解! 📌 温馨提示 • 请重新登录用户后台,检查账号在线状态是否正常。 • 如遇到无法登录、在线状态异常等问题,请及时联系客服处理。 感谢大家的支持与配合! 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice

11 Oct 2026, 05:01 UTC451 views0 reactionsread 4 November 2026
Photo

🔔 独角兽SCRM服务器升级维护公告 为进一步加强服务器安全防护,提升系统稳定性,我们计划于以下时间进行服务器升级维护: ⏰ 维护时间: 北京时间 10月12日(周一)10:00–11:00 ⚠️ 影响范围: 维护期间,用户后台及客户端可能出现暂时无法访问、连接异常等情况。 📌 温馨提示: • 请提前做好工作安排,避免影响正常业务。 • 维护期间建议暂停打粉、接粉等相关操作。 感谢大家的理解与支持! 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice

10 Oct 2026, 08:18 UTC413 viewsread 4 November 2026

✅ 独角兽SCRM维护结束通知 尊敬的用户: 本次系统紧急维护已完成,服务已恢复正常,感谢大家的耐心等待与理解! 📌 温馨提示 • 请重新登录客户端,检查账号在线状态是否正常。 • 如仍遇到无法登录、在线状态异常等问题,请及时联系客服处理。 感谢大家的支持与配合! 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice

10 Oct 2026, 07:32 UTC400 viewsread 4 November 2026
Photo

🚨 独角兽SCRM紧急维护公告 尊敬的用户: 目前系统服务出现异常,技术团队已介入,正在紧急排查与处理中。由此给您带来的不便,敬请谅解。 ⚠️ 当前影响范围: • 客户端暂时无法登录 • 部分账号在线状态显示异常 🛠 处理进展: 技术团队正在全力处理,恢复时间暂未确定。请大家留意后续公告,具体恢复情况将另行通知。 感谢大家的理解与支持! 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice

30 Sept 2026, 03:12 UTC569 viewsread 4 November 2026
Photo

🚀 独角兽SCRM 版本更新: 优化及新增功能: 🔥用户后台增加登录日志 🔥用户后台过期IP支持批量删除 🔥用户后台登录逻辑优化:默认单设备登录,若需多设备登录需开启谷歌验证 🌟新用户注册享受旗舰版 3个端口免费24小时 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice 🌐访问官网:https://dujiaoshouai.com 💻官网下载:https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册后联系客服,可开启惊喜优惠! ⚠️认准官方唯一频道页,谨防假冒诈骗!

23 Sept 2026, 14:00 UTC615 viewsread 4 November 2026
Photo

🔔 独角兽SCRM服务器升级通知 为进一步提升服务器安全性与防护能力,我们计划于⏰北京时间 9月25日(周五)10:00–10:30 进行服务器升级维护。 ⚠️ 升级期间可能影响 升级过程中,用户后台、客户端将会出现暂时无法访问、连接异常等情况。 为避免业务数据受到影响,请各位用户提前做好工作安排,升级期间建议暂停打粉、接粉等相关操作,待升级完成后再恢复正常使用。 📌 升级完成后重要提醒 服务器升级完成后,建议客户端内的 Telegram(TG)账号重新新建会话并登录,尽量不要继续使用升级前的旧会话。 若继续使用旧会话登录,可能出现: • 聊天监控消息不同步 • 工单进粉/计数统计不准确 • 部分会话数据同步异常 建议升级完成后统一重新建立 TG 会话,以确保后续数据同步及统计正常。 由此给您带来的不便,我们深表歉意,感谢您的理解与支持! 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice

23 Sept 2026, 13:15 UTC461 views1 reactionsread 4 November 2026
Photo

🚀 独角兽SCRM 1.22.6 版本更新: 修复以下问题: 💡客户端偶现闪退 💡客户端WS偶现白屏 💡客户端WS偶现自动登出 💡客户端WS发生数据库错误 💡客户端ins消息通知提醒异常 💡用户后台IP续费没有自动打折 💡客户端LINE偶现进粉统计异常 💡客户端LINE点击发送文件没反应 💡客户端WS偶现翻译后文本留白过多 💡客户端偶现翻译失败、翻译一半问题 💡客户端群发图文消息文本换行格式丢失 💡用户后台账号套餐变更后自动退出登录 💡客户端首页账号数与工单账号数不一致 💡WS发送动态后聊天监控会多出一个聊天会话 💡多邀请码分享显示的账号数与实际账号数不符 💡客户端偶现开启禁止发送中文后仍会发送中文 💡客户端LINE账号异常离线后工单在线状态不同步 优化及新增功能: 🔥用户后台增加新手引导教程 🔥客户端跟进记录支持彻底删除 🔥客户画像昵称输入字数增加上限 🔥邀请码管理增加设置邀请码到期时间 🔥聚合翻译记录上一次选择的语言配置 …

🔥1

18 Sept 2026, 11:31 UTC528 views1 reactionsread 4 November 2026
Photo

⚠️【独角兽安全提醒】 随着 AI 工具快速发展,网络攻击的自动化程度和攻击效率也在不断提升,近期勒索病毒、木马程序、恶意文件等安全风险明显增加,已有不少企业因此遭受数据泄露、账号被盗及勒索威胁。 为了保障您的账号、电脑及业务数据安全,请务必做好以下安全防护: 1️⃣ 安装安全防护软件 建议安装并保持开启 360、火绒、卡巴斯基 等安全防护软件,定期进行病毒查杀。 2️⃣ 开启谷歌二级验证(2FA) 建议在独角兽用户后台开启 谷歌二级验证功能,提升账号登录安全性,降低账号被盗风险。 3️⃣ 关闭 Telegram 自动下载文件 建议关闭 TG 的自动下载文件功能,避免群聊、私聊中的未知文件被自动下载至电脑。 4️⃣ 开启数据加密功能 如有更高的数据安全需求,可联系客服开启 数据加密功能。功能开启后,相关数据将进行加密保护,进一步提升数据存储与使用过程中的安全性。 🔐 电脑安全无小事,安全防护绝不能懈怠! 请勿随意点击…

🔥1

11 Sept 2026, 11:21 UTC593 views1 reactionsread 4 November 2026
Photo

🚀 独角兽SCRM 1.22.5 版本更新: 修复以下问题: 💡客户端LINE偶现发送中文 💡客户端AI回复偶现翻译失败 💡工单进粉明细时间排序异常 💡客户端TG偶现等待网络链接 💡LINE群发选择标签后没有生效 💡WS修改粉丝昵称聊天监控没同步 💡聊天监控无法通过账号备注进行搜索 💡客户端新建TG会话首次登录卡在进度条 💡客户端TG点击置顶消息会自动弹到底部 优化及新增功能: 🔥账号活链分配逻辑优化 🔥用户后台首页数据优化 🔥客户端多开子用户上限提高至20个 🔥用户后台增加推广返佣提现管理功能 🔥客户数据导出优化-按查询的结果导出 🌟新用户注册享受旗舰版 3个端口免费24小时 👩‍💼24小时人工客服:@dujiaoshouaiscrmservice 🌐访问官网:https://dujiaoshouai.com 💻官网下载:https://dujiaoshouai.com/dujiaoshou-download 🎁新用户注册…

❤1

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

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“独角兽SCRM | 翻译器 · 工单计数 · 出海社交引流” (@dujiaoshouaiscrm), 5,925 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/dujiaoshouaiscrm.

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.