New joiners get their first week answered without asking around
A new joiner asks whatever they are stuck on and the flow decides whether it is an IT setup question, a people question or a who-does-what question, then answers from your onboarding and IT documentation. Anything else points them to their manager.
People · Someone asks · 10 steps · Reads your documents
QuestionQuestion
RouteWhat kind of question?
RetrieveRetrieve — IT setup
RetrieveRetrieve — People answer
RetrieveRetrieve — Who to talk to
AnswerPolitely decline
AnswerIT setup
AnswerPeople answer
AnswerWho to talk to
Answer shownAnswer shown
10 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
New starters spend their first week interrupting their team to find out how to get a laptop configured, what the expense rule is and who runs a system. IT and HR answer the same questions every intake, and the joiner’s first impression is that nothing is written down.
How it is governed
- Retrieval returns only passages the person asking is permitted to see.
- Answers cite the onboarding or IT document they came from.
- Anything personal is referred to a named person, not answered from records.
- Every question and answer is kept in the run history.
- Who runs it
- People operations teams; IT support teams; Hiring managers.
- What you supply
- Onboarding docs and IT setup guides as knowledge sources.
From template to a live agent
The same builder, tests and release review apply to a template as to anything built from scratch.
- Open it as a working flow
- Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
- Prove it before it ships
- An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
- Keep a person on the decisions
- A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
- Publish where people work
- A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
- What teams usually change
- Rename the categories to match how your first week is organized; Point each path at its own onboarding and IT sources; Add a path for office, travel or equipment questions.
Questions buyers ask
- Can it see a joiner’s own HR record?
- No. It answers from your onboarding documents, policies and IT guides, and is instructed to name who to ask for anything personal. It has no connection to an HR system.
- What happens with a question none of the paths fit?
- It takes the fallback path, says it is not sure and points the joiner to their manager. Nothing is forced out of documents that do not cover the question.
- How do we keep it current?
- It answers from whatever your onboarding and IT sources hold at the time of the run, so keeping those documents current keeps the answers current. Every answer cites its document, which makes a stale page easy to spot.
Related templates
All 60 templates- Employee handbook deskAnswers staff questions from the handbook, with personal data redacted before the model ever sees it.PeopleSomeone asks4 steps
- Candidate screenerScores an application against the criteria for the role, quoting the evidence for every mark so a rejection can be explained.PeopleA document or recording is attached5 stepsa person approves
- Staffing matcherSuggests who to put on a piece of work, from what your own records say they have actually done.PeopleSomeone asks4 steps
See it run on your own data
We open it in the builder, point it at a sample of your documents and systems, and run it with you.