symphony-fleet-auto

Merge a single field into submissions.captured_fields. Use when you derive a value from a message (e.g., reporter texts back "Oct 4 morning" → set loss_date). Key must match an existing FieldDefinition. Triggers a re-evaluation of required_fields_status.

Add or remove an entry on submissions.conversion_blockers. Use when something is preventing the submission from being converted that does not show up in required_fields_status (e.g., reporter says policy has lapsed, contradiction between policy address and reported address).

Terminal. Archive the submission (intake_status → abandoned) when the inbound correspondence is not an actionable claim — spam, a sales pitch, a misdirected message, a duplicate of an existing matter, or a question that needs no claim. Use this instead of escalate_to_human when no human follow-up is warranted. Provide a clear reason; the adjuster sees it in the activity log. This action requires human approval.

Link the submission to a candidate policy by policy number. Use during email intake once the reporter has given (or you've extracted from an attachment) their policy number, so the candidate policy + its coverages appear in your context and the submission can be converted. Returns matched=false if no policy matches — ask the reporter to confirm the number. The candidate policy is required before convert_submission_to_claim.

Terminal. Route this submission's correspondence (the email thread + any attachments) onto an existing claim instead of creating a new one, and close the submission as a duplicate. Use when find_claims shows the inbound email is about a claim that already exists. The claim's driver then picks up the new message and documents. This action requires human approval.

Terminal. Convert the current submission into a Claim row. The claim driver will then open exposures explicitly via `create_exposures`. `coverage_codes` records your coverage hypothesis as advisory metadata on the conversion activity — pick the coverage codes you believe the loss implicates, but no exposure rows are created here. Only call when (a) required_fields_status is all satisfied AND (b) conversion_blockers is empty AND (c) you can confidently pick the coverage codes implicated. This action requires human approval.

Verify whether the claim's policy was in force at the date of loss. The deterministic lookup + plain-language rationale are computed as soon as you call this tool; when human approval is required, the adjuster sees the AI's verdict on the approval card and can confirm or override before it lands on the claim. The verdict is persisted to claim.extended_fields.policy_verified + policy_verification_notes and recorded as a 'policy_verification' work-activity. Call this as the FIRST step on a fresh claim. Call with no arguments — the lookup happens server-side.

Open one or more Exposures on the claim. Each exposure is the unit money attaches to — one Exposure per CoverageGrant the loss actually implicates. Use `policy_snapshot.coverageGrants` as the source of truth for `coverage_grant_id` (do not invent IDs); typical burst-pipe pattern is Coverage A (dwelling) + Coverage C (contents), plus D (ALE) if the home is uninhabitable. `claimant_party_id` is normally the insured (reporter on the submission); use a different party only when a third party is the claimant for that coverage line. `valuation_method` defaults to the CoverageGrant's own valuation_method — only override when you have a specific reason. Existing exposures on the same coverage_grant_id are silently skipped (idempotent on retry). Requires human approval when autopilot is off.

Set reserve amounts on one or more Exposures on this claim. Reserves are the insurer's running internal estimate of what each exposure is likely to cost — split into `reserve_indemnity` (paid to/for the insured for the loss itself: repairs, contents, ALE) and `reserve_expense` (fees, vendor costs, independent adjuster, etc.). At intake/exposure opening, base the number on cause-of-loss severity and the CoverageGrant's limit. Once an inspection or repair estimate is on file, re-call this tool to true up reserves to the estimate's per-coverage RCV — reserves are documentation and should track the latest evidence. Per-exposure `rationale` explains how you arrived at the amount (e.g., 'mid-size burst pipe, drywall + flooring two rooms ≈ $20k indemnity' or 'trued up from inspection report: Coverage A RCV $7,171.32'). Requires human approval when autopilot is off; auto-applied when autopilot is on.

Compute the deterministic payout breakdown for each exposure once the inspection report's per-coverage RCV and recoverable depreciation are known. The tool takes RCV and recoverable_depreciation per exposure (you read these off the verified inspection report fields and split per coverage), then deterministically: (1) computes ACV = RCV − depreciation, (2) applies the policy deductible exactly once — to the exposure with the highest RCV — using the deductibleAmount from that coverage's grant (typical: Coverage A's $1,000), (3) computes net_acv_payable_now = ACV − deductible (or just ACV for non-bearer exposures), (4) writes `depreciationAmount`, `appliedDeductibleAmount`, and `recoverableDepreciationOutstanding` to each Exposure. Returns the per-exposure breakdown including net_acv_payable used as the input to `propose_payment`. Auto-applied — pure math + DB write, no human gate.

Compute the Business Income (time-element) loss for a commercial-property claim, once the period of restoration is known from the engineering/restoration estimate. Deterministically computes gross BI = rooms_down × nights × daily_rate, subtracts the waiting-period (time) deductible, adds continuing expenses to get the BI loss, and reports Extra Expense alongside. Writes the BI loss to the exposure's indemnity reserve and stamps the full breakdown into extended_fields. Pass `reasonable_restoration_nights` so the tool flags when actual downtime exceeds the reasonable restoration period. ONLY run this after a restoration/engineering estimate has produced the period of restoration. Large payouts still gate at `propose_payment` for human/forensic approval. Auto-applied — pure math + DB write.

Zero out the outstanding recoverable depreciation (RCV holdback) on an exposure. Use this when the receipt-submission window has expired without receipts being provided (default: 180 days from the initial payment). The Config carries the timeline as a rule; the driver calls this tool only after the timer fires. Per-call `reason` is required — typically cites the cumulative timer (e.g., '180 days elapsed without receipts; per Config rule the holdback is forfeited.'). Auto-applied — no human gate; clearing an already-zero holdback is a no-op.