WeCom, communities, and cards count fans by channel. The same customer sits in multiple groups; reply target is unclear.
01 Industry judgment
Owned-channel revisit · Owned-channel marketing
Owned channels manage whether replies write back to the customer with a next action — not community size
When WeCom, communities, and cards count by channel, the same customer appears in multiple groups and sales cannot tell which thread to answer. Group activity without a next date cannot map heat to closed deals; ops and sales on separate backends leave no same-day pending-reply list.
B2B or service orgs that retain customers via cards, forms, and communities. This solution writes replies back to the customer — it does not replace WeCom as the chat tool.
Owned-channel marketing · How the business hangs together
Into leads
- Card visit
- Form capture
- Community join
Customer ledger
- Same mobile
- Groups joined
- Benefit promises
Follow-up actions
- Pending-reply list
- Next date
- Deal-related replies
Manager board
- Duplicate joins
- Reply overdue
- Dormant not woken
02 Process diagnosis
After the owned-channel-revisit judgment, split private-domain ops into six process checks. Joins and cards join one customer; replies must write a next date; ops and sales read the same pending reply; benefit promises reconcile from the customer file. Join count is only the door; reply overdue and dormancy decide whether that community keeps investment.
Group is active; the project has no next date. Activity cannot map to closed deals.
Hard to convert
Ops and sales view on separate backends. Same-day should-reply targets have no list.
Hard to manage
Benefits promised in group notices cannot be checked at close; after exit, customers conclude the org only pushes.
Hard to trust
Weekly meetings only watch join counts. Reply overdue, close sources, and dormant customers never reach standup.
Hard to decide
Owned channels are not another chat window. Replies must write back to the customer with a next action.
Hard to solve
03 Matching management actions
01 · Hard to acquire
Joins and cards join one customer
People left via form or card stay that customer after joining. Duplicate numbers merge first.
02 · Hard to convert
Replies must write a next date
Group activity is not follow-up. Deal-related content writes back to the project.
03 · Hard to manage
Ops and sales read the same pending reply
Same-day should-reply targets appear on a list — not by scrolling chat history.
04 · Hard to trust
Reconcile benefit promises from the customer file
Complaints and exit reasons write back to the customer. On rejoin, read the promise of that day.
05 · Hard to decide
Evaluate communities from reply overdue and dormancy
Join count is only the door. Overdue and dormancy decide continued investment.
06 · Hard to solve
Write replies back before opening more windows
WeCom keeps chatting. Qianying manages customers and dates.
Business architecture
Owned channels managed by replies written back to the customer. Joins, cards, pending-reply lists, and next dates sit on one person.
Into leads
Card visit
Form capture
Community join
Customer ledger
Same mobile
Groups joined
Benefit promises
Follow-up actions
Pending-reply list
Next date
Deal-related replies
Manager board
Duplicate joins
Reply overdue
Dormant not woken
Product role on this path
solutions.capabilitiesLead
Three questions before go-live
Sales will not fill forms, it fights the current stack, data will not migrate — almost every team asks these three.
Is WeCom enough?
Conversation lives in WeChat. Who the customer is, who owns them, and what happens next live in CRM.
Will sales have to paste every message?
No. Only conclusions, file versions, and next dates write back to the customer.
Is owned channel a primary acquisition bet?
High-ticket teams use it as a follow-up channel, not the main acquisition engine. Footer no longer rides SCRM keywords for volume.