10 · Usage & ongoing use · Still in use
The system is not erroring. Variance is back in WeChat
Customer success watches whether the main path has fallen back to WeChat, and pushes the thing that is actually blocking use. How many times a menu was tapped sits with product operations.
Customer success owns “still in use”
An acceptance signature only says the paths in scope once walked through. The mark of customer success is watching, after go-live, whether those paths are still happening. He uses behaviour, not satisfaction: how many receiving documents closed in the system this week, how many still in WeChat; whether over-receive pending confirmation has sat more than a day with nobody handling it; whether warehouse clerks who should sign in have had no operations for several days running. No operations may mean someone left and nobody took over, or the old method came back. He asks. He does not treat silence as stability.
Split with Technical support. Support handles a single ticket. Customer success looks at repeating patterns, and judges whether to add training, change a rule, or admit a function should not have gone live. The judgement carries counts. One angry store manager is not every store stopped. Variance in every store sitting outside the system is use failure. A wave-pick menu nobody tapped for two weeks is not a cell customer success counts. That is a function fact for product operations.
How to push, not how to nag sign-in
He does not treat “please use the system more” as an action. Actions are concrete: night shift is missing a training, pending confirmation has no supervisor, the print template makes people rather write by hand. Each item goes to the matching role, and next week he looks at whether the count moved. If it did not, keep chasing the cause. Do not swap in a new slogan. Renewal and upsell, if they happen, should sit on these counts, not on a demo.
Variance in WeChat
A month after go-live, receiving was all in the system. Half of variance closes were still in WeChat. Customer success sampled ten WeChat records and found supervisors felt the reason options in the system were not enough, so they had warehouse clerks say it in WeChat first. That is a rule gap, not an attitude problem. He handed it to the product owner, with the ten documents as evidence. After the options were added, he counted close locations for another week. When WeChat stopped showing new variance, this path counted as recovered. Meetings that only praise the system do not move the number.
He writes this result into the customer monthly: which paths are in use, which are not yet. Each month customer success chases only the one path that most affects use, until the count moves. Chase ten at once and each one stops at “already discussed.” He puts that one path on the first line of the monthly. Other observations go below. A first line with no number is still a courtesy note, not customer success. Unused and cannot-use must be split: does not know how gets training; the system cannot work gets defects and privilege; a function that need not exist goes to product operations for facts. All three need counts. Do not use the same sentence “promote harder.” If the whole variance-close path is in WeChat, and after adding options it still does not come back, only then does he hand “this main path should no longer be a promise” to product. Whether the entry is folded or rebuilt is a function fact from product operations, decided by the product owner. Customer success does not change menus. When he brings it back to the customer he first says which path is already stable, then what the next one to chase is. The recovery action is written as one sentence the customer can retell: this week variance closes all returned to the system. He lines up three counts by store: system closes, WeChat screenshots, pending confirmation over a day. Three numbers side by side show who went back to the old method. For a warehouse clerk with no operations for three days, he first asks whether the person is still on the job, then whether the function is usable. A person not on the job who still holds an account is handed to user operations the same day for deactivation. The weekly does not write a satisfaction percentage. It writes whether this path’s system-close count is up or down from last week.