“Reporting” as it happens in the group
The same job, inside a business entry
WeCom and DingTalk connecting people is valuable: org tree, read receipts, audio/video, notice. Mistaking “connected” for “work done” turns the group into a second system. A shout to change price, a screenshot to redeem, a “ok” to approve. After the fact you can only search chat. Someone changes roles and the delegate dies in a private thread. Why push and tasks must enter a tappable entry. See How push and tasks keep approvals from dying unread.
No fields in chat means no stats and no permissions
You cannot count exceptions this month by point, cannot stop an unauthorized person from “shouting outbound,” cannot let a customer open status without flipping a salesperson’s chat. Customers need self-serve. See Why customers need a self-serve status page. If store redemption is only a count in the manager group, HQ stock will not move. See After the store app shares HQ stock and membership.
WeCom can be a shell. It cannot be the only ledger
The sound pattern: notice on WeCom, documents on the employee side or a mini program, one back office. An approval card can sit in a session; tapping it is still a form with permissions. Official-account menus without a submittable entry idle on the outside too. See Official-account menus without a mini program.
Take “ok” out of chat before a rule can actually run
A group “ok” has no amount cap, no bin, no who-in-what-role may say ok. Finance tracing a discount can only screenshot. A customer wants status; sales can only forward chat. If field reporting stays on voice notes, points and photos will not match and rework shows up next week. Fold official actions into a form. That does not reject WeCom. It puts WeCom back on notice and talk. If the group still takes official tickets after launch, nobody will use the system. Diagnose in Launched, unused: how to diagnose.
Sessions can archive. Documents cannot live only in a session
WeCom session archive is compliance and accountability—not a business state machine. You still cannot filter by bin or stop unauthorized outbound. Groups can keep briefings and pep. “This ticket follows the group” must be voided with an end date: after that the warehouse only recognizes system outbound and finance only recognizes a system discount. Without that cut, launching an entry is just another unused form.
A bot that writes the group into a sheet is still not a business entry
Syncing group messages to a sheet only changes the container: no permissions, no state machine, pictures still scattered in personal chat. If a session photo is evidence, it should land as a ticket attachment. When DaXi Technology connects WeCom, chat stays on the communication layer. To close official actions that still live in the group, start from the mobile service page and say which tickets still run in a session. Also compare Why work has to happen on the phone.