When colleagues can @mention your agent: design the intake before the requests arrive
Microsoft's Autopilot lets colleagues @mention a person's agent like a coworker. Here is how to decide what it may take on, commit to and record.
On 17 November 2026 Microsoft began rolling out Autopilot to its Frontier customers, describing it as "a trusted autonomous agent that is personal to you, always on, and working for you." It lives in the company's tenant "so you can @mention it like a colleague", and it "can watch Teams channels, follow up on emails, run recurring work, and manage a project—without waiting for a prompt." Once colleagues can send requests to someone's agent, that agent becomes a new queue in the company. If nobody decides what it may accept, what it may promise and where each request is recorded, work moves into a side channel that no process owns.
A mention is a request without a record
When a colleague writes "@Ana's agent, can you send me the supplier list and confirm Friday's review?", three things happen in one sentence. Someone asks for information. Someone asks for an action. And someone asks for a commitment in Ana's name.
In a chat, those three look the same. In an operation they are very different. Information can usually be shared if the requester is allowed to see it. An action changes a system. A commitment binds a person, and sometimes the company, to a date, a price or a decision.
The same thing happens without agents: requests arrive in chats and hallways, and only some of them end up in a ticket, a CRM stage or a project board. An agent that answers every mention instantly makes this faster, not better. Speed of response is not the problem to solve. Knowing which requests became work, and who owns them, is.
Four kinds of request
Before a personal agent accepts mentions from others, sort what it can receive into four kinds. The kind decides what the agent does next.
- Information. "What is the status of the Garcia order?" The agent answers from what its owner is allowed to see, and only if the requester is allowed to see it too.
- Action in scope. "Add this supplier to the review list." The agent may act alone if the action is on its approved list and can be reversed.
- Commitment. "Confirm Friday's review with the supplier." Anything that promises a date, a price, an approval or a resource in the owner's name waits for the owner.
- Not this agent's work. "Can you approve this refund?" If the work belongs to a team, a role or another process, the agent routes it to that queue and says so. It does not quietly do it because it technically can.
Microsoft says the owner decides "what work Autopilot takes on" and that it "can check with you before key actions." Writing down which requests count as key actions is the owner's job, and it has to happen before the first colleague mentions the agent.
Write the intake charter
One page per personal agent is enough. Each row is a kind of request the agent may receive:
| Column | Question |
|---|---|
| Request | One verb and one object: "share order status", "schedule supplier review" |
| From whom | Which people or teams may ask for it |
| Kind | Information, action in scope, commitment, or not this agent's work |
| Agent alone | What it may do without asking anyone |
| Needs the owner | What waits for approval, and how long before it reminds |
| Recorded in | The system where the request becomes a record: CRM, project board, ticket |
| Reply | What the requester hears back, and by when |
The charter usually shows two things. Some requests people send to a person's agent actually belong to a team queue that already exists. And some requests come so often that they are a process nobody has written yet.
- 01Mention arrivesTeams, email, channel
- 02Classify the requestInformation, action, commitment, other
- 03Open a recordCase ID in the system that owns the work
- 04Act or waitCommitments wait for the owner
- 05Reply with statusWhat was done, what is pending, by when
Every week, recurring requests are reviewed: the frequent ones become a written process.
Five rules for a personal agent others can reach
- Every accepted request gets a record. If a mention turns into work, it opens or updates a record in the system that owns that work, with a case ID. The chat thread is where the request arrived, not where it lives.
- The agent always replies with a status. Done, waiting for the owner, or routed to another queue, with the name of that queue. A colleague should never have to wonder whether the request was seen.
- Commitments wait, even when the agent is confident. The approval gate sits in the workflow, not in an instruction inside the prompt. A missing approval should block the action, not just discourage it.
- Team work goes to the team queue. A personal agent should not become the back door into work that a team handles with its own stages and owners. Routing is part of its job.
- Review the mentions log every week. Count the requests by kind and by requester. The ones that repeat are the next thing to design properly, as a stage, a form or a team agent with its own owner.
Identity says who acted. The charter says what it was allowed to do.
Microsoft built Autopilot on the controls IT already uses. "Each Autopilot has its own Microsoft Entra Agent ID and a named manager," "IT can scope its access and block it anytime," and "its sign-ins and actions are logged under its own name, so security teams have a clear audit trail."
Those controls answer who acted and with what access. They do not answer whether the agent should have accepted a request from the sales team to confirm a delivery date that belongs to logistics. Access is set by IT. The intake charter is set by the people who own the work, and it is what turns a log of actions into an operation someone can review.
Why the record matters more than the reply
In Sentynel's Rodo case, WhatsApp, social and web enquiries were brought into a service operation with a measurable resolution path. Each enquiry became a pipeline record that moves through New, In progress and Resolved, and that is why the result can be measured at all.
Source: Source: Rodo operational report, 24 September 2026. The resolution cohort covers 31 August–24 September. Figures describe pipeline records, not all conversations.
Requests to a personal agent are the internal version of the same problem. A conversation that never becomes a record cannot be resolved, measured or handed to someone else when the owner is away.
A first step for this week
Before anyone in your company can mention another person's agent, take one person whose inbox and chats fill with requests. Read two weeks of what they received and sort each request into the four kinds. Then fill in the charter for the ten most frequent ones. If more than a few of them end with "recorded in: nowhere", that is the work to design first, with or without an agent.