Article summary
Interpret TG offline time, active days, usernames and frozen status while separating platform activity from dead-number, bot-account and permission questions.
Identifying an active Telegram user means interpreting activity-related observations returned for this check. It does not mean proving that a phone is dead or that an account is a bot. Those questions belong to platform activity, telecom status and account type. Combining them into one label damages both list hygiene and community operations.
Return the three questions to three systems
| Question | Evidence layer | Can TG Activity answer alone? |
|---|---|---|
| Is the phone still served by a telecom network? | Carrier or telecom status | No |
| What Telegram-related activity observation is returned? | Telegram screening fields | Within the field boundary |
| Is the account a Bot API bot? | Account type and Telegram interface semantics | Not from active days |
What TG Activity actually returns
AIPUSH TG Activity may return phone, TG UserID, TG username, offline time, active days, First Name, Last Name, TG VIP observation and frozen status. A wide field set does not promise a value in every cell or create a verified identity profile when combined.
“Offline for a long time” is not a dead phone
A person may reduce use, change privacy settings, move to another account or pause Telegram while the phone still receives calls. Conversely, a disconnected or recycled telecom number cannot be confirmed from one activity result. A dead-number question requires a separate telecom-status service and its own evidence.
Telegram visibility is intentionally not absolute
The official Telegram FAQ explains that Last Seen depends on privacy choices and may be represented as recently, within a week, within a month or a long time ago. A visibility-driven unknown or broad interval must not be rewritten as an exact login time or an “abandoned account” verdict.
Names and behavior do not prove a bot account
A name containing “bot,” an automation-style avatar, constant availability or rapid responses are not reliable account-type evidence. Telegram also documents that what bots can see depends on the conversation and privacy mode. TG Activity output should not be expanded into an unsupported “human rate” or “bot risk score.”
Frozen and VIP observations need narrow semantics
Frozen status describes an observation at the check time. It does not mean that the telecom phone is invalid and does not prove fraud. TG VIP likewise cannot establish income, willingness to pay or lead value. Store frozen_observation and vip_observation separately with checked_at.
Use state combinations instead of one score
- Usable for the current task: format passed, required observation returned and result is current.
- Activity unknown: visibility or return is insufficient; no positive or negative claim.
- Identity conflict: UserID, username or phone relationship requires review.
- Format exception: no valid check occurred, so it is not counted as inactive.
- Business blocked: permission is absent, withdrawn or purpose ended; recent activity does not authorize contact.
Segment from the business relationship
Support contacts, event registrants, community members and unknown-source phones have different processing grounds. Stratify by source, permission and business_event first, then use activity within one stratum for service ordering or human review. “Recently active” must not promote an unrelated phone into a sales lead.
TXT submission and controlled write-back
The TXT contains one phone per line and no community conversations, wallet addresses, orders or permission records. An internal manifest retains input_id and provenance. Excel lands in staging. When UserID or username conflicts, preserve both versions rather than overwriting the community member key.
Audit false interpretations
Review four cohorts: known recent interactions with unknown screening, observed activity with no business response, long-offline observations on telecom-valid phones, and suspected bots without account-type evidence. Report unknowns and conflicts independently. A missing sales reply is not a reference label that proves screening wrong.
When to retire the activity observation
Stop using it when it exceeds the internal freshness window, permission is withdrawn, the business event ends, mapping remains unresolved, or a test shows activity ordering does not improve service. Remove downstream ranking labels without necessarily deleting a customer master record retained on a separate valid basis.
TG Activity is valuable as timestamped platform-related evidence. Kept separate from telecom validity, bot identity and purchase intent, it can clarify list review instead of becoming another misleading master score.
