Article summary
Design LINE private-channel acquisition from voluntary entry through service, nurture and exit, with cleanup, registration, limited attributes and a CRM state machine.
A LINE “private channel” does not mean the business owns a user forever or may contact a collected phone without limit. It should be an explainable customer relationship: a person enters through a clear route, knows what to expect, can change preferences and can leave. Cleanup and registration checking support that relationship rather than create it.
Make the acquisition promise explicit
An ad, store QR, event form or support card states the brand, content after joining, frequency and opt-out. If a phone is also collected, explain why. Do not hide long-term marketing behind a one-time coupon.
Begin CRM with five states
| State | Entry event | Allowed action |
|---|---|---|
| invited | Saw invitation but did not join | No assumed permission |
| joined | Voluntarily established relation | Deliver promised content |
| engaged | Asked or interacted | Provide relevant service |
| dormant | No business interaction | Reduce frequency/review purpose |
| opted_out | Left or refused | Necessary suppression only |
Phone cleaning preserves source evidence
Store phone_raw, source country, submission time and rule version before creating phone_normalized. Uncertain country codes or multiple phones in one field become exceptions. Valid format does not establish LINE registration or holder identity.
The proper place for LINE Registration
AIPUSH LINE Registration returns phone and registration result for a well-sourced sample with continuing purpose. It does not substitute for joining, friend relationship, messaging permission or delivery. Name the output registration_observed and attach checked_at.
Profile fields require a higher threshold
LINE Gender and Age may include user ID, nickname, gender, age, avatar, people count, type and skin tone. Run it only when an approved aggregate study changes a content decision and access/retention has been reviewed. Never use it for individual pricing, credit or denial of service.
The TXT/Excel-to-CRM connection
| Step | Data sent out | Kept internally |
|---|---|---|
| Generate TXT | One phone per line | contact_id, source, permission |
| Receive Excel | Task fields | Batch hash and crosswalk |
| Stage and accept | No additional outbound data | Unknowns, errors, collisions |
| Update CRM | None | Append observation and time |
Nurture content follows user intent
Separate welcome, product education, support, replenishment and event notices and let people choose. Nickname and profile do not substitute for intent. Adjust content from first-party clicks, inquiries and purchases with frequency limits.
Do not merge identity collisions automatically
One phone may connect to several LINE observations, while one user ID may join multiple contacts through historic entry. Send collisions to human review with evidence and dates. Similar avatar or nickname is not a merge key.
Review value and harm together
Measure qualified joins, first resolution, repeat contribution, support time, opt-outs, complaints, unknowns and collision backlog. Friend growth and registered phones found do not establish a healthy private channel. Negative experience is a cost.
Dormancy and exit
Dormant does not mean “increase blasting”; it triggers review of whether the relationship has a purpose. Stop refreshing platform observations when purpose ends. Opt-out immediately blocks marketing and removes unnecessary profiles and temporary files; another check cannot bypass that choice.
The standard for a complete workflow
For every contact, the business can explain entry source, choices, observation batch, why a message arrived and how to leave. When those answers exist, a LINE private channel is a sustainable service relationship rather than a warehouse of phones.
