Telegram Scams That Use Your Team's Name: A Playbook for the Business Being Impersonated

Last week one of your customers asked a question in your Telegram group, and someone answered before your team did. Not in the group. In their DMs, from an account with your support lead's name, your logo as the photo, and a link to "verify the wallet" or "fix the stuck payment".

Every guide to Telegram scams is written for the person who got that DM. This one is written for you, the business whose name was used. Your customer lost money or nearly did, and they will remember whose name was on the account.

Start with one number. Telegram only lets an admin hide a supergroup's member list once the group has at least 100 members, the default set in Telegram's API configuration for hiding participants. Below that, anyone who joins can scroll your full member list. Above it, they can still see every person who posts a message, which is the person the fake admin wants: the one who just admitted they have a problem.

The patterns change their wording every few months. The mechanics barely change. Each one relies on the customer not knowing which account is really yours.

It is the pattern built most directly on your own group. A scammer sits in your group, watches for anyone posting about a failed transaction, a locked account or a refund, and messages them privately within minutes. The display name copies your team member's. The photo is lifted from their profile. The opening line sounds like your support, because your support's replies are in the group for anyone to read.

The customer is primed. They asked for help, and help arrived. The scam works because your real support is slower than the fake one. That is uncomfortable, and it is also the part you control.

Telegram usernames are unique. Display names are not. Anyone can set their name to "Acme Support" and upload your logo. What they cannot do is take your exact @username. So the scammer registers the nearest thing: an extra underscore, a zero for an O, "official" added to the end.

Most customers never look at the username. They look at the name and photo in the chat header, which are exactly the two things the scammer copied.

A bot with your brand in its name, or a link to a page that asks for a Telegram login code, works on customers who have been told some process needs "verification". Telegram's own FAQ says its login codes only arrive in the verified "Verification Codes" chat and should never be shared with anyone, including other apps. Its section on bots is just as plain: do not hand a bot your passwords, Telegram codes or bank details, however politely it asks.

If your product ever asks a customer to verify anything inside Telegram, a scammer will copy that step. Remove it if you can. If you cannot, describe exactly what it looks like in public, so a copy stands out.

These show up after the first wave. A customer who lost money posts about it, and the replies fill with accounts offering to recover the funds for a fee. If you post a warning about an impersonator, expect the same replies under it. Write the warning so it already answers them: nobody from your team, and nobody else, can recover the money for a fee.

Telegram gives you more than people assume, and less than you would want. Here is what exists, checked against Telegram's own pages on 2026-10-14.

The Telegram FAQ says every app has Report buttons that send content to moderators. Its answer to "what if someone is pretending to be me" is one line: contact @NoToScam. That account appears as "Report Impersonation". Open it from the link in Telegram's FAQ rather than from search, because impersonators copy reporting accounts too.

For a business, the person to file the @NoToScam report is the one being impersonated: your staff member, or an admin of your official channel when the brand itself is copied. Include the scammer's exact @username and a screenshot of the DM your customer received. Then tell your customer to report the account from their side too, because the report from the person who received the message is the one tied to the chat.

The Spam FAQ adds that group admins can report users who post spam in their groups. Do that for the scammer's account if it is still a member, then remove it.

Telegram's API defines two flags on an account: scam, described as "This may be a scam user", and fake, set when an account was reported by many users as fake or scam (user object). Apps show these as a warning label next to the name. You cannot apply one yourself. Reports are the input; the label is Telegram's decision.

Telegram's verification policy verifies channels, bots and public groups that meet notability criteria, such as verified profiles on at least two major social platforms and press coverage. It also says plainly that Telegram does not verify user accounts at the moment.

That matters more than it sounds. Your support team answers from a personal account. That account will never carry a blue check, so the customer has nothing on the account itself to tell your real support from a copy.

Third-party verification closes part of the gap. The same policy lets an organization whose official bot is already verified apply through @VerifyBot to become a verifier, then mark accounts and chats with its own icon, as described in the developer documentation. For a large brand that qualifies, that can mean an icon on each staff account. For most businesses running Telegram support, the bar is too high this year.

Three settings reduce how easily a scammer finds your customers. None of them stops a scammer from reading the group.

• Hide members. Available once a supergroup has at least 100 members. The list disappears for members, but anyone who posts is still visible, so the person asking for help is still exposed.
• Join requests. Make new members wait for admin approval (invite documentation). It slows down accounts that join only to harvest. It does not tell you who is a scammer.
• Aggressive Anti-Spam. The FAQ recommends it for large groups. Telegram's config sets the default minimum at 200 members. It removes spam posted in the group; it does not see DMs.

Telegram also lets a person stop strangers from starting chats with them. The API documents a privacy option that limits new chats to contacts, Premium users and people who already have a chat open with them (global privacy settings), and the FAQ mentions that some users charge Stars for messages from non-contacts. Both are your customer's settings, not yours, and a Premium account still gets through.

Ask what a convincing impersonator actually needs. A list of who your customers are. The names and tone of your support staff. And, ideally, who has an open problem right now, because that person is waiting for a DM.

An outsider gets the first from your member list and the third from public messages in your group. Someone who has worked inside your support inbox has all three, plus the exact wording your team uses and the details of each customer's case. In our view, that is the impersonator to worry about most. A contractor who leaves with a list of usernames and open issues does not need to guess who to message.

That is the internal data risk of a CRM, seen from the outside. It does not show up as a breach. It shows up weeks later as your customers receiving very accurate DMs from someone who is not you.

The boundary: most impersonation you will see is run by outsiders reading a public group, and no internal control touches that. Inward controls close one path, the most dangerous one. The public playbook below still has to do the rest.

None of this needs a tool. All of it needs to be written down once and repeated everywhere your customers look.

Pick one @username for support. Put it on your website's contact page, in your official channel's description, in your group's pinned message and in your email signatures. Use the same exact string in every place, so a copy looks wrong next to it.

Telegram does this for itself. Its FAQ names its official support routes and says it has no other support accounts on social platforms, and that anyone claiming otherwise is not Telegram. Say the same thing about your business.

Write the rule as something a customer can check: "Our team will never message you first. Support only replies from @acme_support, after you write to it." Pin it in the group with the rest of your group rules. Put it in the group's welcome message, which Telegram shipped on 2026-08-25 and which only the new member sees, so it reaches people at the moment they are most likely to be targeted.

Then keep the rule. If one salesperson DMs a customer first, the rule is worthless, because the customer now knows exceptions exist.

If five staff members each answer customers from their own Telegram accounts, your customers have to learn five identities. A scammer only has to copy one of them. If the whole team answers from one shared support account, there is exactly one identity to learn, and any other account using your name is wrong by definition.

This is also where most teams get stuck, because one Telegram account on one phone does not work for five people on a shift. Entergram is built for this case: a team can share one Telegram account inside one workspace, and everyone answers it from a single interface, so the customer always talks to the same @username while the work is spread across the team. It runs on real personal Telegram accounts, not bots, so the account your customers see is an ordinary Telegram account with your support username. Our Telegram support software page covers how the shared inbox and tickets work. Entergram does not detect scams, flag lookalike accounts or report impersonators to Telegram. It removes the reason customers have to guess which of your accounts is real.

Entergram's privacy controls point inward. You can hide usernames and hide group member information from users in your workspace, and prevent them from editing or deleting messages. The first two mean a staff member or contractor working your support queue does not walk away with a list of who your customers are. The last two mean the history of what your support account actually said stays intact, which matters when a customer forwards a screenshot and asks whether it came from you. For a copy of that history kept outside Telegram, see Telegram chat backup for business.

The limit: these controls apply to what your team sees inside Entergram. They do not change what Telegram shows to other Telegram users, and they do not hide your group's member list from a scammer who joined the group. That is Telegram's Hide Members setting, above.

When a customer tells you they were contacted by a fake:

1. Ask for the exact @username and a screenshot. The display name is useless as evidence.
2. Report the account in the app, ask the customer to report it too, and file it with @NoToScam from the staff account or channel being copied.
3. Remove the account from your group if it is a member, and report it as spam there.
4. Post a short warning in the group that names the fake @username and repeats your one real support identity.
5. In the same post, say nobody can recover lost funds for a fee.

If the impersonation involves taking over a real staff account rather than copying it, it is a different incident. Work through how to protect a Telegram account first, ending unknown sessions and turning on two-step verification. And if your own support account gets restricted after mass reports, the steps are in what to do when a Telegram account is frozen.

Everything above reduces how convincing an impersonator looks. Moderation reduces how long they sit in your group. A team that removes scam accounts within minutes, and tags repeat offenders so every moderator recognizes them, gives the fake admin less time to find a target. Our community moderation playbook covers shifts, tags and escalation for larger groups, and our guide to customer support from a personal Telegram account covers why customers expect a person rather than a bot.

Report the account from inside Telegram using the Report option, and send the details to @NoToScam, which Telegram's FAQ names for impersonation. Include the exact @username and a screenshot. Ask the customer who received the message to report it as well.

Use the in-app Report option on the message or the account. If the scammer is a member of a group you run, report them as spam from the group and remove them. If your brand or a staff member is being impersonated, @NoToScam is the route Telegram points to.

Not on a personal account. Telegram's verification policy covers channels, bots and public groups that meet its criteria, and says it does not verify user accounts at the moment. A Telegram-verified organization can become a third-party verifier and mark its own staff accounts, but that requires a verified bot first.

Telegram applies it to accounts it considers likely scams or that many users reported as fake or scam. You cannot add it to an impersonator yourself. Reporting is how you feed the decision.

You cannot stop it entirely. You can make it less effective: hide the member list once you pass 100 members, require join requests, enable Aggressive Anti-Spam in large groups, pin a "we never DM first" rule, and put that rule in the group's welcome message. Message authors stay visible no matter what, so the public rule matters more than any setting.

No. Entergram does not scan for scams or flag lookalike accounts. It lets a team answer from one shared support account so customers only have to learn one identity, and it can hide usernames and group member information from your own staff.

Count how many Telegram accounts your customers have been told to trust. If the honest answer is "whoever on the team replied", a scammer has an easy job. Choose the one @username that will be your support identity this week, put it in your pinned message and your welcome message, and then decide whether your team can realistically answer from that single account with the setup you have now.