11 Mar 2026, 11:06 UTC≈25,700 views23 reactionsread 7 August 2026
================== ‼️使用指南 Q&A ================== 如何添加机器人？ 如何设置客服人员？ 如何设置客服群？ 如何回复消息？ 如何封禁/恢复/查询用户？ 如何设置自动回复？ 如何给所有用户发送广播？ 如何设置欢迎消息？
❤22👍1
Channel
【快搜双向】官方频道
@kuaiChat
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,615subscribers
+3 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 | -1003858488014 |
|---|---|
| Type | Channel |
| Username | @kuaiChat |
| Created | 9 March 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/kuaiChat |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 15:04 | 1,615 | +4 |
| 9 Aug 2026, 17:51 | 1,611 | -2 |
| 7 Aug 2026, 04:31 | 1,613 | +1 |
| 7 Aug 2026, 01:16 | 1,612 | first reading |
Engagement
11 posts held, back to 9 March 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pagesof 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 11 posts for this entry, the most recent from 11 March 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
74 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 90.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 67 | 90.5% | |
| 🌚 | 2 | 2.70% | |
| 😁 | 2 | 2.70% | |
| 👍 | 1 | 1.35% | |
| 👏 | 1 | 1.35% | |
| 🔥 | 1 | 1.35% |
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 10 of the 11 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 74reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 9 March 2026 to 11 March 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
11 Mar 2026, 10:57 UTC≈25,400 views8 reactionsread 7 August 2026
Photo
如何设置欢迎消息？ 在机器人设置页面点击欢迎消息，并按照提示设置即可，支持单个图文描述或单个视频描述或纯文本。
❤7🔥1
11 Mar 2026, 10:57 UTC≈24,000 views5 reactionsread 7 August 2026
Photo
如何给所有用户发送广播？ 在机器人设置页面点击广播列表，并按照提示添加广播后，可先查看预览，最后点击确认发送即可全员广播。
❤5
11 Mar 2026, 10:57 UTC≈16,900 views3 reactionsread 7 August 2026
Photo
如何设置自动回复？ 在机器人设置页面点击自动回复按钮，并按提示添加规则，支持三种匹配方式。 • 包含：用户消息包含关键词即触发 • 完全等于：用户消息与关键词完全相同才触发 • 正则：按正则表达式匹配
❤3
11 Mar 2026, 10:57 UTC≈13,900 views4 reactionsread 7 August 2026
Photo
如何封禁/恢复/查询用户？ 1. 引用消息并发送命令 /ban 可封禁用户 2. 引用消息并发送命令 /recover 可解除封禁 3. 引用消息并发送命令 /info 可查询用户基础信息
❤4
11 Mar 2026, 10:57 UTC≈11,600 views6 reactionsread 7 August 2026
Photo
如何回复消息？ 1.用户发送消息后，消息会被转发给 客服群 以及 客服人员 2.客服群内可点击需回复的用户选项卡，直接回复消息 3.客服人员私聊框内需引用消息进行回复 4.发出的消息可重新编辑，用户端自动更新，避免发错消息的尴尬。
❤5👏1
11 Mar 2026, 10:57 UTC≈11,000 views8 reactionsread 7 August 2026
Photo
如何设置客服群？ 1. 创建一个群聊并添加你的双向机器人 2. 开启群话题模式，保存 3. 将你的双向机器人提升为管理员，并确保开启了 编辑话题 权限，如果没有该权限选项，说明当前群没有开启话题模式。 4. 设置成功后，点击群内弹出的 设置为客服群 按钮。或者复制群ID后，在后台手动添加该群。 5. 在后台客服群列表内，手动打开该群的开关。
❤8
11 Mar 2026, 10:56 UTC≈11,500 views7 reactionsread 7 August 2026
Photo
如何设置客服人员？ 1.在机器人配置页面，点击设置客服 2.选择设置客服人员 3.选择设置本账号为客服 4.若需添加其它账号为客服，点击添加客服，并输入对方账号ID。使用前请确保对方账号已关注机器人。账号ID可通过 @userinfobot 获取
❤5🌚2
11 Mar 2026, 10:56 UTC≈10,500 views2 reactionsread 7 August 2026
Photo
如何添加机器人？ 1. 在 @BotFather 创建一个机器人并复制token 2. 在快搜双向机器人页面，点击添加机器人，并输入token
😁2
11 Mar 2026, 10:54 UTC≈247,000 views8 reactionsread 7 August 2026
Photo
🎉 【快】产品发布公告｜【双向机器人】正式上线 快搜正式推出【双向机器人】👀。 该机器人用于在用户与客服之间进行消息转发，能够帮助 被限制私聊的用户顺利联系你，同时也为团队提供 高效的营销与客服管理工具。 机器人支持 个人或多人协作使用，功能完善、操作简单，并提供多项 多数同类产品没有或需要付费才能使用的功能，且完全免费开放使用，欢迎体验。 核心优势： 1️⃣ 完全免费 所有核心功能均免费开放使用。 2️⃣ 消息支持编辑 已发送消息仍可编辑，方便修正内容或补充信息。 3️⃣ 多客服支持 支持多客服协作，并可在 话题群内实现一对一回复，提高客服效率。 4️⃣ 多模式自动回复 支持关键词、规则匹配及 正则表达式自动回复，灵活满足不同场景。 5️⃣ 图文广播功能 支持向所有用户 一键发送图文消息广播，方便营销推广。 6️⃣ 超时未回复告警 当用户消息 长时间未得到回复 时，可通过邮件提醒，避免漏单。 7️⃣ 快捷用…
❤8
9 Mar 2026, 15:49 UTCviews —
Channel created
Showing the 11 most recent of 11 posts we hold for @kuaiChat. 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 — 153,282 of 1,183,361entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“【快搜双向】官方频道” (@kuaiChat), 1,615 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kuaiChat.
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.