Enterprise · Onboarding
AI employee onboarding agent
Week-one as objects: handbook, quizzes, tasks, intro meetings — in the workspace the hire will actually work in.
Week-one as objects: handbook, quizzes, tasks, intro meetings — in the workspace the hire will actually work in.
Onboarding dies as a 40-link email. New hires do not know who to ask; IT repeats itself; managers assume “HR sent something.”
This is internal AI Staff. The hire is a member. The handbook is a doc, the quiz is a check, intros are calendar events, exceptions go to a human. Customer onboarding is support or booking — not this page.
Docs
Handbook as source
Answers from materials you maintain
Quiz
Prove they read it
Scores managers can see
People
Intros on calendars
Not a “find time sometime”
Traditional tools
A Notion checklist, a separate quiz tool, and calendar ping-pong with IT.
With Maicos
Handbook, quiz, tasks, and intros in the same workspace the hire will use on day two.
A checklist that lives where the work will live.
Answers come from the onboarding pack. If the policy changed, update the doc — do not hope the bot “remembers the new vibe.”
Below-bar scores create a task for the manager. A quiz nobody looks at is decoration.
Laptop, accounts, benefits forms. Appflows can start provisioning; the agent should not invent admin access.
1:1s against real calendars once the hire exists as a member. Booking-style mechanics, internal audience.
Membership, materials, proof, people.
This is not a public careers bot. They need the namespace.
Version the doc. Retired policies should not still answer.
Role-specific packs beat one giant PDF for everyone.
Hiring manager, buddy, IT. Calendars, not “loop them in.”
Day one should produce artifacts, not vibes.
Hire asks the onboarding agent about MFA
Answer from the security doc, with a link to the section.
They take the quiz
Score lands in a table. Below 80% → task for the manager.
Agent offers intro times
Hiring manager’s calendar, 25 minutes this week.
IT appflow for accounts
Agent starts the flow; IT completes. The hire is not told “it should just work.”
Onboarding is a project with a due date. If it is only a chatbot, it will lose to the employee’s first real ticket.
“How do we treat customers?” should quote the handbook. If you have not written it down, a human should answer — not a confident paragraph.
onboarding.mquiz · Q4
What is the first step in our refund policy?
82% avg score · 2 need follow-up
The same apps you already work in — not a second chatbot that needs uploads.
Useful agents have a job description. These limits keep this page honest — and help you pick a different agent when you need one.
How people use this every day.
From the official handbook, with links, not a paraphrased wiki from 2019.
Engineering vs sales packs. Low scores notify the manager, not Slack shame.
Tasks plus an appflow. Status visible to the hire and to IT.
Calendar holds for the people in the onboarding table.
Internal Maicos AI Staff that guides new hires through docs, quizzes, tasks, and intro scheduling in the enterprise workspace.
Employees (and contractors you invite). Customer onboarding is support, booking, or a success process — not this role.
It can start appflows you define. The destination system still has to be connected. The agent should not pretend an account exists if the flow failed.
Fix the doc. The agent will keep quoting whatever you pointed it at. That is a feature.
Preboarding can be a limited pack, but mixing candidate-facing recruiting with internal policy is how you leak employee-only information.
Start free — Workspace, Create, Automate, and Integrations built for AI from day one.
No credit card required · Free during beta