Quick takeaways
- Web-user-ID access lookup should match paid access to the right Telegram account before support changes access.
- Supported lookup keys should stay explicit: telegramUserId, email, webUserId/webId, and membershipId where available.
- Telegram username is useful context, but Telegram username lookup is not supported in V1.
- Identity recovery should avoid phone-number matching, public API keys, CRM writeback claims, or full-history claims unless documented.
Map website user IDs to Telegram access with webUserId/webId, membership status, plan evidence, access codes, and support-safe recovery.
Use this guide when the membership record, member status, plan, renewal, or support view has to settle the access decision.
Next read: Telegram Membership API Integration Guide.
How this guide was produced
Every guide is written for the same paid-access workflow: payment evidence, Telegram identity, plan status, support lookup, and expiry enforcement.
Published by KickThemBot from product documentation, launch runbooks, integration tests, and paid-access operating procedures.
Membership lifecycle planning: plan setup, Telegram identity, subscriber status, renewals, support lookup, and expiry enforcement. Automation may assist drafting and page generation; indexed guides are selected for a distinct user job and reviewed against the documented workflow. Claims avoid fake rankings and hidden guarantees.
To help admins make a safer access decision before moving members, payments, invite paths, or expiry rules.
Implementation steps
- Start with the strongest supported lookup key: webUserId or webId when website account evidence is strongest, then membershipId and telegramUserId for access changes.
- Review the identity risk: website account mismatch, shared checkout accounts, stale website IDs, or renewals that update a different Telegram identity.
- Choose the support-safe workflow: map the website account to the membership, confirm plan/status/source, and update Telegram access from trusted backend evidence.
- Set boundaries: do not expose API keys in the browser or treat webUserId as a reusable public invite credential.
Start from supported lookup keys
Paid Telegram support should begin with identifiers the membership system can actually query and explain.
For this website identity lookup, start with webUserId or webId when website account evidence is strongest, then membershipId and telegramUserId for access changes. Supported lookup fields include telegramUserId, email, webUserId, webId, and membershipId, plus status, state, plan, and source filters when narrowing a review.
Treat usernames as weak context
Telegram username can help a human understand a ticket, but it should not be the source of truth for paid access.
The risk is website account mismatch, shared checkout accounts, stale website IDs, or renewals that update a different Telegram identity. Telegram username lookup is not supported in V1, so support should not approve access from username evidence alone.
Recover access without creating duplicate seats
Identity recovery should protect legitimate buyers while avoiding duplicate active access for one purchase.
The support workflow should map the website account to the membership, confirm plan/status/source, and update Telegram access from trusted backend evidence.
Keep API keys and identity checks server-side
Lookup and access changes should run from trusted backend code with server-side API keys, not from public frontend pages.
The boundary is clear: do not expose API keys in the browser or treat webUserId as a reusable public invite credential. Do not claim phone-number matching, full Telegram history, CRM tag/note/classification writes, outbound webhooks, or public frontend lookup unless the product documentation supports it.
FAQ
What is Telegram web user ID access lookup?
It is the process of using a website user identifier to find the membership record that controls Telegram access.
Can KickThemBot V1 look up a member by Telegram username?
No. The documented V1 lookup should use supported identifiers such as telegramUserId, email, webUserId/webId, or membershipId. Telegram username is useful support context, but username lookup is not supported in V1.