Skip to content

For claims and underwriting leaders at P&C carriers and MGAs

Every new claim triaged before adjusters log in

Say what happened and Tiersel opens the claim, scores the queue, checks coverage against the policy wording and prices the renewal. Every step shows the records it used, and nothing is opened, routed, reserved or sent until a person approves it.

Live demo on synthetic data · Built on Jev by TypeSafe AI

Preview

An animated example types requests as if they were spoken and shows the card Tiersel builds for each one.

For the VP Claims or Chief Claims Officer at a P&C carrier or MGA, with commercial underwriting leaders

The first hour of a claim goes to finding things.

An adjuster takes the call, then opens the policy system to confirm coverage, the claims system to check prior losses, a fraud tool for flags and a spreadsheet for caseloads. A coverage question means reading the form and every endorsement again. Renewal pricing means rebuilding loss runs by hand. The information exists. Pulling it together is the work that slows cycle time, and a rushed file is where leakage and missed fraud start.

$45Bestimated yearly cost of property and casualty insurance fraud in the U.S., before auto theft and workers' compensation, which the study counts separately.Coalition Against Insurance Fraud, The Impact of Insurance Fraud on the U.S. Economy, 2022$86Bin loss adjustment expense incurred by U.S. P&C insurers in 2025: the cost of investigating and settling claims, on top of the losses paid.NAIC, U.S. Property & Casualty and Title Insurance Industries, 2025 Full Year Results, 202619.3 daysaverage repair cycle time for repairable vehicles, down from 22.3 days the year before, among 9,455 customers who settled an auto claim.J.D. Power, 2025 U.S. Auto Claims Satisfaction Study, 202527%of auto claims in the same study were total losses, up from 16% in 2022. Claims of $2,000 or less fell to 20% of the total.J.D. Power, 2025 U.S. Auto Claims Satisfaction Study, 2025

4 agent workflows

Built for the work your team already does.

Each workflow starts from a sentence. The agent calls your systems, shows its evidence, and waits for a person before anything consequential happens. Every card below is the real, working interface.

Workflow 01 · Claims intake representative or desk adjuster

First notice of loss to an assigned claim

Claim intakeInsurance

  1. 01 · Trigger

    The loss is reported

    A policyholder calls, or a web or mobile report arrives, and the handler describes what happened in their own words.

  2. 02 · Tool call

    Find the policy and read the call

    Pulls incident facts from the call transcript, finds the policy in force, and checks which coverages and deductibles apply.

  3. 03 · Reasoning

    Check completeness and severity

    Lists what the file still needs, such as a police report number or photos, estimates severity and suggests a reserve.

  4. 04 · Tool call

    Match an adjuster

    Compares the loss type and severity with each adjuster's skills and open caseload.

  5. 05 · Human approval

    Handler approves

    The handler reviews the draft claim, chooses the adjuster and approves. The photo request goes to the insured only after approval.

    Nothing happens until a person approves

  6. 06 · Outcome

    Claim opened and assigned

    The claim is open, reserved and in an adjuster's queue, with the missing items already requested.

What changes

Intake that meant four systems and a callback becomes one spoken description and one approval, with nothing left off the file.

CCaaS platformPolicy administrationClaims systemAdjuster workload

Workflow 02 · Claims supervisor or triage unit

Morning triage of new claims

Claims triageInsurance

  1. 01 · Trigger

    New claims arrive

    Overnight and early-morning first notices land in the queue, and the supervisor asks for triage.

  2. 02 · Tool call

    Verify and look back

    Confirms each policy is in force and matches prior losses by insured, address and vehicle.

  3. 03 · Tool call

    Score each claim

    Scores fraud indicators against your SIU referral rules, and estimates severity, complexity and reserve.

  4. 04 · Reasoning

    Recommend a route

    Marks straight-through claims for fast track, sends complex or injury claims to the right adjuster and flags SIU referrals with the reasons.

  5. 05 · Human approval

    Supervisor approves in bulk

    The supervisor reviews the list, unticks anything they disagree with, and approves the routing.

    Nothing happens until a person approves

  6. 06 · Outcome

    Queue cleared

    Each claim has an owner and a reserve, and every SIU referral carries the indicators that triggered it.

What changes

The morning queue is sorted and assigned in one review, and fraud referrals come with evidence instead of a hunch.

Claims systemPolicy administrationPrior-loss historyFraud scoringAdjuster workload

Workflow 03 · Adjuster or coverage specialist

Coverage position on a reported loss

Coverage checkInsurance

  1. 01 · Trigger

    A coverage question

    An adjuster asks whether a specific loss is covered on a specific policy.

  2. 02 · Tool call

    Read the policy

    Pulls the declarations, the policy form and every endorsement on the policy, with the claim notes.

  3. 03 · Tool call

    Check the guidelines

    Searches your coverage guidelines for the peril and tests each exclusion against the facts on file.

  4. 04 · Reasoning

    Reach a verdict

    Returns covered, likely covered or excluded, quotes the governing clauses with section references and lists the facts that would change the answer.

  5. 05 · Human approval

    Adjuster approves the position

    The adjuster edits or approves the drafted position. Denials and reservations of rights go through your normal review.

    Nothing happens until a person approves

  6. 06 · Outcome

    A cited position on file

    The claim file holds the answer and the exact wording it rests on.

What changes

A coverage question gets an answer tied to the policy wording, with the exclusions that were considered written down.

Policy administrationPolicy forms libraryCoverage guidelinesClaims system

Workflow 04 · Commercial underwriter

Commercial renewal review

Renewal reviewInsurance

  1. 01 · Trigger

    Renewal comes up

    An account enters the renewal window, or the underwriter asks for it by name.

  2. 02 · Tool call

    Pull history and loss runs

    Reads five policy years of premium and losses, open claims with reserves, and the renewal application.

  3. 03 · Tool call

    Compare exposure and signals

    Compares units, values, revenue and locations to the expiring terms, and reads telematics or loss control findings.

  4. 04 · Reasoning

    Build the rate

    Breaks the indicated rate into loss experience, trend, exposure mix and credits, and offers retain, recommended and firm options with terms.

  5. 05 · Human approval

    Underwriter decides

    The underwriter picks the option and approves. Anything over their authority routes to a manager instead of the broker.

    Nothing happens until a person approves

  6. 06 · Outcome

    Terms to the broker

    The broker receives the quote and terms, and the rationale is saved on the account.

What changes

A renewal review that meant rebuilding loss runs by hand starts from a complete file and a rate build the underwriter can defend.

Policy administrationClaims systemRating engineTelematics or loss controlBroker portal

How it plugs in

An agent on your systems, one component per workflow.

Requests come in by voice, text or system event. The router picks the workflow, the agent calls your systems, and the answer lands as a live card where your team works. Nothing is written back until a person approves it.

In

VoicePush to talk, any browser
Typed requestSame intent, same card
System eventWebhook, queue or schedule

Tiersel

Intent routerPicks 1 of 4 workflows as you speak
First notice of loss to an assigned claimClaims intake representative or desk adjuster
Morning triage of new claimsClaims supervisor or triage unit
Coverage position on a reported lossAdjuster or coverage specialist
Commercial renewal reviewCommercial underwriter

Your systems

Claims and policyClaims system (e.g. Guidewire ClaimCenter, Duck Creek Claims), Policy administration
IntakeCCaaS platform, Web and mobile FNOL forms
Fraud and dataPrior-loss history, Fraud scoring model
UnderwritingRating engine, Loss runs
DocumentsPolicy forms and endorsements, Coverage guidelines

Out

Live cardIn your app, sidebar or kiosk
Human approvalHandler approves
Write-back + auditEvery call and decision logged

Workflow blueprint · Claims intake representative or desk adjuster

First notice of loss to an assigned claim

Starts when
The loss is reported. A policyholder calls, or a web or mobile report arrives, and the handler describes what happened in their own words.
Reads
Find the policy and read the call. Pulls incident facts from the call transcript, finds the policy in force, and checks which coverages and deductibles apply.
Match an adjuster. Compares the loss type and severity with each adjuster's skills and open caseload.
Decides
Check completeness and severity. Lists what the file still needs, such as a police report number or photos, estimates severity and suggests a reserve.
Waits for
Handler approves. The handler reviews the draft claim, chooses the adjuster and approves. The photo request goes to the insured only after approval.
Writes back
Claim opened and assigned. The claim is open, reserved and in an adjuster's queue, with the missing items already requested.
CCaaS platformPolicy administrationClaims systemAdjuster workload

This workflow is one component

export const fnol = defineSkill({
  id: "fnol", category: "insurance",
  // when this workflow, and not a neighbour, is meant
  criterion: "A claims handler reports a new loss (first notice of loss) from a caller's description and wants a claim opened: not triaging a queue of claims, not a coverage question, and not a health insurance or expense claim.",
  examples: ["open a claim, the customer rear ended someone on i-80 this morning", "start a new claim for a kitchen fire at 14 birch lane"],
  match: (text) => score, // intent score, runs on every word
  parse: (text, ctx) => record, // entities + tool calls into your systems
  reply: (record) => "…",
  Card: ClaimIntakeCard, // the live UI, with its approval step
});

The id, criterion, examples and reply are read live from the skill that renders the card above. Adding a workflow for your team means adding one of these: its intent, the calls it makes, what it says, and the interface your people approve in.

Fits your stack, answers to your people

Reads your systems. Acts only with approval.

What the agent connects to

Claims and policy

Claims system (e.g. Guidewire ClaimCenter, Duck Creek Claims)Policy administrationBilling

Intake

CCaaS platformWeb and mobile FNOL formsEmail and document intake

Fraud and data

Prior-loss historyFraud scoring modelWeather and geospatial dataVehicle history

Underwriting

Rating engineLoss runsTelematicsLoss control surveysBroker portal

Documents

Policy forms and endorsementsCoverage guidelinesDocument management

Product names are examples of systems in this category. Each deployment is connected to your systems through their APIs as part of the build.

A person approves every consequential step

Opening a claim, routing it, setting a reserve, sending a coverage position or quoting a broker waits for a named person. The agent prepares the action and stops.

Every step is logged

Each card shows the systems the agent read, what it found and how long it took. Approvals and rejections record who decided and when.

Least-privilege access in your environment

When deployed, the agent runs in your environment with scoped service accounts, so policyholder data stays there, and your reserve and rate authority limits are enforced as rules.

Synthetic data in this demo

Every policyholder, claim, policy form and account on this page is invented.

The cost of doing it by hand

Put your own numbers in.

Move the sliders to match your operation. Nothing is sent anywhere unless you choose to email it.

Each year

8,400

staff hours back, about 4.0 full-time people

$436,800

of staff time, at your hourly cost

Email me a pilot plan for these numbers

Covers the intake, triage and first coverage read on each claim, not the full adjustment or the settlement. The $52 default starts from the BLS May 2024 median wage for claims adjusters, examiners and investigators ($76,790 a year, about $36.92 an hour) and adds roughly 40 percent for benefits and overhead. The share is the part of those minutes the agent drafts for a person to approve. Change any number to match your operation.

Hours = claims a month × 12 × minutes each × share, ÷ 60. A full-time person is 2,080 hours a year. Default hourly cost from U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, 2024.

Questions buyers ask

Straight answers.

  • No. It drafts a position that quotes the clauses and lists the exclusions it considered. An adjuster or coverage specialist decides, and denials go through your usual review before anything reaches the policyholder.

  • When deployed, the agent runs in your environment and reads your claims and policy systems through scoped service accounts. Policyholder records stay there. This demo uses only synthetic data.

  • It is only as good as your data and your referral rules. Every score shows the indicators behind it so a supervisor can check it. A pilot replays a sample of your closed claims and compares the agent's routing and referrals with what actually happened.

  • No. It reads from and writes to the systems you already run, and it takes over the gathering and drafting. Adjusters keep the judgment calls, the conversations and the authority.

  • Pick one workflow, usually intake or morning triage, connect read-only access to the systems it needs, and run it next to your current process for a few weeks before turning on any write actions.

  • The demo on this page is free and needs no signup. For a pilot on your own data, book a call and we will scope it with you.

See it on your own workflow.

Watch the insurance claims workflows run end to end, or speak to the agent yourself. Then tell us which one to build on your data.

Scope a pilot with hello@sasid.ai
  1. 01

    Pick one workflow

    A short call to choose the workflow that costs you the most time, and who approves its actions.

  2. 02

    See it on your data

    We build that workflow against your sample or de-identified data so your team judges the real thing.

  3. 03

    Run it with people in charge

    Your staff use it on live work. The agent drafts and prepares; a person approves every consequential step.

  4. 04

    Decide from results

    You keep what measurably saves time and drop what does not.

Other operations

The same agent, other teams.