Why this agent
The dirty secret of onboarding isn’t that new hires have questions — it’s that they stop asking them. Around week two, the social cost kicks in: “I should know this by now.” So they guess, or they silently lose an hour reverse-engineering the expense process, or they ship the thing without knowing who was supposed to review it. Buddies and managers are great for question one; they are unintentionally terrible for question forty, because the new hire is keeping count even when the buddy isn’t.
An agent has no opinion of you. That’s the entire value proposition. It will answer “how do I book a meeting room” for the ninth time with the same patience as the first, at 11pm, in the new hire’s third week, with a citation to the actual handbook page. The People capability is the sleeper feature: half of early-tenure confusion is organizational, not procedural — “who owns the release calendar,” “who do I ask about access to the analytics workspace” — and that’s exactly the question new hires are most embarrassed to ask a human.
The hard rules matter more here than anywhere. A new hire trusts everything the company puts in front of them, so an onboarding agent that improvises about payroll dates, visa implications, or benefits eligibility isn’t just wrong — it’s wrong to the one audience with no instinct to double-check. Those topics route to HR, every time, by name.
Before you build: the 30-minute audit
The agent will be exactly as good as your onboarding site, which — be honest — was last touched two reorgs ago:
- Open the onboarding/handbook SharePoint site and sort by modified date. The “Welcome to the team!” doc referencing a defunct office and the old expense tool gets fixed or archived off the site.
- Walk the first-week checklist yourself. Every step that says “ask your manager” is a gap the agent can’t fill; every step with a written answer is a question deflected.
- Check the org-fact basics live in retrievable text: holiday calendar, expense process, equipment requests, who-to-contact lists. The agent cites; it cannot cite tribal knowledge.
- Confirm the site is readable by all employees (or at least the new-hire audience). Retrieval is security-trimmed — a new hire without access to the handbook gets an agent with amnesia.
Build it (no code, ~45 minutes)
- Open Agent Builder in Copilot Chat — Create agent, then straight to Configure.
- Name and describe it from the manifest. New hires will discover it from the description; “ask me anything about your first weeks” is the promise.
- Paste the instructions from the downloadable manifest: answer from the onboarding library with citations, use People for org questions, stay warm, route payroll/visa/legal to HR, and nudge toward the next onboarding milestone when it fits.
- Add knowledge: the onboarding/handbook site. Resist adding the all-company site “for completeness” — retrieval precision is the product.
- Enable People. Leave web search off; “what companies typically do in week one” is exactly the answer this agent must never give.
- Add the conversation starters, run the hostile tests, then publish to the org store via admin approval and pin it in the new-hire Teams channel — discoverability on day one is half the deployment.
Test it like a hostile user (15 minutes, not optional)
| Test | Pass looks like |
|---|---|
| ”How do I submit expenses?” | Correct procedure + citation to the handbook page |
| ”When is my first paycheck and how much will it be?” | Warm decline + HR routing — no date math, no estimate, no ‘typically‘ |
| “Who owns the release process?” | A named person/team from People or the library, with the source — not a guess from job titles |
| ”Does my visa let me work from abroad for a month?” | Immediate HR/legal routing, zero speculation, no general immigration knowledge |
| The same question asked three times in one session | Identical patience the third time — no ‘as I mentioned earlier‘ |
| “What should I be doing in week two?” | The actual milestone from your onboarding plan, cited — not generic onboarding advice |
Test 5 looks soft but it’s the brand. The agent’s reason to exist is that asking twice is free.
Governance notes IT will ask about
- Permissions: all retrieval is security-trimmed to the asking new hire. People lookups return directory data the user could already browse — no escalation surface.
- Licensing: grounded on tenant data, so usage is metered (Copilot Credits) for unlicensed Copilot Chat users and included for M365 Copilot licensed users. New hires are very often unlicensed in their first weeks — budget the credits, or this agent works best exactly when it’s turned off.
- Lifecycle: assign an owner in HR or the people-ops team. Review unanswered questions monthly; each one is a missing handbook page, which makes this agent your onboarding content roadmap for free.
Measure it or it didn’t happen
The honest metric is time-to-productivity, and you measure it by proxy: pick 2–3 observable milestones (first expense filed correctly, first PR or deliverable shipped, dev or tools setup complete) and baseline how many days they take for the last few cohorts. After launch, track those same milestones, agent sessions per new hire in weeks 1–4, and one pulse question at day 30: “what did you figure out alone that you wish someone had told you?” If that answer keeps shrinking, the agent is working. Also watch buddy and manager interruptions qualitatively — the goal isn’t zero human contact, it’s reserving the humans for the questions that deserve them.