How It Works

One gate. Every claim. A record you can audit.

Quixas is an AI-powered intake gate that sits out of band, beside your intake and never inside your systems. A forwarding rule sends each FNOL package to the gate. The gate reads it, checks it, and returns the flags and reasons. That is the whole footprint.

01Receive

The gate receives the whole package

Most intake failures hide between documents, not inside them. So Quixas reads the whole package together, not one file at a time.

A forwarding rule or secure upload is enough to start. No API project, and no writes to your claims system, ever.

One FNOL package

Email body

ACORD form

Estimate

Photos

Read as one claim

02Check

Completeness first, then consistency

Completeness confirms what your rulebook requires for that peril is present. Consistency is where the gate earns its keep: it checks that the claim agrees with itself.

A claim can pass completeness and fail consistency. Those are the claims that cost you the most, because without a gate they get worked before anyone notices.

Pass 1 · Completeness

InsuredPolicyDate of lossPerilPhotos

Pass 2 · Consistency

The stated peril is consistent with the damage described and the photos attached

The loss date falls inside the policy term

The ACORD form is consistent with the email narrative

Names, addresses, and policy details line up across every document

03Return

Every claim comes back with the reason attached.

Claims that pass both gates route straight to assignment. Flagged ones come back with the reason and a drafted follow-up your team reviews and sends. A human decides what happens next. Always.

Every check is logged, a documented record of your intake controls that you can put in front of a carrier during a review.

Result

Passes both gates

Routes straight to assignment.

Flagged

Comes back with the reason and a drafted follow-up.

Logged: checked · found · rule · time

Quixas audit trail screen showing a per-claim timeline of checks with timestamps, rule set versions, and reviewer actions. — Illustrative product views. Synthetic claim data.

Live interactive demo

Watch the gate run these steps.

It moves through the steps on its own, reads a claim, checks it, and pauses on the result. Replay it or try another claim whenever you like.

fnol_8841_wind.eml

Live demo · synthetic data

1Intake

2Extract

3Check

4Route

Receiving FNOL package

Claim C-8841 arrived via Intake mailbox forward.

Quixas reads the email, the ACORD form, and the attachments together, before anyone opens the file.

Running Intake...

Pipeline gains

Traditional Intake vs. Quixas Intake Gate

Securing complete, consistent property intake at the threshold transforms how claim handling times distribute.

FNOL arrives

One claim, two paths

Traditional / manual

Agent opens email, reads ACORD by hand

Manually checks fields and loss date

Gaps found days later, claim reset and re-chased

Gaps surface days later, under load.

Quixas intake gate

Intake gate, checked at intake

Gaps surface at intake, before assignment.

Architecture model

How Quixas Fits Your Stack

The gate sits beside your raw intake channels, out of band from your core claims systems.

A · Intake channels

ACORD documents, email bodies, and portal or upload submissions.

B · Quixas Intake Gate

Extracts the claim data, checks completeness and consistency (e.g. loss date within the policy period, the documents on file match what the claim states).

C · Your claims core

Your core claims system and system of record, where complete files are delivered.

The boundary

What the gate never does.

It never writes to your core systems

It never makes coverage determinations

It never sends anything without your team’s review

It never runs rules you haven’t seen and approved

The gate flags and drafts. A human reviews, sends, and decides.

The gate is only as good as the rulebook.

See how we build your completeness and consistency rules from your own claims and your own adjusters' judgment.

See the rulebook process