A task list on a PC only serves people at a desk. The approver travels, sits in a meeting or goes home and the ticket stops. An @ in a group is worse: some read and never reply, some swipe past it. No timeout, no delegate, no “this is no longer theirs.” WeCom chat does not replace tasks with state. See WeCom chat is not a business entry.
A notice that only says “you have an approval” and cannot open the form is not a push. The tap should show key fields and let them act.
Leave auto-transfers to a delegate; four hours untouched escalates to the manager. A rule beats another nudge.
Not every entry deserves OS push
Native APP push is the most reliable. That is a common reason to build an APP. The decision is in When you actually need a native APP. If employees already live in WeCom, a session card or app message is often enough. Do not keep a store app only for push. Mini-program subscribe messages have count and template limits. They fit booking reminders, not as the only approval channel. Customer-side status reminders cut inbound calls. See How a customer mini program cuts support calls.
A flood of tasks makes people turn notifications off
Push broadcast, news and marketing into the approval channel and people with authority will kill push in system settings. Approvals die unread again. Split channels: one for approval, one for work exceptions. Keep marketing out. The employee side only holds tasks and work. See Employee features people will actually use. If nobody uses it after launch, first check whether push is noise or cannot even open. See Launched, unused: how to diagnose.
After the tap, finish in three steps
Agree, reject, transfer. Show only amount, bin and due date. Long notes go in detail. Approvers use one hand in an elevator. A complex page equals no push. Read is not done—split the lists. Write night and weekend policy: urgent outbound can wake someone; ordinary expense can wait for a workday. Push everything hard and authority treats the system as spam. The task list should sort by timeout. Management should see who sits on tickets.
Push copy should name the object and the deadline. Avoid empty “you have a task” notices you cannot rank. Do not push the same document three times—merge and update state. After travel or no network, tasks should still be there when they reconnect—not “missed the tap, gone.” DaXi Technology writes “who takes over after timeout” as configuration, not a group announcement. To keep the process moving on the road, go to the mobile service page and say whose desk the approval is stuck on now. Also compare efficiency you can actually see.