Claimwell Mail Room · Product 01 · Standalone

Every document indexed the day it arrives. Written straight into your claims system.

The Claimwell Mail Room replaces the manual indexing operation. Scanned mail, fax, email, portal uploads, and employer feeds go into one queue. Each item comes out classified, matched to its claim, labeled, and written back with the provider, the service dates, and the codes already filled in. Your team handles the exceptions. Every page is traceable.

How it works

Capture, match, label, write back

Documents arrive the way they really do: multi-document scan batches, skewed pages, cover sheets, duplicate faxes, email replies without a reference number. The pipeline renders every page, reads it with layout-aware OCR and a vision model for handwriting and bad scans, classifies the document, extracts the identifiers and the domain fields, and searches your claims system for the match.

Reads what capture vendors miss

Handwritten dates, stamped provider names, degraded fax headers. Field-level confidence on every value.

Matches on evidence, not a barcode

Name, date of birth, last four of SSN, employer, claim number, reference token. Scored; thresholds are yours.

Catches the second fax

Duplicate detection across channels. The repeat is discarded with an audit record pointing at the original.

Your team runs the exception desk

Ambiguous matches, unreadable pages, documents with no claim. Ranked candidates, one click to resolve, every resolution audited.

Mail Room · today's batch
Attending Physician Statement
fax · matched CW-204118 · confidence 0.97 · 6 fields written
indexed
Claim form, 4 pages, skewed scan
scanned mail · new claim · shell created
indexed
Employer reply: last day worked
email · reference token matched · 1 field written
indexed
Attending Physician Statement
fax · duplicate of item 1 · discarded with audit
dup
APS, DOB mismatch on two candidates
fax · confidence 0.61 · below threshold
exception
Items in batch212 Indexed without a touch203 (95.8%) To the exception desk4 Median arrival to indexed11 min
What it writes into your system

The field catalog is the product

OCR is a component. The deliverable is a claim file where every document carries the fields your examiners and your downstream systems need, populated, cited, and scored. Mapped to your admin system's document and activity objects during implementation.

FieldExampleSourceEvery value carries
document_labelAttending Physician Statement · claim form · medical records · job description · authorization · employer statement · appeal letter · correspondence · otherclassifierconfidence score
page citation
channel and received time
batch and sender
model and prompt version
claim_matchCW-204118, matched on name + DOB + employermatcher
claimant_identifiersname, date of birth, SSN last four, employee idextraction
provider / facilitytreating physician, practice, NPI where printed, fax-back numberextraction
service_datesvisit date, date signed, period covered, surgery dateextraction
diagnosis_codesICD-10 codes and descriptions as printedextraction
key_dateslast day worked, expected return to work, delivery dateextraction
restrictionsas stated on the form, verbatim with page referenceextraction
senderprovider office, employer HR contact, claimant, attorneyclassifier + extraction
duplicate_ofdocument id of the original, when detectedduplicate detector
page_mapwhich pages belong to which document in a multi-document batchsplitter
activity"New APS received" on the claim, or an exception activity for a humanrouter

What the Mail Room does not do

It is an indexing product. It does not interpret, recommend, or decide. Your decisioning framework stays exactly where it is.

  • No interpretationIt records that a physician statement lists a diagnosis code and a return-to-work date. It does not say whether the claim is supported.
  • No routing to outcomesIt routes documents to claims and unmatched items to people. It never moves a claim's status.
  • No silent guessesBelow your confidence threshold, the item goes to the exception desk with ranked candidates, not into the wrong file.
Integration footprint

One adapter. Three endpoints. No runtime.

The standalone Mail Room is deliberately light: the document pipeline, the matcher, the write-back adapter, the exception desk, and the audit store. No workflow engine, no strategy layer, no model gateway beyond a single configured endpoint. It runs in your cloud account as one container stack.

claims · search and read

Fuzzy search by name, DOB, SSN last four, employer, reference token. Read the claim to confirm the match.

documents · create

Post the document with its label, extraction payload, confidence, and original pointer. Originals stay in your repository.

activities · create

"New document" on the claim for your examiners, or an exception activity for the desk.

contacts · create (optional)

Claimant and provider contacts when a first-notice document arrives for a claim that does not exist yet.

channels · read

Scan batch folder, fax inbox, mailbox, portal upload bucket, employer feed drop. Each is a drop point we read from.

audit store · ours

Append-only. Every classification, match, discard, and human resolution, with inputs and model version.

What you measure it on

The numbers the indexing team is already measured on

Arrival to indexed

Minutes, not days. Reported by channel and document type.

Touchless rate

Share of items indexed with no human. The rest went to the desk with candidates ranked.

Index accuracy

Audit-sample accuracy by field and document type, including degraded scans. Measured before go-live on your own mix.

Cost per document

Against the current vendor line. Backlog goes to zero on day one.

Send us a week of your mail

De-identified or synthetic, your choice. We run it through the pipeline and show you accuracy by document type before you commit to anything.