A new hire's first week tends to follow the same script. They hesitate to interrupt their mentor again, dig through old messages for the CRM password, have no idea who signs off their building pass, and by Friday they have formed a view of the company based on how hard it was to get a straight answer. The mentor, meanwhile, is trying to do their own job between dozens of small "where do I find…" questions. This article covers how to put an AI assistant next to a new employee specifically for week one: which questions it handles on which day, when it should message first, where it must hand over to a person, and how to prepare its material in a few working days rather than a quarter.
What new hires ask in their first five days
First-week questions are predictable, and that is exactly what makes them a good fit for AI. They also shift day by day: first logistics and access, then tools, then processes and people. Ask your last two or three hires what they asked, and you will get something close to this:
| Day | Typical questions | Where the answer lives |
|---|---|---|
| 1 — logistics and access | What time to arrive, where people eat, how to join the Wi-Fi, who takes my documents for HR, when the laptop arrives | Office guide, contact list, IT checklist |
| 2 — tools | How to log in to the CRM, where the email templates are, which chat is for what | Software guides, map of work chats |
| 3 — processes | How a deal moves from enquiry to payment, who approves a discount, how refunds work | Team procedures, process diagram |
| 4 — people and roles | Who owns purchasing, who to ask about deliveries, who the person everyone keeps mentioning actually is | Org chart with areas of responsibility |
| 5 — wrap-up | What is expected of me by month end, how probation is assessed, where to see my tasks | Onboarding plan, agreements with the manager |
The first four rows are reference questions: the answer is the same for everyone and is written down somewhere, or should be. The fifth is a conversation with the manager, and the AI's only job there is to remind both sides that the meeting is in the plan.
How an onboarding assistant differs from a help desk bot
An internal help desk bot waits to be asked; we covered that model in our piece on an internal help desk built on a knowledge base. For a new hire that is not enough. They often do not know what to ask and feel awkward asking anything that sounds obvious. So an onboarding assistant runs on a schedule and speaks first:
- Day one, morning: a short welcome, the plan for the day, the mentor's name and three things to get done before lunch.
- Day one, end of day: "Did all your access come through?" with buttons for email, CRM, work chats and building pass.
- Days two and three: one short tip a day about the process the new hire is starting on, with a link to the guide.
- Day four: who owns what in the team, and which questions go to whom.
- Day five: three feedback questions: what was unclear, what you could not find, what you wish you had known earlier.
If the new hire reports that CRM access still has not arrived, the assistant does not offer sympathy. It opens a task for whoever handles access and lets the mentor know. That is a case where automation saves not minutes but an entire lost day.
Example: a sales hire on day two
An illustrative conversation in a messaging app. The mentor has gone home; the new hire messages the assistant in the evening:
New hire: I'm handling inbound enquiries tomorrow. A customer is asking about paying in instalments. Do we offer that?
Assistant: Yes. Under the sales procedure, instalments go through a partner bank; you only take the request and pass it to the processing team (section 4, "Payment methods"). Don't quote terms yourself, the bank confirms those. There is a reply template under "Templates → Payment".
New hire: And if they ask for a discount for paying cash?
Assistant: Discounts beyond the price list are approved by the head of sales, see section 5.1. I've added this to the list for tomorrow's session with your mentor, since it's worth going through real examples of how the team usually responds.
The assistant did not invent a discount policy, and it did not leave the new hire stuck either. It gave the rule and moved the judgement call to a person. Section and folder names here are placeholders; yours will differ.
Who owns what during week one
| Task | What the AI does | What stays with people |
|---|---|---|
| Logistics, access, contacts | Answers from the office guide, checks everything was issued, raises tasks for anything missing | IT grants the access |
| Using the software | Walks through the guide step by step, in whatever language the hire asks in | Mentor demonstrates on a live task |
| Processes and rules | Quotes the procedure and says who approves exceptions | Manager explains why the rule exists |
| Employment paperwork | Says which documents to bring and to whom | HR processes them and handles anything personal |
| Expectations and probation | Reminds about the meeting and collects questions for it | Manager sets goals and gives feedback |
| Culture and unwritten rules | Nothing, because none of it is written down | The team |
Building the first-week pack
A common mistake is to start by documenting every process in the company. Onboarding does not need that. A new hire uses a small slice of company knowledge in week one, and that slice can be assembled quickly.
- Interview your most recent hires. Twenty minutes each with two or three people who joined in the last six months: what they asked, what took longest to find, what they learned too late.
- List the questions by day. Use the table above as a skeleton. You will usually end up with a few dozen questions, many of them shared across teams.
- Write short answers. A paragraph each, with a file link where one exists and the name of the topic owner. If the answer is nowhere, that is a finding in itself: the rule lives in someone's head. We hit exactly this when moving our own processes into one system (case study).
- Plan the check-ins. Five to seven proactive messages over the week is plenty; more starts to feel like nagging.
- Split by role. Sales, warehouse and finance need different guides. The shared layer is the same for everyone; the assistant only answers from what the new hire's role is allowed to see.
- Test it on your next hire. On Friday, sit down with the mentor, review what the assistant could not answer, and fill the gaps for the next person.
If your onboarding really starts before day one, with screening and interviews, see how AI helps with first-pass screening of applications.
What the manager sees on Friday, and the limits
By the end of the week you have a list of everything the new hire asked. It shows which topics caused friction, which guides are out of date, and which questions had no answer at all. Use it to improve onboarding and to brief the mentor, not to assess the employee, and say so on day one. Otherwise people stop asking.
- The assistant is only as good as the pack. Old screenshots in a guide mean it will confidently describe a button that no longer exists. Every answer needs an owner and a last-updated date.
- It does not transmit culture. How the team disagrees, who you can message at the weekend, what "urgent" means to this manager: people learn that from people.
- It is not worth it if you hire once a year. Update the guide and give the mentor time instead. It pays off when people join regularly or across several locations.
- Personal matters go to HR only. Pay, sick leave and family circumstances should never pass through the assistant's shared log.
More on internal processes is in our Operations section.
FAQ
How is this different from a PDF welcome guide?
A guide gets read once on day one and forgotten. The assistant answers when the question actually comes up, searches all documents at once, checks in on schedule and notices when something has not been issued. The questions it cannot answer tell you what the guide is missing.
Which languages can it handle?
It replies in the language it is asked in, even when the source guide exists in only one language, and links back to the original document. That matters for mixed teams, whether in Dubai, London or Tashkent.
Can the same assistant stay on after week one?
Yes. It usually turns into an internal help desk for all staff: the check-in schedule switches off and the question-and-answer base keeps growing.
How much does it cost?
It depends on the number of roles, the volume of documents and whether it needs to connect to your CRM or access management. The first conversation is to scope it for your company: get in touch, and read how we approach these projects on our AI agents page.