Telegram CRM for agencies: client and KOL relationships that outlast the account manager

Nobody chose Telegram as an agency operating system. The clients chose it, and the agency followed. Telegram passed a billion monthly users in 2025, and in several markets it is closer to the default internet than to one app among many: Russia counted 90.6 million monthly users in January 2025 and 105 million by November, 51% of Ukrainians name it their main news source (an Ipsos study put it at 62%), and in Uzbekistan it reaches 76% of internet users.

What that looks like inside an agency depends on the kind of agency. A crypto or web3 marketing agency runs the client's launch from an “Agency x Project” group, coordinates with the client's community team in another, and keeps its KOL roster in DMs. A KOL or influencer agency negotiates rates, sends briefs, approves copy, and collects payment wallets almost entirely in private chats. A community management agency moderates client groups that can hold up to 200,000 members. A growth or performance agency ends up in Telegram because the founder answers there within minutes and answers email within days. A launch PR agency coordinates embargoes and media timing in a small group with the client's comms lead. And a market-entry agency working in the CIS or Central Asia simply meets the market where it is.

There is a channel risk too. Russia restricted Telegram and WhatsApp calls in August 2025 and later confirmed a partial block of both. An agency whose entire client history exists only inside one app is exposed to whatever happens to that app in that market.

None of this makes Telegram the problem. It is where the clients, the KOLs, and the communities are, and an agency that refuses to work there loses the account. The problem is that nothing is writing it down: the agency's knowledge of every client lives in the Telegram accounts of the people who do the work.

Agencies lose people constantly. Media agency staff turnover has hovered around 30% a year, which means a mid-sized agency replaces several account managers every year as a matter of routine. In an email agency that is an IT ticket: the departing person's mailbox sits on the company's domain, and an admin hands it to the replacement.

In a Telegram agency, there is usually no mailbox to hand over. The account manager signed up with their own phone number. They created the client group from their own account, so they may be its owner. The KOL DMs, the quote a partner sent at midnight, and the voice note where the founder approved the campaign budget are all on their phone. When they leave, the agency keeps the contract and loses the room where the work happened.

The law has an opinion about whose contacts these are. In Hays v Ions [2008] EWHC 745, a UK court ordered a former employee to disclose the LinkedIn contacts he had built while employed: contacts made for the business can be the business's information. Rules differ by country and contract, and this is not legal advice. But the practical problem comes before the legal one. Even an agency entitled to the record usually doesn't have it, because the record was never kept anywhere except one person's account.

Then there is the handover clock. Suppose your account manager on a token launch resigns on a Friday and their last day is the following Wednesday. The client group was created from their account, so you need ownership moved to an agency account. Telegram's ownership-transfer rules typically require two-step verification to have been enabled for at least seven days and a session at least 24 hours old. If they turned on two-step verification on Monday to prepare the handover, ownership cannot move before they are gone. The lesson is boring and important: set up the accounts that will own client groups correctly on day one, not on the last day.

One more slow failure: Telegram deletes accounts after 18 months offline by default. An agency that “keeps” a former employee's account in a drawer and never opens it can lose that account to the default setting.

Here is a handover that looks fine and isn't. A senior account manager leaves; the agency adds a new account manager to the “Agency x Project” group the same day; the client is told, warmly, that nothing will change. The new account manager opens the group and sees nothing before today.

Telegram groups have a setting called chat history for new members. When it is set to hidden, someone who joins never sees the messages from before they joined, and flipping the setting to visible later does not bring those messages back for them. Telegram closed the bug report as expected behavior. So the original brief from March, the KPI numbers the client agreed in the second month, the founder's approval of the launch thread, and the list of KOLs the client vetoed are all invisible to the person now responsible for them.

What agencies do next is predictable. The new account manager asks the client to re-send the brief, which tells the client the agency lost it. Or they ask the departed colleague for screenshots, which works once and depends on goodwill. Or they guess, and re-propose a KOL the client already turned down.

The real fix is for the record to exist outside the group, captured while the work happened. With Pantheon, that means the account that sat in the group was connected while it was there, so the history is on the record when the next person picks up the client. Be clear about the limit: Pantheon backfills from conversations already on the connected account. If an account never saw a message because history was hidden when it joined, no tool working from that account can show it. That is a reason to connect the account that owns the client relationship early, and to keep history visible in the groups your agency runs.

Telegram's limits are generous for a person and tight for an account manager who sits in client groups, KOL groups, partner groups, and the client's community. Most agencies meet them in this order.

The 501st group. A free account can join 500 channels and supergroups; Premium raised that to 1,000. An account manager who covers eight clients, each with a war room, a community, an announcements channel, and a dozen KOL and partner groups, gets there faster than anyone expects. At the cap, they start leaving old groups to join new ones, and the history of a client from last year goes with each group they leave.

Four phones' worth of personas. One person often speaks in several voices: the agency account, a client's support persona, a community moderator account. One Telegram app holds three accounts, four with Premium, so the fifth persona means a second phone, and a second phone means a second place the record can be lost.

Folders that don't scale. Free accounts get 10 folders of 100 chats; a client roster sorted into folders outgrows that quickly. Shareable folder links look like a handover tool, since a link can add someone to every group in a folder, but they only work for groups where the person sharing is an admin with invite rights. If the agency isn't admin in the client's groups, the folder link adds the new hire to nothing.

Partly, and not for agencies. Telegram Business, launched in March 2024, gives a Premium account quick replies, greeting and away messages, chat labels, chat links that count taps, and the ability to connect a bot. It is a good toolkit for one person answering customers in private chats. Telegram's announcement describes no team seats and no shared access.

The gaps line up exactly with agency work. Quick replies work in private chats, not groups. Connected business bots act only in the account's private chats, and since Bot API 9.0 in April 2025 such a bot may act for the account only in chats that were active in the last 24 hours. An agency's most important conversations are group conversations: the client war room, the community, the KOL coordination group. Business tidies one account manager's DMs; it does nothing for the client groups, and nothing for the handover when that account manager leaves.

That is why so many agencies add a CRM with a Telegram bot, and why that also falls short. A bot only sees the groups it has been added to, it starts from the moment it joins, and adding a vendor's bot to a client's community is a conversation many clients would rather not have. A Telegram CRM for agencies has to start from the agency's own account, see the groups that account is in, and keep what it saw.

In September 2025, ZachXBT published one project's price sheet for more than 200 crypto KOLs, with prices from $50 to $60,000 per post paid to Solana wallets, and found that fewer than five of the 160-plus who posted disclosed the posts as ads. Whatever you think of the leak, it describes the market KOL agencies work in: hundreds of influencers, prices negotiated one DM at a time, payment in crypto, and almost no paperwork. When a sheet like that surfaces, the agency with records can explain what it agreed and what it paid for. The agency without them has a group chat.

The everyday version is smaller. The agency pays $3,000 to a wallet for a thread on launch day. The client says the thread never appeared. The influencer says it ran and was deleted after 48 hours, as agreed. The only record of “as agreed” is a DM the influencer has since deleted, on the phone of an account manager who left in the spring.

For every KOL deal, an agency should be able to pull up, in one place:

• Who. Every handle the KOL uses on Telegram and X/Twitter, plus the WhatsApp number their manager uses, as one person.
• What was bought. Post, thread, pin, repost, or AMA; the date; how long it stays up; whether the client approved the copy, and who approved it when.
• The price and the wallet. The amount, the asset, the receiving address, the transaction hash, and the date paid.
• Disclosure. Whether a paid-post label was agreed, in writing.
• Delivery. The link to the post, when it went live, and whether it was still up on the agreed date.
• The conversation itself. The actual messages where the terms were set, not a summary someone typed later.

Pantheon keeps the KOL as one contact with the deal and your notes beside the conversations where the terms were set, so “what did we agree with this KOL?” is a search, not an archaeology project. It does not read wallets or verify payments on-chain: the transaction hash goes in the note, and the record of what it paid for is the conversation that sits next to it.

An account manager's Telegram is a high-value target because it is trusted by every client, KOL, and community it touches. Attackers know this, and the common attacks all use that trust.

The hijacked colleague. In December 2024 Kaspersky described fake “Telegram Premium gift” messages sent from contacts' hijacked accounts that steal the target's login code and password. Picture it at an agency: an account manager gets a gift link from a KOL they work with, enters a code, and loses the account. The attacker now sits in every client group that account belongs to and posts a “quick sync, here's the Zoom link” message. That is not hypothetical as a pattern: around September 2025, THORChain's founder lost roughly $1.35 million after a fake Zoom invite arrived through a friend's hijacked Telegram account.

The fake verification bot. Scam Sniffer reported in December 2024 that fake “Safeguard” verification bots in crypto groups were delivering wallet-stealing malware, with around 300 impersonator accounts created a day and two victims losing more than $3 million. A community agency that set up the client's group is the first to be asked why the bot was there.

The fake admin. A copycat account with a near-identical name, say @pr0ject_support, DMs the client's holders offering “support.” Nobody at the agency did anything wrong, but the client blames the moderation, and the agency's job is suddenly to prove what its real admins said and did.

In each case the agency needs two things fast: a clear list of who its real accounts and admins are, and a record of what was actually said in the affected groups that does not depend on the compromised account.

None of this needs a security team. It needs a few rules decided once and applied to every new client.

The agency owns the login, not the person. Since December 2022 Telegram has sold anonymous +888 numbers on Fragment that need no SIM, so an agency can own the number behind a client-facing account rather than having it live on an employee's personal SIM. An ordinary agency-paid SIM works too; the point is that the login belongs to the agency.

Two-step verification on day one. It protects against the code-phishing attacks above, and it starts the seven-day clock that ownership transfers typically need. Turn it on when the account is created, not when someone resigns.

Decide who owns and who admins each client group. Usually the client should own its community and the agency's role account should be an admin with named rights. For the agency's own war rooms, an agency account, never a personal one, should be the owner. Write down which is which per client.

Keep history visible in groups you run. Hidden history is right for some public communities, but in a working group with a client it guarantees that the next account manager starts blind.

Publish the real admin list. Pin it in every client community you moderate, and say plainly that admins never DM first. That turns the fake-admin problem into one the community can check for itself.

Capture the record outside Telegram. If an account is hijacked, frozen, or lost, the conversations it held should still be readable by the agency. That is the part a CRM is for, and the part no account setting can do.

Agencies ask this first, so here is the precise answer. Today Pantheon connects one Telegram account per workspace. An agency that runs a role account per client, or one per account manager, runs one workspace per account. That makes client separation structural: Client A's contacts, groups, and deals sit in Client A's workspace, and Client B's never appear there. It is not a tag or a saved filter that someone can forget to apply.

Clients are not users of your workspace, so nothing about one client is shown to another. The people who see a workspace are the people the agency gives the account to.

What is not there yet: a shared team workspace where several account managers work the same client records together. Shared team workspaces are next, with SSO and isolated-tenant deployments, and they are provisioned through guided onboarding rather than a self-serve button. If you run a team that needs that, write to enterprise@pantheon.run. Larger deployments are arranged case by case, from fully managed to fully yours on dedicated servers.

Until then, the pattern that works for agencies today is simple: an agency-owned account per client or per account manager, each connected to its own workspace, so the record of each relationship belongs to the agency from the first message.

Telegram-first is a regional fact, not a global one. In Brazil, Telegram is on 57% of smartphones and WhatsApp on 99%. An agency running a launch for a client with communities in the CIS and partners in Latin America will run one campaign across two apps.

A typical week: the client's war room and the Russian-speaking community are on Telegram. The Brazilian exchange partner and two local KOLs will only use WhatsApp. The client's US-based co-founder answers in iMessage. Half the KOL negotiations start as DMs on X/Twitter. The timeline of one campaign is now in four apps, and the person who knows how they fit together is the account manager.

The failure is the same as on Telegram, just spread wider. A KOL's manager confirms the posting date on WhatsApp while the KOL confirms the price on Telegram, and nobody sees both. The partner who agreed the co-marketing slot on WhatsApp shows up in the Telegram group under a different name, and the new account manager treats them as a stranger.

Pantheon follows the person, not the app. It keeps one record per person across Telegram, WhatsApp, iMessage, and X/Twitter, so the KOL and their manager, the partner, and the co-founder each read as one history no matter where they wrote. If one channel becomes unreliable in a market, the record of the relationship does not depend on it.

Pantheon is in alpha. Here is what it does today, with an agency's account connected.

It captures the work as it happens. Connect the account, with no bot added to the client's group and no browser extension, and Pantheon builds a contact for every person the account actually talks to, backfilled from the conversations already on it. It is available on the web platform and on desktop; mobile is available through private access.

It understands groups. In a client war room or a KOL coordination group, every message is attributed to the right person, so the client's head of marketing, their community lead, and the KOL's manager become real contacts rather than names in a scroll. The group itself stays visible as a relationship.

It keeps one record per person. The same KOL on Telegram, on X/Twitter, and through a manager's WhatsApp number resolves to one contact with one history. iMessage joins the same record.

It puts the business beside the conversation. Contacts, companies, deals, and notes live next to the threads. The client is a company, the retainer and each KOL buy are deals, and your notes sit next to the messages they refer to. Search runs across the history.

It answers questions over your own chats, with the AI you choose. Pick your model (ChatGPT, Claude, Grok, or one from Hugging Face) and ask Milo, your assistant: what did we agree with this KOL, what did the client approve for the launch week, which client groups went quiet. Milo summarizes a long group and reminds you who is waiting on a reply.

Your data is yours and is never sold; the details are in the privacy policy and the security overview.

Much of what is sold as agency Telegram software is built for volume: run dozens of accounts from one seat, put each behind its own proxy or dedicated IP, rotate accounts as they get restricted, and send DMs at scale. Pantheon does none of that, on purpose.

Not a mass DM or outreach tool. Pantheon does not send bulk messages or run outreach sequences. It records the conversations your people have.

No proxies, no account rotation, no anti-detection. Proxies per account and account rotation exist to make many accounts look like unrelated people, which is to say to work around a platform's spam controls. The accounts an agency should care about are the ones that hold years of client and KOL relationships. Those are the last accounts to put through that, and a tool that does it puts the agency's most valuable asset at risk to save a few hours of typing.

Not a compliance archive. Pantheon is a relationship record, not a regulatory archive. If a client's industry requires message retention, legal hold, or audit logs, that obligation needs a system built for it.

Not a bot in the client's group. A bot added to a client's group shows up in the member list for everyone in it, and it is one more thing the client has to approve. Pantheon works from the account the agency already uses in the group.

The narrow promise is the useful one: when an account manager leaves, a client asks what was agreed, or an account is lost, the agency still knows who it works with and what was said.

These are the questions to ask any vendor, with Pantheon's honest answer to each.

1. Who owns the account, and the record, if my account manager leaves? Look for a setup where the agency owns the login and the record lives outside the person's phone. Pantheon: connect an agency-owned account, ideally on an agency-held number, and the record in that workspace belongs to whoever holds the workspace, not to whoever last used the phone.

2. Will it see group history from before we connected? Pantheon: yes, it backfills from conversations already on the connected account. It cannot show messages that account never saw, such as a group whose history was hidden when the account joined.

3. Does it work in groups, or only private chats? Telegram's own Business tools and connected bots are private-chat-only. Pantheon: groups are captured, with every message attributed to the right person.

4. Can Client A's records be kept apart from Client B's? Ask whether separation is structural or a filter. Pantheon: today one Telegram account per workspace, so client separation is workspace separation. Shared team workspaces with SSO and isolated tenants are next.

5. What happens if an account is hijacked, frozen, or banned? Pantheon: what was captured stays in the workspace, outside Telegram. Getting the account back is between you and Telegram.

6. Can I show what we agreed with a KOL and what we paid? Pantheon: the KOL is one contact, with the deal, your notes, and the conversation where the terms were set side by side. Payments are recorded by you in the note; Pantheon reads no wallets.

7. Is the same person on WhatsApp, iMessage, Telegram, and X/Twitter one record? Pantheon: yes.

8. Does it need a bot in the client's group, or send messages for us? Pantheon: no bot, and no bulk sending. It is the record, not the megaphone.