thinkhard.SI

Prompt repository Customer support & success

Update a policyholder on the status of their claim

A policyholder asks where their claim stands, and you need an update on what is done and what is outstanding that never strays into deciding coverage.

Registry no.
SUP-053
Collection
Customer support & success
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
9

Customer support & successAny chat

The prompt

Score 10 of 10, Excellent

Use it when A policyholder asks where their claim stands, and you need an update on what is done and what is outstanding that never strays into deciding coverage.

  • {{policyholder_name}}
  • {{claim_reference}}
  • {{channel}}
  • {{sender_role}}
  • {{policyholder_message}}
  • {{claim_notes}}
  • {{service_standards}}
  • {{required_notices}}
  • {{stale_days}}
Full prompt and why it works
Prompt
Write a status update to {{policyholder_name}} about claim {{claim_reference}}, to send by {{channel}} from {{sender_role}}. People waiting on a claim are often dealing with damage or injury at the same time, and much of their stress comes from not knowing where things stand. The update should say what has happened, what is still needed and from whom, and when they will hear next, so that they can do their part and stop guessing.

The policyholder's question or last message:
"""
{{policyholder_message}}
"""

The claim file notes (dates received, documents in, inspections, adjuster actions, payments issued, open items):
"""
{{claim_notes}}
"""

Service standards or timelines we commit to, if any: {{service_standards}}
Notices we are required to include in claim letters, if any: {{required_notices}}

Use these labels, in this order, each at the start of its part:
Where your claim is: one or two sentences naming the current stage as the file shows it.
What has been done: a short list with dates.
What is still needed: each outstanding item, who it is needed from (you, a contractor, a medical office, another insurer, us), and by when if the file says.
What happens next: the next step and when to expect it, only from the notes or the service standards.
Questions: who to contact, and how.

Keep it under 220 words, in plain words. Avoid claim jargon such as "subrogation" or "reserve"; if a term is needed, explain it in a few words.

Do not:
- State or hint at a coverage decision, a settlement amount or an approval the adjuster has not recorded in the file. If the file shows no decision, say a decision has not been made yet.
- Estimate a payment date that the notes or service standards do not give.
- Comment on fault, liability or the other party.
- Repeat medical or other sensitive details beyond what the update needs.

For example, an outstanding item in the right form: "Repair estimate from your contractor: needed before the adjuster can review the roof damage. We have not received it yet." That example shows the form only.

A good update is one the policyholder could read aloud to a family member, and both would know what happens next.

Put required notices where they belong, word for word; if none are given, leave them out and do not invent any. If the notes conflict, the last entry is more than {{stale_days}} days old, or an item's owner is unclear, write [CHECK: what] in its place and add a first line "FOR THE ADJUSTER: check the file before sending."

Variables

{{policyholder_name}}
The policyholder's name as you address them.
{{claim_reference}}
The claim number.
{{channel}}
How the update will be sent, for example "email" or "the claims portal".
{{sender_role}}
Who it comes from, for example "your claims handler".
{{policyholder_message}}
The policyholder's question or latest message.
{{claim_notes}}
The claim file notes: dates, documents received, inspections, adjuster actions, payments, open items.
{{service_standards}}
Timelines you commit to, for example "contact within 2 business days of each new document", or "none".
{{required_notices}}
Any notice your rules or regulator require in claim letters, pasted exactly, or "none".
{{stale_days}}
After how many days without a file entry the notes count as out of date, for example 14.

Why it works

  • What to avoid. No coverage decision or payment date appears unless the adjuster has recorded it, so a friendly update never commits the insurer.
  • If unsure. Conflicting or stale notes and items with no clear owner are marked and sent back to the adjuster before the update goes out.
  • Format. Labeled parts with who owes each outstanding item answer the question the policyholder is really asking: what is holding this up.

How to use it

  1. Press Fill in blanks and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/insurance-claim-status-update

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "insurance-claim-status-update"}, or just ask for it by name.