Policy & advice desk
Policy and advice desk takes the routine questions off a legal team that is meant to be doing something harder. It answers from your own policies, standard positions and published guidance, cites the section behind each answer, and hands anything needing judgment to a lawyer. It repeats what your policy says; it does not advise.
Step by step
Take the question in channel
A colleague asks in the channel they already use, in whatever words they would use with a person.
Search the policy library
Policies, standard positions and approved guidance are searched, along with the precedent bank where it applies.
Answer with the citation
The answer quotes the relevant section and links to it, so the colleague can see the policy rather than take the agent's word.
Judge whether it is routine
Questions that need interpretation, involve a regulator, or have no covering policy are marked as needing a lawyer.
Route the rest to legal
Flagged questions go to the legal queue with the context already gathered, so the lawyer starts from something useful.
Lawyer reviews flagged answers
Anything the agent has marked as needing judgment is answered by a lawyer, who approves it before the colleague sees a reply.
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 modelIn-house legal teams answering the same procurement, data and policy questions weekly, and organisations where colleagues ask a lawyer because they cannot find the policy.
Escalation
When it asks a personA lawyer reviews any answer flagged as needing judgment before it is sent
Applications & Rights
Which tools it uses, and what it may do in each
ConfluenceRead only
SharePointRead only
NotionRead only
SlackReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
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
In-house legal teams answering the same procurement, data and policy questions weekly, and organisations where colleagues ask a lawyer because they cannot find the policy.
What you’ll need
- Policy library connected and current
- Routine and non-routine boundary agreed
- Legal queue and channel set up
- Lawyer on rota to review
What you get
- A cited answer from policy
- A routed question with context
- A log of the questions asked
What it doesn’t do
It repeats and cites what your policies say. It does not give legal advice, interpret a policy in a new situation, or answer anything from a regulator, and it routes all of those to a lawyer.
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
Is this giving legal advice?
No, and the boundary is built into the agent rather than left to a disclaimer. It answers only where a written policy covers the question and cites the section it came from. Anything requiring interpretation is routed to a lawyer, and that boundary is agreed with your team during the co-build.
What happens when the policy is silent?
It says the policy does not cover the question and passes it to legal with the context attached. Silence is a useful signal too, and the log of unanswered questions tends to be the best guide to which policy needs writing next.
Can we keep a record of what colleagues were told?
Yes. Every answer and its citation is logged, which matters when a decision has to be explained after the fact. That log is also how a team spots a policy being misread across the business.
Does it apply to privileged material?
Only material you connect and scope to it, and most teams keep privileged matter files well outside this agent's reach. Deciding what the desk may read is a scoping decision made with your team, not a default we set.