04 / Coverage

One platform, tuned to
the line you write.

The mechanics of a claim do not change much between lines of business. The parties, the correspondence, the documents and the deadlines change a great deal. The agents are configured to what each line actually produces.

Every line below is live work rather than a roadmap entry. Where a line is not listed, the honest answer is that we would want to look at the workflow before promising anything.

Organizations writing more than one line run the same agents across all of them, configured separately.

Line 01

Workers' compensation

The longest tail, the most parties, and the most correspondence per claim.

A workers' compensation claim is a relationship rather than a transaction. It runs for months or years, it involves an injured worker, an employer, one or more treating providers, sometimes an attorney and a regulator, and almost every one of those parties will call to ask where things stand.

It is also the line where the administrative load is heaviest. Wage statements have to be obtained, work status has to be tracked, treatment has to be authorized, jurisdictional forms have to be filed on time, and every one of those steps generates correspondence that somebody has to read and record.

This is where the agents carry the most. Intake takes the injury report from the employer at the end of a shift. Outreach chases the wage statement and the records. Status answers the worker who wants to know when the check arrives. The assistant reads the medical file when compensability is in question.

Parties on the claim
Injured worker, employer and payroll contact, treating physicians and specialists, imaging and therapy providers, examiners, nurse case managers, attorneys and the regulator.
Where the volume sits
Status calls from workers and employers, wage statement and work status chase, records requests, authorization follow-ups, and the correspondence each of those generates.
Documents the agents read
Injury reports, medical records and narrative reports, work status notes and restrictions, wage statements, examination reports, invoices and bills, and jurisdictional forms.
What is captured at intake
Mechanism and narrative of injury, body part and nature, date, time and place, employer and supervisor, witnesses where reported, treating provider, wage basis and jurisdiction.
Where agents stop
Compensability, reserve setting, benefit rate determination, settlement, and any dispute, complaint or regulatory matter.

Line 02

Property and casualty

High volume, surge driven, and decided on the quality of the first report.

Property and casualty claims arrive in waves. A storm, a freeze or a single bad week produces more first notices in forty-eight hours than the previous month, and the queue that forms in those hours determines how the whole event is handled.

Intake is where that is won or lost. A loss captured completely at first notice can be triaged, assigned and reserved immediately. A loss captured as a name, a phone number and a sentence becomes a callback, and a callback during a surge is a claim that waits three days.

The agents absorb the surge. Intake takes every report that arrives on every channel at once, without a queue forming behind a limited number of people. Status answers the policyholders calling to ask where their claim has got to. The document parser structures the estimates, invoices and inspection reports as they come in, so the adjuster opens a file rather than a folder.

Parties on the claim
Policyholder or insured, claimants and third parties, brokers and agents, contractors and repairers, adjusters and inspectors, and recovery or subrogation counterparties.
Where the volume sits
First notice of loss during surge, inbound status from policyholders and brokers, document intake from contractors and inspectors, and follow-up on outstanding documentation.
Documents the agents read
Loss reports and statements, photographs and inspection reports, estimates and scopes of work, invoices and receipts, police and incident reports, and policy documentation.
What is captured at intake
Policy and coverage reference, date, time and place of loss, cause and description, property or vehicle involved, damage detail, third parties and injuries, and immediate mitigation taken.
Where agents stop
Coverage determination, liability, reserve setting, settlement authority, and any claim your team flags as potentially fraudulent or catastrophic.

Line 03

Health

Volume measured in interactions, where being right the first time is the whole job.

Health claims generate fewer long running files and far more individual interactions. Members call about what is covered, what was applied to a deductible and why a claim processed the way it did. Providers call about eligibility, authorization and the status of a submitted claim.

Each of those conversations is short and each of them has a correct answer sitting in the record. The cost is not the difficulty of the question, it is the volume, and the real damage is a wrong or partial answer that produces a second call, an appeal, or a complaint.

The agents answer from the record and carry the context across the channel the member or provider chose. The same question asked by phone today and by email next week gets the same answer, because both are answered from the same assembled claim.

Parties on the claim
Members and their authorized representatives, treating providers and their billing offices, employer group contacts, and third-party administrators.
Where the volume sits
Member and provider status enquiries, eligibility and authorization questions, documentation requests, and outbound follow-up on incomplete submissions.
Documents the agents read
Claim submissions and remittance detail, authorization requests and determinations, clinical documentation supplied in support, and member correspondence.
What is captured
Member and policy identification, provider and service detail, dates of service, the question actually asked, and anything the caller volunteers that changes the record.
Where agents stop
Clinical judgment, medical necessity, benefit determination, appeals, and anything a member is not entitled to be told.

Configured per line, not per demo.

Running three lines on one platform only works if each line is configured for what it genuinely produces: its parties, its forms, its deadlines and its limits.

The same agent behaves differently in workers' compensation than it does in property, because the claim does. That configuration is agreed with the people who run each book, and it is theirs to change.

Who we work with

Built for the organizations that carry the file.

Different accountability, same operational problem.

Insurance carriers

Carriers running their own claims operation, where the agents absorb intake and status volume across the book and the adjusters keep the decisions and the regulatory accountability.

Third-party administrators

Administrators handling claims for multiple clients, where configuration differs per client and per programme, and where service levels on responsiveness are contractual rather than aspirational.

Self-insured employers

Employers carrying their own risk, usually with a small claims team and a large correspondence load, where the agents provide the handling capacity a bigger team would otherwise be hired for.

Brokers and partners

Brokers and partners who touch the claim at first notice and at status, and who need what they capture to arrive in the carrier or administrator's system complete.

Questions

Questions about fit.

We write a line that is not listed here.

Tell us about the workflow. The answer may well be yes, but we would rather look at the parties, the documents and the deadlines before we say so. A line we have not configured for is a project, not a switch, and pretending otherwise would waste your time.

We handle several lines on one team.

That is common and it is supported. The agents are configured per line, so the same intake agent asks different questions on a workers' compensation report than on a property loss, and routes to different places. Your team sees one queue behaving sensibly across both.

Our claims are too complex to automate.

The decisions in them probably are, and those are not what we automate. The intake, the status calls, the chase and the reading are mechanical in a complex claim too. Complexity usually increases the administrative load rather than reducing it, which is why the agents tend to carry more on the harder book, not less.

We operate in multiple jurisdictions.

Jurisdiction is part of the configuration: required fields at filing, forms, deadlines and what an agent is permitted to say all vary by where the claim sits. Multi-jurisdictional operations are the normal case in workers' compensation and the agents are set up per jurisdiction accordingly.

Next step

Start with the line that hurts.

One line, one queue, one workflow. We would rather prove it narrowly on your book than promise it broadly.

Get in touch