## The problem Every company has a handbook. Every company has a benefits doc, a remote-work policy, a parental leave policy, an expense reimbursement guide, an office-conduct policy, and a doc about how to actually book PTO. None of those documents are read end-to-end by anyone who isn't writing them. The result: the head of people-ops answers the same six questions every Monday — "how much PTO do I have left," "what's the parental leave policy at my tenure," "is dental effective on day 1 or day 30," "do I need approval for this conference," "can I expense this," "is my role eligible for the new home-office stipend." Each question takes five minutes to look up and another five to answer. People-ops loses three hours a week to lookup work; meanwhile employees who don't ask end up making assumptions that turn into avoidable HR conversations later. ## Author The **head of people ops** and a **people partner** co-author the policy answerer in the AgentBundle dashboard wizard. They paste in the canonical policy library: the company handbook, the benefits summary, the parental leave policy, the remote-work agreement, the office-conduct policy, the expense reimbursement guide, and the PTO booking how-to. MCP connections wire the agent to the live policy docs (so it always references the current version, not a snapshot) and to the HR system (so it can read the asking employee's tenure and role to answer eligibility questions correctly). No code; the wizard generates the bundle. The reviewer-workflow controls referenced below ship on Business tier and above; see [/pricing](/pricing) for what's gated. The agent is built around one rule: **it surfaces what the handbook says. It never invents an answer.** If the published policy doesn't cover a situation, the agent says so explicitly and tells the employee to file a ticket with people-ops, surfacing the policies it consulted so the employee can include them. No making things up, no guessing, no extrapolating from one policy to another. ## Review The VP People approves the agent. Every change to the policy library is reviewed by the head of people-ops and the people partner before publishing. [The audit log captures every edit, who made it, and what the prior text said](/security#approval-workflow) — important when an employee asks "what was the policy when I joined?" and the answer needs to be definitively retrievable. ## Distribute [APM (Microsoft's open packaging spec for AI agents)](https://microsoft.github.io/apm/) ships the agent to every runtime — engineers running Claude Code, designers running Cursor, customer-success folks running Copilot, sales running ChatGPT-equivalents through whatever plugin they prefer, and the AgentBundle dashboard for everyone who doesn't want to leave their workflow. Same agent, same answers, regardless of how someone prefers to work. ## Use The agent answers the same canonical policy questions across every role: - **Engineering** asks "can I expense a co-working space day while I'm traveling for a conference?" The agent reads the expense policy and the travel policy together, returns the relevant excerpts with section references, and notes that approval is required for stays over five nights — and links to the approval form. No people-ops ticket needed. - **Sales** asks "I'm being recruited for a board seat at a non-competing company — is that a conflict?" The agent reads the outside-employment policy, returns the disclosure requirement, and tells the employee to email the head of people-ops with the policy excerpt pre-formatted in the agent's response. The agent didn't decide; it surfaced the policy and handed off to the human. - **Customer Success** asks "how much PTO do I have left this year?" The agent reads the employee's calendar via MCP, surfaces remaining PTO based on the company's policy, and links to the booking form. People-ops doesn't see the question. - **A new hire on day 3** asks "is my dental plan effective today?" The agent reads the benefits doc and returns the answer with the effective-date language verbatim. The new hire doesn't have to interpret it; the agent quotes the policy directly. - **A manager** asks "can I extend a contractor's engagement past Q4?" The agent reads the contractor-engagement policy, surfaces the maximum allowable engagement length, and — if the extension would exceed the maximum — tells the manager to file a request with people-ops and includes the relevant policy excerpt for the manager to attach. The manager gets a direct answer for the simple cases; people-ops only sees the edge cases. The agent's value is **not** that it replaces people-ops. It's that it handles the bottom 80% of policy lookups so people-ops can focus on the 20% that actually need a human conversation. ## Composition When a question touches a policy edge case the agent doesn't have a confident answer for, it doesn't guess — it tells the employee to file a ticket with people-ops and surfaces the policies it consulted so the employee can include them in their ticket. The agent recommends; the employee acts; people-ops gets a ticket with full context that the employee assembled. ## Iterate A new benefit ships — say, the company adds a mental-health stipend through a new partner. The head of people-ops updates the benefits doc and the agent's policy library. The agent picks up the change on the next sync; the next employee asking about wellness benefits sees the new option. **No all-hands email that 40% of the company will skim. No HRIS broadcast. No "did you see the new benefit?" questions piling up in people-ops's inbox six weeks later.** The new policy is surfaced to anyone who asks, with the same accuracy as the policies that have been there for years. And six months later, when an employee asks "when was the mental-health stipend added?", the audit log answers definitively.