New starter enablement
New starter enablement is the colleague a new joiner can ask anything without feeling awkward. It answers from your own documentation and connected channels, links to the page behind each answer so the joiner learns where things live, and records the questions it could not answer. It writes nothing and messages nobody.
Step by step
Ask anything, in plain English
A new joiner asks how something works, where a process lives or who owns a system, without needing the right search terms.
Answer from your own docs
The answer is drawn from the documentation, handbooks and connected channels your organisation already maintains.
Link the page behind it
Every answer carries a link to the source, so the joiner ends up knowing the map rather than only the answer.
Point at the owner
Where a question needs a person, the agent names the team or role that owns it instead of guessing at the answer.
Record the unanswered questions
Questions the documentation does not cover are logged for the enablement owner, which is the most honest onboarding backlog a team can have.
New starter opens the source
The joiner reads the linked page for anything that matters. The agent writes nothing back, sends nothing and changes nothing.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelCompanies hiring faster than they document, and teams where the same onboarding questions land in the same channel every month.
Escalation
When it asks a personThis agent changes nothing outside ollo, so it runs without an approval gate. Its output is still cited and reviewable.
Applications & Rights
Which tools it uses, and what it may do in each
ConfluenceRead only
NotionRead only
SlackRead only
Google DriveRead onlyVerification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Companies hiring faster than they document, and teams where the same onboarding questions land in the same channel every month.
What you’ll need
- Documentation spaces connected
- Channels in scope agreed
- Ownership map available
- Enablement owner for the gap list
What you get
- A cited answer with links
- A named owner for open questions
- A running list of documentation gaps
What it doesn’t do
It answers from documentation that exists. Where the documentation is wrong the answer will be wrong, and it does not replace a buddy, a code review or a proper onboarding plan.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
What does a new joiner see if the documentation is wrong?
The answer the document gives, with a link to it and its date. That is why the gap list matters: a wrong answer traced to a page is a documentation bug your enablement owner can fix, rather than a rumour passed between new starters.
Can it see things a new joiner should not?
No. It answers under the joiner's own permissions, so restricted spaces stay restricted. Access is a joining question, not something the agent works around.
Why does it not write anything?
Because it does not need to. This one only answers on screen, which means there is nothing to approve and no way for it to change a system of record. Where a team wants answers written back, that is a different agent with a gate.
What do we do with the gap list?
Treat it as an onboarding backlog. The questions new joiners ask that the documentation cannot answer are, in order, the pages worth writing next, and the list is generated by real questions rather than by guesswork.