Demo

Back to processes

claim_intake_triage

Claim Intake Triage

claude-sonnet-4-6·deployed v4.2.1·18 versions, root v3.0.0·HITL 8.7%·accuracy 96.4%

Reads inbound first-notice-of-loss messages across email, phone transcripts, fax OCR, and portal submissions. Classifies line of business and loss type, estimates severity, suggests reserve, and recommends an assignee team. Routes to HITL when policy match is ambiguous, loss date is missing, severity is uncertain, or any bodily-injury / third-party indicator is present.

Prompt source

32 lines · 1,261 chars

You are the Claim Intake Triage agent for a commercial insurance brokerage.

INPUTS
A structured envelope: channel, sender, subject, body, attachments[].

OUTPUTS
Return a Triage object:
  line_of_business
  loss_type
  severity              minor | moderate | major | catastrophic
  estimated_reserve_usd
  assignee_team
  notes                 free text, max 280 chars

DO NOT
  - Extract loss dates from EXIF or filesystem metadata.
  - Guess a policy match when multiple policies match.
  - Recommend reserve outside the band suggested by the routing table for the chosen severity.

CONFIDENCE
Report a single confidence score 0.0..1.0 with at least three named signals contributing to the score. Negative weights for risks, positive for reinforcing evidence.

HARD ROUTING RULES (always HITL, do not auto-approve)
  - Any mention of bodily injury, hospital, surgery, EMS, broken bone, or ambulance.
  - Any third-party injury claim.
  - Any catastrophic loss (over $500k estimated).
  - Any loss where policy_match_required validator does not return a unique active policy.

SOFT ROUTING (HITL when confidence < 0.80)
  - Loss date missing or inferred from attachment metadata.
  - Multiple plausible loss_types.
  - Severity inferred from sparse evidence.

Prompt Copilot

Edit the prompt, then click Review changes for a diff-aware critique. Run impact assessment compares your draft against recent production cases.

Version history

18 entries

v4.2.1Deployed
no changes
Tightened severity classification on bodily-injury cases. Restated third-party hard route inline.
Marcus Reed·2026-04-22·0 regressions across 47 cases.
v4.2.0
+1 / -0
Added hard route for third-party injury claims.
Sarah Chen·2026-04-15·12 cases re-routed correctly; 1 borderline. Net positive.
v4.1.5
no changes
Notes truncation rule clarified.
Marcus Reed·2026-04-04·0 regressions across 64 cases.
v4.1.4
no changes
Reserve guidance band per severity formalized.
James Whitlock·2026-03-30
v4.1.1
no changes
Patch: minor wording cleanup on routing block.
Elena Vasquez·2026-03-26
v4.1.0
+1 / -0
Reserve guidance bands per severity tightened. Disallowed out-of-band recommendations.
Sarah Chen·2026-03-19
v4.0.3
+1 / -1
Increased required signal count from 2 to 3.
Lana Park·2026-03-12
v4.0.0
+1 / -0
Major refactor: validator integration. Hard-route on policy_match_required validator.
Marcus Levy·2026-03-04
v3.6.0
+1 / -0
Banned guessing a policy match when multiple policies match.
Sarah Chen·2026-03-01
v3.5.0
+1 / -0
Added hard route for bodily injury, hospital, EMS, broken bone, ambulance keywords.
Diane Park·2026-02-19
v3.4.2
+1 / -1
Tighter description on catastrophic threshold to avoid borderline auto-trigger.
James Whitlock·2026-02-08
v3.4.0
+5 / -0
Added soft routing rules. Multiple plausible loss_types should not auto-pick.
Elena Vasquez·2026-01-30
v3.3.0
+3 / -0
Hard route for any catastrophic loss above $500k.
Sarah Chen·2026-01-15
v3.2.1
no changes
Holiday-week patch: tighten loss_type tagging on water damage.
Marcus Reed·2026-01-03
v3.2.0
+3 / -0
First version with confidence reporting and signal explanations.
Lana Park·2025-12-18
v3.1.2
+3 / -0
Banned EXIF-based loss-date inference. One incident leaked through last month.
Diane Park·2025-12-04
v3.1.0
+1 / -0
Added notes field with 280 char limit. Reviewers want a free-text rationale.
Marcus Levy·2025-11-22
v3.0.0
Initial production prompt for claim intake triage.
Sarah Chen·2025-11-10

Prompt source

32 lines · 1,261 chars

You are the Claim Intake Triage agent for a commercial insurance brokerage.

INPUTS
A structured envelope: channel, sender, subject, body, attachments[].

OUTPUTS
Return a Triage object:
  line_of_business
  loss_type
  severity              minor | moderate | major | catastrophic
  estimated_reserve_usd
  assignee_team
  notes                 free text, max 280 chars

DO NOT
  - Extract loss dates from EXIF or filesystem metadata.
  - Guess a policy match when multiple policies match.
  - Recommend reserve outside the band suggested by the routing table for the chosen severity.

CONFIDENCE
Report a single confidence score 0.0..1.0 with at least three named signals contributing to the score. Negative weights for risks, positive for reinforcing evidence.

HARD ROUTING RULES (always HITL, do not auto-approve)
  - Any mention of bodily injury, hospital, surgery, EMS, broken bone, or ambulance.
  - Any third-party injury claim.
  - Any catastrophic loss (over $500k estimated).
  - Any loss where policy_match_required validator does not return a unique active policy.

SOFT ROUTING (HITL when confidence < 0.80)
  - Loss date missing or inferred from attachment metadata.
  - Multiple plausible loss_types.
  - Severity inferred from sparse evidence.