AI for insurance brokers: renewals and claims, with advice left to you

Where a broker’s time goes

A renewal is rarely a single event. It is a history: the original placement, the changes over the year, the claims, the conversations with the client and the notes people made along the way. Pulling that history together before a renewal conversation takes time, and much of it is searching across email, documents and other systems.

Seesa is built to do that groundwork. It connects to the places where your records live, builds one memory from them and answers questions in plain language, with the sources shown. The idea is that your team starts each renewal or follow-up with the history already in view.

What Seesa prepares

Seesa’s insurance broking page lists the work it can help with.

• Renewal preparation and claims correspondence.
• Premium follow-ups.
• Preparation of evidence for internal reviews.

What stays with your team

Seesa’s insurance broking page is direct about this: regulated decisions stay with your team. Seesa does not state cover, give insurance advice, decide claims or reach fair-value conclusions. Nothing it drafts gives advice or assesses suitability, and it prepares information for the people responsible.

In daily use, that means a prepared draft is a starting point. A claims email is assembled from the correspondence on record and then read, edited and sent by a person. A renewal summary lists what the records show, and a person decides what to recommend. The same applies to review evidence: Seesa can gather it, and a person judges it. Seesa’s own website terms also say AI-generated outputs can be wrong and should be reviewed before being relied on.

Permissions and approvals

Brokerages hold sensitive information about clients and claims, and not every person needs to see all of it. Each person’s access governs what their Seesa can use. Sharing an answer does not have to mean sharing the records behind it.

You also set the permitted actions and approval rules for connected tools, so your team decides where Seesa can prepare work and where it can carry out agreed actions. Seesa confirms source connections, permissions and the first workflows before installation.

Why on your premises

Seesa’s models, company memory and agent execution run on an installation in your building, supplied, installed and managed by Pentatonic. Company memory is stored on that installation.

That is not the same as being disconnected. Seesa’s security page says source systems, user access and maintenance may use external services, and the company explains these connections as part of the deployment design. Pentatonic also documents the support connection, permissions and data-access arrangements for your deployment before it goes live.

Starting with one workflow

The insurance broking page suggests bringing a renewal or follow-up workflow your team wants to prepare with more context. That is a good place to begin: pick one, see what Seesa prepares, and compare it with how your team does the work today.

If you want a routine tailored to your brokerage, bespoke routines can be developed with Seesa’s specialists under a separately agreed scope. Seesa serves companies of all sizes. The insurance broking page shows how it applies, and the security page explains access and external connections.

Routines for recurring checks

Brokerages have work that repeats: following up premiums, preparing for renewals as they come round, assembling evidence for an internal review. Seesa lets regular work become a routine, written in plain English. The routine decides what Seesa gathers and drafts, and where a person’s approval is needed before anything moves on.

Seesa’s film says more than a hundred routines are ready to switch on and that you can write your own. Where you want help, the specialist engagements are optional and priced separately, and a routine is built with your team, checked against the work it needs to do and handed over so that your people can run and adapt it.

Questions your team can ask

Seesa answers questions in your own words, grounded in your company’s records. Seesa’s features page gives examples such as asking why an invoice is still unpaid, or what was agreed. In a brokerage, the same approach applies to the history around a client: what was said, what was sent and what is still open.

Each answer shows the sources behind it, so the person asking can open the underlying record and judge it for themselves. That matters in a regulated setting, where the reasoning behind a decision should rest on the records and on your people.

What a first conversation covers

Seesa’s contact page invites you to tell the team about your company and the work you have in mind, and the team will discuss your setup and arrange a demonstration. Standard setup includes installation, historical import, supported connections and permissions, and your proposal describes the scope before you order, so you know what is setup and what needs bespoke work.