Agent

Renewal review brief

Renewal meetings go well when somebody has read the file, and badly when the file was read in the taxi. This agent builds the brief ahead of the meeting: what is expiring, what has changed at the client according to your own correspondence, what has happened on claims, and the questions worth asking. Every point carries the document it came from.

How it runs

Step by step

01

Connect the client record

The policy file, the correspondence history and the claims record for that client, connected read-only.

02

Set the brief's structure

We use the pre-renewal brief your team already writes, so the output slots into the meeting you already run.

03

It reads the expiring position

Cover, limits, excesses, endorsements and warranties are set out as they currently stand, cited to the schedule.

04

It finds what has changed

New sites, new activities, disposals and anything else the correspondence records is surfaced against the expiring cover.

05

It drafts the questions

Points where the file is out of date or contradictory become questions to put to the client rather than assumptions in the brief.

06

The account executive approves

The brief is filed and used only after the account executive has read it and signed it off ahead of the meeting.

The harness

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 model

Account executives and handlers running a renewal book where the client's business has moved on and the file has not caught up.

Escalation

When it asks a person

The account executive approves the brief before the renewal meeting

Applications & Rights

Which tools it uses, and what it may do in each
SharePointRead only
GmailRead only
Google DriveReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every 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

Account executives and handlers running a renewal book where the client's business has moved on and the file has not caught up.

What you’ll need

  • Policy files and correspondence connected
  • The claims record readable
  • Your brief structure agreed
  • An account executive to approve

What you get

  • A pre-renewal brief in your format
  • A change list drawn from correspondence
  • Questions to put to the client

What it doesn’t do

It reports what your file says. It does not recommend cover, does not confirm what a market will offer at renewal, and where the correspondence and the schedule disagree it shows both rather than deciding which is right.

How you get it

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.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

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.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Manual pre-renewal file readingRenewal notes written from memory
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

How far ahead does it run?

At whatever lead time you set per class, which usually differs for a simple package and a layered programme. The brief is rebuilt if something material lands between the first draft and the meeting.

Does it read our emails with the client?

Only the mailbox you connect, with rights set per source. Most firms connect the shared account mailbox rather than personal ones, and that is the safer place to start.

Can it advise on whether cover is adequate?

No, and that boundary is deliberate. It sets out the position, the changes and the questions; whether cover is adequate is advice, and advice comes from the broker with their name on it.

What does it do with a client that has gone quiet?

It says so. Where there is no recent correspondence, the change section is short and the questions section is longer, which is a fair reflection of what you actually know.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.