“I want to know what @username said today” represents two different tasks in group chats and broadcast channels. Messages in group chats may include the sender’s username; posts in broadcast channels are typically published by the channel itself, and “@username” in the body is simply a mentioned string. Mixing the two together will yield an answer that seems reasonable but identifies the wrong account.
If the product currently only supports broadcast channels, a more accurate question would be: “Which messages in the channel today mention @username, and what do those messages say?” This article discusses only such mentions in the channel’s content and does not interpret them as posts made by that user personally.
First, distinguish between three types of objects
| Object | What it represents | Can it be used to determine if the message was posted by the user? |
|---|---|---|
@username in the channel body |
Message text contains a username | Cannot |
| Channel posting identity | Posts published by the channel or a visible signature | Can only specify the visible publishing identity |
| Group message sender | Group messages associated with a specific account or anonymous identity | Requires evaluation based on group permissions and identity fields |
A channel may mention someone else’s username, paraphrase their views, publish interview content, or remind users to follow a specific account. A search result for “@username” only confirms that the username appears in the channel’s content; it does not prove that the account holder wrote the post, nor does it establish the user’s true identity.
Conduct the First Round of Searches Using the Exact Username
First, keep the format @ and enter the full username, such as @example_user. Then, try removing the @ part, as the body text might simply say example_user or include it within a link like t.me/example_user.
It is recommended to document three sets of variations:
- Current full username;
- The username without “
@”; - Known display names, brand names, or former usernames.
Usernames may be changed or transferred. If a current username does not yield old messages in a search, this does not mean it was never mentioned in the past; the text preserved in old messages may still contain the previous name. Conversely, the same string at different times may not necessarily refer to the same actual user.
Include the time and context in the question
Don’t just ask, “What did this user say?” Instead, try:
Identify messages in today’s channel posts that mention
@example_user,Example Labs, orexample_user. Sort the results by time, indicate whether each mention is a reference, recommendation, criticism, or contact information, and provide the original message. Do not speculate on whether the account owner posted the message themselves.
If the channel contains a large amount of information, include project names, locations, or events as well. The time range should use the start and end dates actually displayed on the page, paying particular attention to the time zone corresponding to “today.”
Handling Forwarded Messages, Quotes, and Screenshot Text
Forwarded messages may retain the visible source, or they may contain only the channel’s own text. Usernames within quote blocks are still just the text displayed in the current post. Usernames within screenshots, video captions, or attachments may not be detectable via a standard text search.
Therefore, the results should specify that the search is based on searchable message text and the provided metadata, rather than the content of all images, voice messages, and files. When users know for certain that a username appears in a screenshot, they should directly open the media file from around the corresponding date, rather than interpreting a zero-result text search as meaning the username does not exist.
How to Organize Search Results
A verifiable list should include at least the following: message timestamp, variations of the name mentioned, brief context, and a link to the channel message. A “mention type” field may also be added, but only using classifications supported by the original text:
- Contact information or account recommendations;
- whether quoted or paraphrased;
- Event participants;
- Risk alerts or complaints;
- Cannot be determined from the context.
Do not infer the relationship between an account and a channel based solely on tone. The fact that a channel refers to someone as “our friend” does not imply that a legal, employment, or business relationship has been established.
How to Maintain Traceability After a Username Changes
When saving research results, record the username as it appeared in the message at the time, rather than just saving the account that was later parsed. The original message link and message timestamp are more stable than the currently displayed name and make it easier to explain “why it matched at the time.”
Links may be inaccessible due to access restrictions, changes to the channel’s username, or message deletions. In such cases, you may state that the source is currently unavailable, but you must not fabricate content that was not in the original text, nor automatically map old usernames to unverified new accounts.
What Can asktele Answer?
It can search for mentions in the body text of a selected broadcast channel, organize relevant messages using natural language, and provide the sources of the messages. It cannot convert the “@username” in the body text into the group sender field, nor can it verify real-world identity, account ownership, or confirm that a specific statement was actually posted by that user.
If the question truly requires “what a specific group member posted today,” the current product’s channel scope is not suitable; instead, use Telegram to search for and manage senders within the group itself. Clearly defining the product’s scope is more important than returning a complete answer that contains an incorrect identity.
Say “The channel message mentioned @username,” not “@username said these things in the channel,” unless the source actually provides and verifies the sender’s identity.
Sources
- Telegram:messages.search — Filtering by chat text and sender are separate conditions.
- Telegram: Search and filters — Message search and type filtering on Telegram.
- Telegram: Deep Links — Link structures for public channel messages and other messaging scenarios.
- Telegram: Channels, supergroups, and basic groups — Differences in identity and access behavior between broadcast channels and groups.
This page was last reviewed on August 9, 2026. Telegram interfaces can change by client and version.