Private Telegram communities often have no public @username. Lookup still accepts invite links (t.me/+…, joinchat/…) and negative numeric IDs, but results depend on what Telegram and the resolution layer can see.
Invite link lookup
- Copy the invite link (Share link from an admin or existing member).
- Paste into private chat with @doublegram_lookup_bot.
- Lookup queries Telegram for a chat preview.
When preview data is available, the card may include:
- Title — group or channel name
- Description — public preview text
- Members — member/subscriber count when exposed
- Privacy: Private group (invite link) — marks invite-only entities
There is typically no @username on private invite-only chats.
Private channel paths (t.me/c/…)
Links like https://t.me/c/1234567890/99 point to a post inside a private supergroup or channel. Lookup extracts the embedded chat ID (as -100…) and queries that ID directly.
When Lookup cannot access a chat
For negative IDs or chats never seen before, Lookup may return:
Cannot access this group/channel. The userbot account must be a member and have interacted with this chat recently.
Lookup adds a note that the resolution account needs:
- To be a member of the group or channel
- To have recently interacted with it
- To have the chat in its session cache
This is a Telegram/session limitation — not something you fix in Lookup settings.
Workaround: Join the chat with your own Telegram account first (using the invite). That does not automatically fix Lookup's resolver, but public metadata from invite previews often still works without membership.
Public vs private comparison
| Entity | Best input | Typical data |
|---|---|---|
| Public channel | @username or t.me/name |
Full card + @username + members |
| Invite-only group | t.me/+… |
Preview title, description, members, private flag |
| Unknown private ID | -100… |
May error until resolver has session access |
Quick reference
- Invite links: t.me/+ or joinchat/
- Private flag on result card
- Access errors → chat not in resolver session
- Forward channel posts when possible for reliable IDs
Related: learn how to read a user result card field by field in Read a User Result Card in Telegram Lookup.