Private-domain build-out needs ownership, tags, SOPs, and compliance. Chasing friend counts alone yields an unusable address book. Answer frequent questions first, then the summary table.
Move personal WeChat to WeCom?
Yes, with migration incentives and customer notice templates.
More groups better?
No. Themed groups with admins; archive zombie groups.
Measure private-domain ROI?
Repeat purchase, referrals, service cost—not friend totals.
Outsourced ops risk?
Contract data/account ownership and script compliance audits.
Turn the address book into operable assets
| Decision lens | Common trap or cost | Safer cut |
|---|---|---|
| Ownership/inherit | Rules before launch | Stop account loss |
| Tags+SOP | Executable outreach | Less spam |
| Measure | Repeat/referral/cost | Not friend count alone |
- Contact ownership and offboarding inheritance must be written before launch.
- Tag systems serve outreach, not executive aesthetics.
- SOPs need triggers, script versions, and frequency caps.
- Connect conversation quality to conversion before calling it retention.
- Compliance: consent logs, sensitive-word filters, and complaint handling are mandatory.
