Article summary
Segment Telegram community lists across relationship, permission, account observation and business events without turning TG fields into membership claims.
Dividing a Telegram community list into only “active” and “inactive” hides the questions that matter: what relationship exists, what contact is permitted, and when was the observation made? A usable membership canvas needs at least four axes.
Horizontal axis: where the relationship came from
Distinguish a paying member, event registrant, public-community participant, support contact and imported lead. TG account fields do not create membership. Membership status must come from an order, contract or the organization’s own community system.
Vertical axis: what contact is permitted
Record the authorized sender, channel, purpose, time and withdrawal. Joining a group should not automatically mean consent to one-to-one marketing. Leaving or opting out cannot be overridden by a new activity observation.
Third layer: account observations are movable notes
| Observation | Can support | Should not imply |
|---|---|---|
| Registration | Channel-availability routing | Valid membership |
| Active days/offline time | Choosing a review window | Purchase intent |
| Username/UserID | Deduplication and human lookup | Real-world identity |
| VIP/frozen observation | Account-state review | Customer value |
Fourth layer: business events set priority
Renewal date, support ticket, event registration, content download and sales stage come from the company’s own systems. They may be combined with TG observations to create an operating queue. TG fields cannot replace commercial and service facts.
Four example canvas zones
- Known relationship plus valid permission: provide the requested service.
- Known relationship plus unclear permission: collect evidence before outreach.
- Unknown relationship plus recent account observation: audit the source only.
- Mapping conflict or frozen observation: route to human review.
Where AIPUSH fields belong
TG Registration returns phone and registration observation. TG Activity may return UserID, username, offline time, active days, names, VIP observation and frozen observation. Every one belongs in the account-observation layer with checked_at.
A TXT task does not carry membership identity
Upload a TXT file with one phone per line. Keep member_id, orders, group name and permission in a private crosswalk, then rejoin Excel with batch_row. If the task file is exposed, it does not reveal the complete membership relationship graph.
What the canvas must periodically erase
Expired activity observations, purposeless name fields and person-level labels from completed projects should be deleted or reduced to aggregates. Telegram’s Privacy Policy is a useful reminder that visibility and processing depend on feature and context.
Move from canvas to queues, not fields to blasts
The output should be reasoned work queues: service, review, permission repair, suppression and deletion. If a segment cannot name its evidence, purpose, owner and expiry, it should not enter automation.
