Telegram RegisterThe public register of Telegram
Telegram profile photo for 双向客服系统克隆

Channel

双向客服系统克隆

@kfxtBOT

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

275subscribers

+95 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-1001729103864
TypeChannel
Username@kfxtBOT
Created28 January 2022measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/kfxtBOT

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

1792752277 August 2026 — 180 subscribers8 August 2026 — 180 subscribers16 August 2026 — 179 subscribers24 August 2026 — 267 subscribers31 August 2026 — 268 subscribers10 September 2026 — 266 subscribers18 September 2026 — 275 subscribers7 August 202618 September 2026
7 measurements spanning 42 days, net +95. 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 165–289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 12:36275+9
10 Sept 2026, 09:59266-2
31 Aug 2026, 06:24268+1
24 Aug 2026, 09:43267+88
16 Aug 2026, 06:15179-1
8 Aug 2026, 13:01180no change
7 Aug 2026, 15:15180first reading

Engagement

5 posts held, back to 28 January 2022the 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 5 posts for this entry, the most recent from 30 March 2022. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 2 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
250.0%
👍125.0%
😁125.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 2 of the 5 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 28 January 2022 to 30 March 2022, 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

30 Mar 2022, 16:24 UTC≈1,660 viewsread 8 August 2026

如果你有多个项目都需要客服, 只要一个TG客服号就能管理多个项目的客服 🅾️简单操作、容易上手、分辨清晰 1. 科技风:极速响应零延迟,多重加密筑壁垒,安全体验一骑绝尘! 2. 实用风:操作瞬间即达,安全密不透风,极速安全超省心 。 3. 情感风:怕等待怕泄密?极速安全来守护,给你稳稳安全感 。 .................................................🖍 克隆机器人到: @Kaitongbot 在线客服: @JQRkfkfBOT

28 Jan 2022, 05:25 UTC≈1,610 views2 reactionsread 8 August 2026

⁉️很多人找我开发客服要求都是安全问题 🟰🟰🟰🟰🟰🟰🟰🟰 💯 简单、隐私、极速、安全 🟰🟰🟰🟰🟰🟰🟰🟰 建立私密群,拉入客服机器人, 只要是私密群里的用户皆可回复用户 简单隐私不繁琐, 一键开启个人专属私密空间,极速安全超放心 。 .................................................🖍 克隆机器人到: @Kaitongbot 在线客服: @JQRkfkfBOT

2

28 Jan 2022, 05:24 UTC≈1,050 views2 reactionsread 8 August 2026
Photo

中文版🇨🇳机器人客服系统操作说明: 一、先创建注册个机器人 创建克隆机器人步骤 : • 打开 @BotFather 发送 /newbot • 发送机器人的名字(可以是中文) • 发送机器人的用户名 (英文且以bot结尾) • 从 @BotFather 注册后会有api key的消息 (复制和粘贴) • 打开 @Kaitongbot 点击开始 ,充值金额,点击购买机器人发送刚才注册好的机器人的API • 克隆完成 ! 二、客服群设置 1、克隆完成后,接着自己建立个私密群,把需要负责的用户拉进群 2、在把克隆好的机器人拉进私密群就完成 3、每次回复用户的时候 都需要 【艾特的信息 回复你想回复的内容】 .................................................🖍 克隆机器人到: @Kaitongbot 在线客服: @JQRkfkfBOT

👍1😁1

Showing the 5 most recent of 5 posts we hold for @kfxtBOT. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“双向客服系统克隆” (@kfxtBOT), 275 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kfxtBOT.

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.