A day with a digital employee in procurement采购部数字员工的一天
Instead of a definition, a day: the lookups, drafts and follow-ups a digital employee takes on, and the moments it hands the decision back to a person.不下定义，讲一天：数字员工接下的查询、初稿和跟进，以及它把决定交还给人的那些时刻。
October 7, 2026 · 3 min read2026 年 10 月 7 日 · 阅读约 2 分钟
"AI agent" can mean almost anything. So instead of a definition, here is a day.
What follows is an illustrative day for the digital employee of a procurement team, built from the tasks procurement teams hand over most often. The supplier names and figures are examples. The way the work moves is not.
08:55 — It is already in the chat
There is nothing to open. The digital employee is a member of the procurement group chat, like everyone else, and it answers when someone @-mentions it. It also has a name and a face on the team's roster, and an owner: the procurement manager, who trains it and answers for it.
Before anyone asks, it knows three things about its job: the procurement policy, the team's vocabulary ("confirmed date" means the supplier's written confirmation, not the date on the purchase order), and what it is allowed to see. It reads purchase orders, receipts and supplier records. It does not see payroll, because the procurement team does not.
09:02 — "Check this month's lead times"
A buyer asks it to check lead times for the team's regular suppliers. Two minutes later there is a card in the chat: lead-time changes over the last four weeks, read from the ERP's purchase orders. Supplier A is five days late, Supplier B three, Supplier C on time. At the bottom: as of 09:00 today, and two suggested next steps: request backup quotes, or draft a chaser letter.
Two details matter here. The answer cites where it came from, so the buyer can click through to the orders. And the next steps are suggestions. Nothing has been sent.
09:20 — A correction that sticks
The buyer replies: Supplier B confirmed a new date by email yesterday; use that, not the order date.
The digital employee updates the card. More importantly, the correction is recorded against its instructions for the team, so tomorrow it checks for confirmed dates first, for every buyer, without being told again. This is what training looks like in practice: not a model being retrained, but a team's way of working being written down, one correction at a time.
11:30 — "Compare three quotes, per our policy"
A new part needs a supplier. The buyer asks for a comparison of three quotes. The digital employee builds comparison sheet P-0924-018 following the procurement policy, which asks for price, delivery time and the supplier's track record, side by side.
Supplier A: 30-day delivery, $26,400. Supplier B: 35 days, $25,500. Supplier C: 25 days, $27,400.
The policy says that a purchase of this size needs the procurement manager's approval, so the sheet does not go to the suppliers. It goes to the manager, marked awaiting approval. The manager picks Supplier A for the shorter delivery time and approves. The approval, and who gave it, is recorded in the Action Log.
14:00 — The letter it did not send
Supplier A is the one running five days late on an older order. The buyer asks for a chaser letter. The digital employee drafts it, with the order numbers and the confirmed dates, and leaves it in the chat as a draft.
It could not have sent it on its own even if it had wanted to. Writing to a supplier is an action on behalf of the company, and in this team, actions like that wait for a person. The buyer edits one sentence and sends it.
Friday, 16:00 — The weekly summary
Every Friday afternoon, the digital employee posts the week to the group: 42 orders placed, 31 received, 3 delayed, with links to each of the late ones. Nobody asked this week. It is one of the routine tasks the manager set up in the first month, and it takes the manager's Friday afternoon back.
What the day adds up to
Look at what the digital employee did, and what it did not do.
It looked things up, quickly, from the right systems, and said where every number came from. It drafted: a card, a comparison, a letter, a summary. It learned one correction and kept it. It followed the policy.
It did not decide. It did not send anything outside the company without a person. It did not see data its team cannot see. And every step it took can be traced afterwards.
That combination is the whole point. The hours go to the machine. The judgement stays with the people. And the know-how, including that correction about confirmed dates, now belongs to the team instead of one buyer's memory.
「AI 智能体」这个词几乎什么都能指。所以我们不下定义，讲一天。
下面是一个采购部数字员工的一天，按采购团队最常交给它的活编排。供应商名字和数字是举例；活怎么流转，是真实的。
08:55 它已经在群里
不用打开任何东西。数字员工和其他人一样是采购部群里的成员，有人 @ 它，它就回。它在团队名册上有名字、有头像，还有一位负责人——采购经理，负责带它，也为它负责。
还没人开口，它已经知道三件事：采购管理制度；团队的说法（「确认交期」指供应商的书面确认，不是采购订单上的日期）；以及它能看什么。它能读采购订单、收货记录和供应商档案；工资它看不到，因为采购部本来就看不到。
09:02 「核一下这个月的交期」
一位采购员让它核常用供应商的交期。两分钟后，群里出现一张卡片：近 4 周的交期变化，数据来自 ERP 的采购订单。供应商 A 延后 5 天，B 延后 3 天，C 正常。卡片底部写着「截至今天 09:00」，还有两个建议的下一步：发起备选询价，或者生成催交函。
这里有两个细节。回答附了出处，采购员点进去就是那几张订单。下一步只是建议，什么都还没发出去。
09:20 一次留得住的纠正
采购员回复：供应商 B 昨天邮件确认了新交期，按那个算，别按订单日期。
数字员工改了卡片。更要紧的是，这次纠正记进了它在这个团队的工作说明里：从明天起，它对每一位采购员都会先查确认交期，不用再提醒。这才是「训练」在实际中的样子——不是重新训练一个模型，而是把团队的做事方式，一次一个纠正地写下来。
11:30 「按制度，三家比价」
一个新零件要定供应商。采购员让它对三家报价做比价。数字员工按《采购管理制度》生成比价单 P-0924-018：价格、交期、供应商的历史表现，并排列出。
供应商 A：30 天交货，¥186,000；供应商 B：35 天，¥179,500；供应商 C：25 天，¥192,800。
制度规定这个金额要采购经理审批，所以比价单不会直接发给供应商，而是标上「待采购经理审批」交给经理。经理看重交期，选了 A，点了批准。谁在什么时候批的，记在 Action Log 里。
14:00 它没有发出的那封信
供应商 A 正是那家在一张旧订单上延后了 5 天的。采购员让它写催交函。数字员工起草好，带上订单号和确认交期，以草稿的形式放在群里。
就算它想，它也发不出去。给供应商写信是代表公司的动作，在这个团队里，这类动作要等人。采购员改了一句，发了出去。
周五 16:00 周报
每周五下午，数字员工把这一周发到群里：已下单 42 单，已到货 31 单，延期 3 单，每一张延期单都附了链接。这周没人提醒它。这是经理在第一个月设好的例行事务之一，把经理的周五下午还给了经理。
这一天加起来是什么
看看它做了什么，没做什么。
它查东西，查得快，从对的系统里查，每个数字都说清出处。它起草：一张卡片、一份比价、一封信、一份周报。它学到一次纠正，并且记住了。它按制度办事。
它没有做决定。没有人点头，它不往公司外发任何东西。团队看不到的数据，它也看不到。它走过的每一步，事后都查得到。
关键就在这个组合：时间交给机器，判断留给人；而经验——包括那条关于确认交期的纠正——从此属于团队，不再只存在某一位采购员的脑子里。
AIDC · AI Deployment CompanyAIDC · AI Deployment Company
