If install, repair, and swap are only “whoever is nearby” in the group, you get two outcomes: the tech thinks it is done, the customer does not; or it is done, but parts and hours will not match, so you cannot settle or analyze repeats. Close the loop means something narrow: every work order must land in an end state, and every hop has a person, a time, and a rule for whether it can roll back.
After-sales changes to: can chase, can check, can settle
The state machine exposes overtime: dispatch not accepted in two hours, on site past the promise, parts waiting more than three days. The system chases; a supervisor does not scroll the group. The tech completes and photographs on the phone; the back office settles by work order — not a pile of slips at month-end. How dispatch lands for install/after-sales companies is in Installation and after-sales: how dispatch should close the loop. A work order with no closed state is no after-sales scorecard.
Open work orders poison a sales promise
If sales cannot see open installs and complaints when the customer orders again, they promise a date as if nothing is wrong. Hang the work order on the customer card so sales and finance see the same relationship — not only the contract amount. See Sales and finance looking at the same customers and contracts. On the sales-order-to-cash chain, an after-sales allowance should apply too. See From order to cash: how a system cuts one more fight.
When people move, open tickets must reassign
A tech leaves, the group stays, unfinished visits live in a personal photo album. The state machine says the work order belongs to a pool, not a private chat. Reassign, transfer, and assist leave a trail. Why operations stay up when people leave is in Why operations do not fall apart when people leave. Risk of WeChat dispatch is in The risk of taking orders and shipping from WeChat groups.
If parts and hours miss the work order, settlement and quality are false
Parts in a pocket and a spare on the truck become off-book stock first. Closing the loop means issues hang on the work order; leftovers return or move to the next ticket. Otherwise the ticket says “fixed” and stock is a loop short — the parts bin breaks first. Repair reasons must classify: bad install, material lot, customer use — so quality is a sampleable ticket, not a feeling. When a customer asks what that visit swapped, the attachment is the working paper. See What the system does when you reconcile, audit, or a customer asks for a document. If repeats in a growth period still live in veteran memory, the step jams. See Why growth requires an operations system of your own.
When DaXi Technology builds work orders, we draw your real states — not a three-box “open / in progress / done.” Waiting parts, waiting the customer to cut power, waiting a second visit: miss one and the floor goes back to the group. To pin states from repair to follow-up, go to Business systems service page and say which hop will not close. Chase and fewer repeats are visible efficiency. See The efficiency a business system can make visible. When a packaged work-order module misses the floor, compare When SaaS does not match how the floor actually works.