// growth
Telegram Community and Channel Management
One thing this service cannot do on Telegram is stop a message from being posted. There is no moderation queue and no pending state: a message is live the second it is sent, and everything here is built around that. A join gate decides who is in the room, and a bot removes what it can recognise within seconds. A person on cover handles the judgement neither of those can make. Tuning the gate and staffing the clock are the daily work, not a content calendar.
Groups and channels both belong to this page. Discord servers have their own page. Reddit and public forums have a third. The parent community page holds the strategy, staffing model and reporting above all three. Paid promotion to fill the room is a different service again.
A channel and a group are different products
Briefs use the two words interchangeably, and they solve opposite problems.
A channel is one-to-many. Only admins post, subscribers read, and subscribers cannot see each other. It is a broadcast surface for releases, incidents and announcements. Quiet by design.
A group is conversation. Everyone posts, everyone sees everyone, and the volume is whatever the members make it. Support happens here. So does the abuse.
Most products want both, wired together. A channel for what you say, a linked discussion group for what people say back, one rule about which goes where. Skip that and you get a channel nobody opens, or a group where your outage notice scrolls out of sight before anyone reads it.
There is no thread, so context dies in the scrollback
Telegram has replies. It does not have threading. Three conversations interleave in one column, and a question asked at the top of the hour is unreadable by the end of it. So the same question is asked over and over, and the answer cannot be found by the next person who needs it. A moderator coming on shift has to read the room instead of picking up a queue.
We work against that instead of pretending it away. An answers bot for the questions that repeat, and pinned posts short enough to be read. Then a weekly digest, so the repeated answers can move into your documentation.
Anti-spam tuning is the job, not a setting
Telegram attracts a specific and unrelenting kind of abuse. Accounts that copy an admin’s name and photo. Scripts that harvest new joiners and message them privately within seconds. Forwarded-message floods, and a wallet address dropped into every conversation that mentions payment. A default configuration does not survive contact with it.
Tuning means choosing a position on one tradeoff. Tighten the gate and you stop the scams and also swallow a real customer’s first message. Loosen it and the room learns that anything posted there might be bait. Neither error is free, which is why the number reported here is members retained alongside spam removed without losing real posts. Either one alone can be won by sacrificing the other.
What goes in: a join gate that costs a person a second and a script real work. A probation window on links and media for new accounts. Bait rules written for your category, and an impersonation check against the people who genuinely hold admin. Then we watch the false positives weekly and loosen what needs loosening.
Admin rights are coarse, so the rota has to be precise
Telegram’s permission model is a short list of toggles per admin. Delete messages, restrict members, pin, invite, add other admins. Each one applies to the whole group. No per-topic role matrix, no moderator who is strong in one corner of the room and weak in another. Handing someone the right to clear spam hands them most of the rights that matter.
So the human process is the control. A written register of who holds which toggle and why, with rights removed the day somebody leaves the rota. A bot does the routine deletions, so fewer people need the ban right at all.
We write the bot instead of renting one
The Bot API is capable, and its model is not Discord’s. A bot receives updates through a webhook and needs privacy mode disabled before it sees ordinary group messages. It has to be an admin to remove anything, and it cannot read what was posted before it arrived. Off-the-shelf moderation bots are written for the general case.
We build the product and the demand for it, so the engineering is in scope. An impersonation detector. A report button that drops a flagged message into a private admin group in one tap. A bridge into whatever ticket system your support team runs, and the weekly digest. It ships as source into a repository you own. The day the engagement ends, it keeps running.
Cover, because nothing queues
Nothing queues, so cover has to be a rota. The only thing standing between a scam post and your members is whether somebody is in the room at that hour. The rota names its windows and sets out which decisions a moderator must not take alone. It carries a handover note each time the room changes hands.
Asked for often, refused every time
We do not run pump groups. No paid-shill rooms, no hype written under sock accounts, no bought members to make the online count look healthy. That count is the one number here which is trivially faked and worthless.
We will not mass-message a list harvested from somebody else’s group. And we will not moderate a room whose purpose is to move the price of a token instead of helping people use a product. What those two refusals protect is the only thing a group has that a buyer can verify from outside. The people posting in it are real, and they are there for the product.
What you get
- A group and channel architecture, with a written rule for what is broadcast, what is conversation, and where each one lives
- An admin rights register naming every person and bot that holds each toggle, and what is removed the day someone leaves the rota
- The anti-spam stack configured and then tuned against your own traffic, covering join gate, new-account restrictions, link and bait rules, impersonation checks
- A moderation rota with named cover windows, an agreed escalation path, and a written handover at the end of every shift
- The bots we write for your group, deployed and handed over as source in a repository you own, with the token in your secret store
- An announcement rhythm for the channel and a pinned-message set for the group, both short enough to actually be read
- A weekly report of what was removed, what was escalated, and the questions asked often enough to belong in your documentation instead
How it runs
- 01
Read the scrollback first
Before a single setting changes we read back through the group and the channel. What the members actually use it for, who the unpaid regulars answering questions are, and which of the current rules are load-bearing. Communities punish a moderator who arrives and starts deleting.
- 02
Separate broadcast from conversation
The channel becomes the place you speak. The linked discussion group becomes the place people speak back, with one written rule about which goes where. Most of the noise complaints we inherit are one surface being asked to do both jobs at once.
- 03
Tune the gate against real traffic
The join gate, the new-account restrictions and the bait rules go in, and then we watch what they catch for a fortnight. Every rule is scored on what it blocked and on the real first posts it swallowed. Anything with a bad ratio gets loosened, and never defended.
- 04
Run the cover and hand the shift over
Named windows, a moderator who is actually present in them, and a handover note so the next person starts informed instead of scrolling. Nothing queues on Telegram, so the only thing between a scam post and your members is whether somebody is in the room.
- 05
Report what the group is asking for
The questions that repeat are a product and documentation signal, on top of the moderation volume. Each week we send what was removed, what was escalated, and the answers that should stop living in a moderator's head.
Questions we get asked
- Should we run a group, a channel, or both?
- Usually both, wired together. A channel is a one-way broadcast surface that stays quiet and readable, which is where releases, incidents and announcements belong. A group is conversation, which is where support and everything else happens. Running only a group means your outage notice scrolls out of sight. Running only a channel means members have nowhere to reply, so they go and organise somewhere you cannot see.
- How is this different from your Discord page?
- Different platform, different mechanics, different failure modes. Discord gives you threads, a role and permission matrix, and rooms you can partition. Telegram gives you one column of scrollback and a short list of coarse admin toggles that apply to the whole group. It also brings a far heavier stream of scam and impersonation traffic. The daily work is not the same work, so it is not the same page.
- We are a crypto project. Will you take the group?
- If there is a real product and real users, yes. A support-heavy group full of people holding a token is still a community, and it still needs moderating. What we will not do is run a promotion room. No pump groups, no paid shilling under accounts that pretend to be members, no bought membership to make the room look busy. If the group exists to move a price, we are the wrong agency for it.
- Can bots solve the spam on their own?
- They do the volume, not the judgement. A bot removes the obvious floods, enforces the new-account restrictions and flags likely impersonation faster than any human can. What it cannot decide is whether a borderline first post from a nervous new customer is a scam or a sale. Every anti-spam configuration is a tradeoff between what it blocks and what it silences. A person reviews that tradeoff against your own traffic.
- Do you take over our existing group or start a new one?
- We take over the existing one in almost every case. The members, the history and the search results are already there. Asking a community to move platforms or rooms loses the regulars who make the place worth joining. A new group is the right answer in one case. The current one has been harvested by scam accounts so thoroughly that its member list is worth more to spammers than to you.
- Who owns the group and the bots when we stop working together?
- You do, throughout. The group and channel stay under your account, with your people holding the owner rights. We hold admin rights that you can revoke in one action. Anything we write ships as source into a repository you control, with credentials in your secret store. The handover is not an event at the end. It is how the work is set up from the first week.
- Can you cover our members' time zones?
- We tell you which windows we can staff before you sign anything. They are named in the rota, instead of coverage being described in the abstract. If your members are most active in a window we cannot cover well, we say so and we plan for it. Tighter automated restrictions during that window, a clear escalation path, and a visible note in the group about when a human is next on. Quiet hours that nobody warned you about are how a group gets hollowed out.