
Answers on policies for agents and brokers, with the clause cited
When an intermediary has the customer in front of them and a doubt about a cover, they call the insurer and wait for someone to find the wording of the right edition.
The same questions, every day, to network support
Agents and brokers write to or phone the office that looks after the network to find out whether a cover applies to a given event, which excess applies to a policy issued years earlier or how far a replacement has got. The operator looks up the wording in the product archive, checks the edition, opens the portfolio for the policy's status and replies. The questions are very alike, but two operators can give two different readings of the same clause, and sometimes the intermediary calls back for confirmation before speaking to the customer.
The assistant answers citing the source, the operator steps in on doubtful cases
In the example, the assistant works in the portal or the email the network already uses and introduces itself as an AI system. It identifies the policy, reads in the Company Brain the wording of the edition under which it was issued and replies citing article and edition, showing each intermediary only the policies in their own portfolio. When the question touches a clause open to different readings, or asks for an exception, it hands the conversation to the operator, and we write the rules on those clauses with the people who know the product.
- The intermediary asks about a term or the status of a policy
- The assistant answers from the right edition, citing the clause
- On doubtful clauses or exceptions it hands the conversation to the operator
- The operator replies and flags the rule to be written
Illustrative example
Sources, modules and responsibilities of the network assistant
| Item | In this case |
|---|---|
| Data | In this casePolicy wording by edition, technical notes and circulars to the network, the policy portfolio with each policy's status, questions already received by support |
| Modules | In this caseCompany Brain, Workspace, Data Foundation |
| Who decides | In this caseThe support operator on the questions the assistant hands over; whoever is accountable for the product on the rules for the clauses; on whether a claim is covered, the claims handler always decides |
| What we measure | In this caseThe time taken to get an answer, questions handed to the operator, answers corrected by support and call-backs on the same question, against the starting point |
| AI Act risk class | In this caseThe assistant answers on terms and policy status and neither assesses risks nor sets premiums, so it does not perform the high-risk uses in Annex III that concern insurers, namely risk and life and health premiums for individuals. Anyone who writes to it must know they are dealing with an AI system. We classify the case with risk and compliance before development |
| Where to start | In this caseWith Deployment on a product line with definite editions, starting from the questions support receives most often, which can be read in the emails and requests already on file |
Where the wording has no definite version, tidy up first
If a product's editions cannot be told apart with certainty, the assistant risks citing the wrong clause with precision, and for the intermediary that is worse than a slow answer. In that case we first put the documents in order, and the project takes longer. It is also worth waiting when the network mostly asks for exceptions and commercial judgements, which remain work for the insurer's people.
The case comes from the insurance page.
Let's start from the questions your network asks most often
Together we read a sample of the requests that have reached network support, to understand how many find their answer in the written wording.