Intake operations
Loss notices are routed, parsed, reviewed, and approved before becoming claim files, with 24/7 claim setup, multilingual support, and intake help for carrier programs.
FNOLintake
Reviewbefore creation
Routeby program rules
Insurance ops
FNOL intake that turns notice into a clean claim file. Routed, reviewed, ready.
Corgi Claims turns loss notices, emails, call-center forwards, and program inputs into structured claim files with 24/7 claim setup and multilingual support.
Capabilities
FNOL intake without loose ends. Operationally specific, file by file.
Routed inboxes
Program inboxes route notices to the right organization and keep unmatched items visible for review.
Extracted facts
Structured fields, provenance, missing facts, conflicts, attachments, and raw source context stay attached to the draft.
Draft approval
Drafts can be reviewed, edited, approved, discarded, or reprocessed before becoming live claim files.
Claim creation
Approved intake creates the claim, insureds, parties, metadata, and audit trail without losing the original notice.
Operating process
A clean file rhythm. Every step has an owner.
- 01Receive notice
- 02Route to program
- 03Extract fields
- 04Review and approve
- 05Create claim file
Visibility and controls
FNOL is not a black box. Grounded in the file.
The intake workflow tracks inbound email, attachments, routing status, extracted fields, field provenance, missing facts, conflicts, and claim creation.
Routed inboxes support organization-specific intake flows.
Forwarded FNOLs can be reviewed on the TPA side before approval.
Approved drafts materialize into real claim records with audit metadata.
Service scope
What the page means in practice. Scope, focus, evidence.
AreaScopeOperating focus
ChannelsEmail FNOL, forwarded call-center intake, carrier submissions, and document-backed notices.Route the notice, preserve the source, and avoid duplicate claim creation.
Draft reviewExtracted facts, missing fields, conflicts, attachments, and editable payloads.Human approval before claim creation.
Claim setupCustomer claim number, insureds, parties, loss facts, claim type, and metadata.Clean handoff to adjusting and administration.
ExceptionsUnmatched routing, no enabled claim type, discarded notices, and reprocessing.Keep intake errors inspectable instead of buried in email.
FAQ
Questions carriers ask. Plain answers.
Can Corgi Claims handle email FNOL?
Yes. The intake workflow supports inbound email, attachments, routing, extracted facts, review, approval, and claim creation.
Does every notice become a claim automatically?
No. The model supports review and approval so bad routing, missing facts, and duplicates can be handled before creation.
What happens to attachments?
Attachments remain connected to the intake record and can move into the claim file as documents when the draft is approved.
Claims operations review