10 · Usage & ongoing use · Who receives it
The supplier left. The coupon still lands in his WeChat
User operations owns who it is sent to. Identity rules follow the solution architect. No permanent Excel on the side. Who calculates first between spend-and-save and coupons is not this role.
Send by group: Everyone in the WeChat group gets the same coupon. People who left, other suppliers, and HQ are mixed in.
Send by live identity: Only supplier accounts still bound and not deactivated. Unbind, and they disappear from the list the same day.
User operations owns “who receives it”
Accounts, stores, suppliers, and members are not a list that can be exported at any time. The mark of user operations is binding the list to the identity lifecycle. Leaving, unbinding, and deactivation must take effect before the next reach. He stays consistent with identity rules set with the solution architect. He does not keep a second permanent list in a spreadsheet. A permanent list expires the next day, and nobody knows.
Reach needs a purpose and an exit. Order reminders go to store managers, not to everyone who has looked at the system. Supplier reconciliation notices go to the person currently bound. Send records can show who received it and who was excluded because of deactivation. The exclusion reason must be explainable, or the business will think the system missed a send.
Coupons and messages are not better the wider they go
The cost of sending to the wrong person in an enterprise setting is goods in the wrong channel, leaked prices, and complaints. User operations asks the campaign side for filter conditions: which stores, members in what state, whether to exclude already deactivated. Conditions go on the campaign document. They cannot only say “old customers.” Old customers with no definition becomes the whole database. He refuses lists exported from the system and then forwarded by hand, because forwarding cuts deactivation.
Still receiving coupons after leaving
A supplier salesperson left. He was still in the WeChat group. Someone sent settlement coupons by group. The other party screenshot and asked about the price. User operations changed to taking people only from the binding. Unbind is done by purchasing in the system. The coupon job reads the same-day binding. The group is oral reminder only, not a send list. The fix is to void the wrongly sent coupon and record why. After that, every send has a preview of headcount. If the count does not match the bound count, it cannot send.
Preview headcount is this role’s gate, not an extra report. After every send, user operations samples three people who should have received it and one who should not. Should have received and did not: check the binding. Should not have received and did: stop the job at once and void the content. Looking only at total send-success cannot find a wrong recipient. In an enterprise list, sending to the wrong person is harder to take back than sending too few. When a supplier changes contact, how soon the old contact disappears from the send pool must be written in the rule. Same-day disappear versus month-end sync is a full month of price leak. That difference cannot be solved by everyone politely leaving the group. After a send list is generated, he keeps the conditions on the job, not only the final headcount. Headcount cannot be replayed. Conditions can. Next time someone says a send was missed, he can replay the conditions and see why they were excluded then. If the conditions include a hand-added person, he asks for a reason and an expiry.
A hand-added person with no expiry becomes a permanent privilege that bypasses identity deactivation. He writes wrong-recipient handling as a fixed action: stop the job, void the content, notify the scope, resend to the right people. Miss one of the four steps and the group only sees an apology. An apology cannot make a received price disappear. Voiding and a scope note can. He hands list conditions to campaign operations to reuse, so nobody screens again by hand. Reuse the same conditions, and coupon sends and notice sends will not have one excluding deactivated and the other missing it. Different conditions on the two sides, and the error always shows up in the louder campaign. List conditions must not say “people in the WeChat group.” The group is oral reminder only.