Claims history lookup
The answer to a claims question is nearly always in a file somebody else opened. This agent reads across the claims records you connect and answers in plain English with the file and the date cited, whether the question is about one claim or a pattern across a book. A handler still confirms the position before it is repeated outside the firm.
Step by step
Connect the claims records
Claim files, correspondence and loss runs, connected read-only with rights set by team.
Agree your claims vocabulary
Your own terms for status, reserve movements and settlement stages, so a question in house language returns the right thing.
It indexes the history
The agent maps claims to clients, policies and periods, including the files that were never named consistently.
The team asks in the channel
Questions are asked where the team already works, and each answer comes back with the claim reference and the document.
It shows the working
For a question about a pattern, the agent lists the claims behind the answer rather than only the conclusion.
A handler confirms before it travels
Nothing is repeated to a client or an insurer until a handler has checked the position against the file itself.
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 modelBrokers and claims handlers answering client questions on the spot, and account executives preparing for a meeting where claims will come up.
Escalation
When it asks a personA handler confirms the position against the file before it is repeated to a client or an insurer
Applications & Rights
Which tools it uses, and what it may do in each
SharePointRead only
DropboxRead only
Google DriveRead only
SlackWrites 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
Brokers and claims handlers answering client questions on the spot, and account executives preparing for a meeting where claims will come up.
What you’ll need
- Claims records connected read-only
- Your claims vocabulary agreed
- A channel the agent may answer in
- A handler who confirms before anything travels
What you get
- Cited answers to claims questions
- A list of the claims behind a pattern
- A note where records are incomplete
What it doesn’t do
It reports what the claims records say at the moment it reads them, which is not the same as the insurer's current position. It makes no coverage determination, sets no reserve, and settles nothing.
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 it current with the insurer's own system?
Only as current as the records you connect, and it says which date its answer is drawn from. Where a position may have moved since, the handler checks with the insurer, which is why the confirmation step exists.
Can junior staff see the whole book?
Only what their permissions already allow. The agent inherits the rights on the underlying folders, so it does not become a route around the access controls you have set.
What about claims that were filed under the wrong client name?
It finds them more often than a name search does, because it maps on policy references and dates as well as names. Mismatched filing usually shows up as a by-product in the first weeks.
Does it write anything back to the claim file?
No. It posts answers into your channel and has no write access to the claims records themselves, so the file remains exactly what your handlers put in it.