It depends on whether the outcome already exists. An AI agent can tell a verified customer the outcome of their claim once the decision is recorded in the claims system, using approved wording. It must not predict an outcome that has not been decided, reinterpret the decision, or handle a challenge to a decline; those go to a person.
When does the outcome "exist" for the agent?
An outcome exists when the system of record says so: the claim status is final, the decision has a named decision-maker, and the amount or reason is attached. That is a sealed fact. Anything short of it is not an outcome, however likely it looks.
The common failure is inference. A claim marked "assessment complete, awaiting sign-off" looks almost decided, and a model will happily say "it looks like it will be approved". That sentence becomes a promise in the customer's mind and, often, in the complaint that follows. The rule is simple: the agent reports statuses until the status is final, then reports the decision.
What can the agent say, and what stays with a person?
| Situation | The agent may | Stays with a person |
|---|---|---|
| Claim still open | Give the current status and the next published step | Estimating the decision |
| Claim approved | Confirm the decision, the amount and when payment is due | Changing the amount |
| Claim partly approved | Give the amount and the recorded reason for the reduction | Explaining judgement behind the reduction |
| Claim declined | Confirm the decision exists and that a letter sets out the reasons | Discussing the reasons, any challenge, any complaint |
| Customer disputes the outcome | Log the dispute and the customer's points | Reviewing the decision |
Declines need care for a reason beyond tone. A decline usually carries reasons, the customer's rights to challenge, and how to complain. Those words are written by people who know the claim and are often reviewed before they go out. The agent can confirm the decision and point to the letter, but it should not paraphrase the reasons. A paraphrase can drop the condition that mattered.
An illustrative example
Take a home insurer's chat agent. A verified customer asks about a claim for a burst pipe.
The claims system shows the claim as settled: 2,000 approved, 500 deducted as the policy excess, payment issued yesterday. The agent tells the customer exactly that, gives the payment reference and when it should arrive. That is the whole job, and the agent can do it without a person.
A second customer asks about a storm claim. The system shows it declined, with the letter issued. The agent confirms that a decision has been made and sent, and offers to resend the letter. The customer asks why. The agent says the letter sets out the reasons in full and offers to connect them to the claims handler who made the decision. It does not summarise "wear and tear exclusion" in its own words. If the customer says they want to complain, the agent records it as a complaint and routes it.
What controls keep it safe?
- Final status only. The agent's capability reads the decision field, and only when it is final. Interim statuses use a separate, plainer script.
- Approved wording. Approval, part-approval and decline each have set phrasing. The agent fills in recorded values; it does not compose explanations.
- Verification before disclosure. Claim outcomes are personal data. The agent confirms identity first and never discusses a claim with a third party who has no recorded authority.
- Disclosure of what it is. Customers hearing a decision deserve to know they are talking to an AI and can reach a person; see whether an AI support agent should tell customers it is an AI.
- Outcome testing. Sample conversations about decisions and check the customer understood what happened and what they can do next, as in customer outcome testing with an AI agent.
The same pattern applies to other figures a customer asks for. Reporting a recorded fact is different from interpreting it, as whether an AI agent can tell a customer their balance shows for accounts.
Does the type of claim change the answer?
At the edges. A delivery claim is low stakes and often decided by rules, so an agent may make some of those decisions within limits. An insurance claim is decided by a person, and the agent only relays. Where a claim touches health information, access should be narrower still. If the customer asks how their data was used to decide, that has its own route: answering questions about how customer data is used.
Where Pryme fits
In Pryme, "read final claim decision" and "explain decision reasons" are separate capabilities with separate certificates. The decision arrives from the claims system stamped as sealed, so the agent can state it; anything less final is refused as an outcome. The wider rules are in the AI support agent that knows when to say no.
Questions people ask
Can the agent tell the customer when a decision will be made?
Only if the claims system holds a committed date or the business publishes a service standard. It must not estimate from how long similar claims took.
What if the claim outcome changes after the agent told the customer?
The agent's statement was correct when made, and the record shows which status it read. The customer should be told of the change by whoever changed the decision.
Can the agent tell a broker or solicitor the outcome?
Only where their authority is recorded on the claim. Otherwise it takes their details and passes the request to a person.