What Can Digital Employees Do on Their Own, and What Requires Your Sign-Off?
On Monday morning, the owner of an industrial parts trading company opens his phone. Overnight, his digital employees have already taken care of more than 40 tasks: synced contact changes for 12 customers, flagged three overdue orders with outstanding payments, replied to nine routine inquiries, and sent quotes to two long-time customers. He skims past the first few, then stops at the word “quote.” The price is right. The tone is right. The problem is that this task bypassed him.
Whether a task can run automatically has little to do with how smart the model is. Ask three questions: Can a mistake be undone? Does the action reach outside the company? If something goes wrong, can you trace who signed off? Let reversible actions that stay internal run freely; pause anything irreversible or that creates an external commitment and wait for a person. The boundary is about the level of the action: the same digital employee can write internal weekly reports fully automatically, but must get sign-off before sending external quotes.
Three levels are enough to put this into practice: run automatically; do it first, then notify (with a two-hour to half-day window to undo it); or get sign-off before doing it. The easiest thing to overlook is an action with no monetary value but significant responsibility—for example, promising “the goods will definitely arrive by next Wednesday.” It costs nothing, but it’s still a commitment you’ll be held to. The boundaries also need to be built into the system: an action whitelist, permissions attached to actions, a replayable end-to-end audit trail, pre-authorization within defined limits, and escalation when those limits are exceeded. If approval becomes a rubber stamp, the sense of security it offers is false.
This article is adapted from our company’s WeChat public account article, “What Can Digital Employees Do on Their Own, and What Requires Your Sign-Off?” The original has no public link.
This does not constitute investment advice.
On Monday morning, the owner of an industrial parts trading company opens his phone. Overnight, his digital employees have already taken care of more than 40 tasks: synced contact changes for 12 customers, flagged three overdue orders with outstanding payments, replied to nine routine inquiries, and sent quotes to two long-time customers. He skims past the first few, then stops at the word “quote.” The price is right. The tone is right. The problem is that this task bypassed him.
Whether a task can run automatically has little to do with how smart the model is. Ask three questions: Can a mistake be undone? Does the action reach outside the company? If something goes wrong, can you trace who signed off? Let reversible actions that stay internal run freely; pause anything irreversible or that creates an external commitment and wait for a person. The boundary is about the level of the action: the same digital employee can write internal weekly reports fully automatically, but must get sign-off before sending external quotes.
Three levels are enough to put this into practice: run automatically; do it first, then notify (with a two-hour to half-day window to undo it); or get sign-off before doing it. The easiest thing to overlook is an action with no monetary value but significant responsibility—for example, promising “the goods will definitely arrive by next Wednesday.” It costs nothing, but it’s still a commitment you’ll be held to. The boundaries also need to be built into the system: an action whitelist, permissions attached to actions, a replayable end-to-end audit trail, pre-authorization within defined limits, and escalation when those limits are exceeded. If approval becomes a rubber stamp, the sense of security it offers is false.
This article is adapted from our company’s WeChat public account article, “What Can Digital Employees Do on Their Own, and What Requires Your Sign-Off?” The original has no public link.
This does not constitute investment advice.