How to answer claim status questions from policyholders with an AI agent

"Where is my claim?" has a factual answer, and an agent can give it. Read from the claims system, it tells the policyholder the stage, what is still needed and from whom, and the next expected step. It does not predict the outcome, reveal reserves or investigations, or deliver a decision. Those stay with the claims handler.

What is a claim status enquiry, and who owns it?

After a claim is made, policyholders call and write to find out what is happening. Has my claim been registered? Did you get my photos? When will the loss adjuster visit? Has the payment gone? These contacts take handler time without moving the claim forward, and they rise sharply after weather events and other surges.

The claims function owns the claim and every decision on it. Customer support or a claims contact team owns the enquiry. Brokers and other authorised parties may ask on the policyholder's behalf. The agent answers enquiries at depth 3 because the answer is a read of the claims record, presented consistently. It stays well short of the decision, the boundary set out in our guide to the AI support agent that knows when to say no.

What are the steps, and at what depth?

1. Agent, depth 1: verifies the caller and their right to discuss this claim: the policyholder, a named party on the policy, or an authorised broker.
2. Agent, depth 1: reads the claim record. Stage, outstanding items, appointments, payments issued, and the handler or team assigned.
3. Agent, depth 3: reports the stage in the firm's approved stage descriptions, not the internal codes.
4. Agent, depth 3: lists what is outstanding: documents still needed, who is waiting for whom, and how to send them.
5. Agent, depth 3: gives the next expected step where the record holds one, such as a scheduled inspection or a payment date.
6. Agent, depth 1: recognises requests it cannot answer: "will you pay?", "how much will I get?", "why is it taking so long?" when the answer involves judgement.
7. Agent, depth 2: drafts a handler message with the policyholder's question, for the handler to answer directly.
8. Person, claims handler: makes and communicates every decision: cover, settlement amount, decline, or a request for further investigation.

Which controls matter, and what evidence does each leave?

Approved stage descriptions. Internal codes can mislead. "Referred" might mean a specialist review or a fraud check. The agent maps each code to approved customer wording. Evidence: the mapping version on each answer.

Hidden fields stay hidden. Reserve amounts, fraud referrals, internal notes and liability views are outside the agent's sources entirely, not just filtered at the reply. Evidence: the agent's source permissions.

No predictions. "Claims like this are usually paid" is outside scope, and certification tests for it. Evidence: scope-gate results and sampled conversations.

Decisions come from people. A decline or settlement is delivered by the handler, even if the record already shows it. Evidence: decision communications attributed to named handlers.

Every answer is filed. If a policyholder later says they were told the claim was approved, the record shows what was said. Evidence: the append-only record.

What should you measure?

• Status enquiries answered without transfer, by stage.
• Repeat enquiries on the same claim within a short period. Usually a sign the next step was not clear, or the claim is stuck.
• Handler messages drafted, and how long handlers take to reply.
• Claims stuck at one stage, which the agent's enquiries surface well.
• Complaints that mention the agent's information.

Where does it usually go wrong?

The record is out of date. A handler spoke to the policyholder yesterday and did not update the system. The agent repeats stale information. Make "last updated" part of every answer.

Stage implies outcome. "Approved for payment" read aloud before the handler has called the customer creates a decision the customer did not hear properly. Hold decision stages for the handler.

Investigations leak. A stage that reveals a fraud review can prejudice it. Keep such stages mapped to a neutral description.

Third parties are treated as policyholders. On a motor claim, the other driver may call about their own claim against your policyholder. They are not your customer and are owed different information. The agent should recognise them and route to the team handling third-party claims.

Vulnerable policyholders get the same script. Someone whose home is uninhabitable or who has been bereaved needs a person sooner. Route on those signals.

Status and payment questions mix. "Has the money gone?" is part claim, part payment. The agent can confirm a payment was issued from the claims record; tracing it is a payments question, much as answering billing questions with an AI agent separates explanation from adjustment.

Where Pryme fits

The Pryme Context Protocol lets you give the agent the claims record as a sealed source while leaving reserves and investigation notes out of its sources altogether. Attest certifies status answers on your own past enquiries, including ones where the right answer was to pass the question to a handler.