From first notice to adjuster assignment — automated.
Fnolwise sits between your intake channels and your claims management system. In the time between a claimant's first contact and your adjuster's morning queue, Fnolwise resolves the four intake questions that drive every subsequent handling decision.
Five steps. Zero manual triage.
FNOL Received via Any Channel
The first notice arrives: a phone call transcript, web portal submission, email, mobile app filing, or agent-submitted ACORD form. Fnolwise ingests all formats simultaneously. No preferred channel — the intake operation handles whatever comes in.
Phone · IVR · Portal · Email · Mobile · AgentACORD Form Normalized
Incoming data is mapped to ACORD 1 (property), ACORD 2 (auto), or ACORD 4 (inland marine) field structure. Missing required fields are flagged. The output is a validated, structured ACORD record — regardless of how the claim arrived.
ACORD 1 · ACORD 2 · ACORD 4Coverage Verified via ISO PolicyServices
Fnolwise queries ISO PolicyServices to confirm the policy is in force at the date of loss. Coverage type is resolved — commercial property, commercial auto, or inland marine. A coverage dispute at the intake stage is prevented, not discovered four weeks later.
ISO PolicyServices APISeverity Scored + Fraud Screened
Fnolwise scores claim severity (Low / Medium / High / CAT) using reported damage type, commercial vs. personal line, location, and policy limits. Simultaneously, an ISO ClaimSearch lookup and pattern matching identifies fraud indicators. SIU referral threshold is evaluated against carrier-configured rules.
ISO ClaimSearch · Severity EngineRouting Decision Written to CMS
The completed triage record — coverage confirmation, severity score, fraud flag status, and adjuster routing decision — is written back to Guidewire ClaimCenter, Duck Creek Claims, or Insurity via API. Your adjuster opens a claim that already has its first-notice triage resolved.
Guidewire ClaimCenter API · Duck Creek · InsurityAPI-based integration with no custom middleware required. Fnolwise connects to your CMS via documented carrier-tenant isolated API credentials. IT scoping takes two to three sessions.
ACORD 1, 2, and 4 — every field captured
Fnolwise supports the three primary ACORD forms used in commercial P&C FNOL intake. Regardless of the channel, the output is a complete, validated ACORD record before triage begins.
| Form | Coverage Type | Key Fields Captured | Common Use |
|---|---|---|---|
ACORD 1 |
Commercial Property | Loss location, damage type, building occupancy, reported loss amount, date/time of loss | Commercial property losses: fire, water damage, structural |
ACORD 2 |
Commercial Auto | Vehicle description, driver information, accident description, third-party involvement, injuries reported | Fleet and commercial vehicle claims |
ACORD 4 |
Inland Marine | Covered property description, location at time of loss, reported value, circumstances of loss | Equipment, cargo, and contractor tools claims |