Resource Library · November 2026

Claims Intake (FNOL) Agent Playbook

A first-notice agent that starts with what is already running, and a first case that can travel. Intake, routing and acknowledgement are in-scope. Coverage, liability and settlement are a person’s decision. Not a twelve-week guarantee.

28 pages40 min readIntermediateCompanion workbook included

By AsymiLink Meta · Published · Updated

Request the guide and workbook

Summary

A first-notice agent that starts with what is already running, and a first case that can travel. Intake, routing and acknowledgement are in-scope. Coverage, liability and settlement are a person’s decision. Not a twelve-week guarantee. Frameworks excerpted on this page: Six families of first-notice work; Fourteen design tests (excerpt). A 28 pages November 2026 document, with a companion workbook.

  • This service playbook is complementary to the Insurance AI Playbook, not a replacement. That playbook remains the industry map; this one takes the FNOL family in depth and will not give a different reading of the same firm.
  • Intake, routing and acknowledgement are in-scope. Coverage, liability and settlement are a person’s decision. The human gate is architecture, not a prompt.
  • For the illustrative insurer, the honest first work is to put two existing claims pilots on an inventory, then, if the tests pass, fund a bounded FNOL assist: extraction and completeness, with a person on anything that opens, pays, or denies.
  • Return is measured on a named process against a signed baseline, using the ROI guide. This playbook will not invent an FNOL-sector return, a cycle-time figure, or an STP rate, and will not promise a twelve-week go-live.

A crawlable plain-text copy of this page is also at /resources/claims-intake-fnol-playbook.txt. The canonical URL is https://asymilinkmeta.com/resources/claims-intake-fnol-playbook.

Written for Claims, operations and technology leaders, and the sponsors who have to fund a first-notice (FNOL) agent around a process that is already running.

What's in this playbook

This playbook is the operational document for a claims-intake (first notice of loss) agent. It is complementary to the Insurance AI Playbook already in this library, and is not a replacement for it. That playbook remains the industry map: six families, with FNOL as one of them, and a first case that puts two existing claims pilots on an inventory before a live claims use. This playbook will not reprint that map, and will not give a different reading of the same firm. The Agentic Workflows white paper remains the companion for a human gate as architecture; this playbook will not reprint its six patterns as deployments, and will not publish a migration roadmap.

What it is, instead, is a service playbook for the FNOL case: six families of first-notice work, fourteen design tests, and a first-case path consistent with that industry playbook. Intake, routing and acknowledgement are in-scope. Coverage, liability and settlement are a person’s decision. The human gate is architecture, not a prompt. A third claims pilot, an unsupervised settlement or deny, a coverage decision at intake, or a twelve-week claims framework, is not a first case this playbook will recommend. This playbook will not invent a “cycle time,” an “STP” rate, or an “accuracy” sector figure, and will not close a named insurance rule.

How the tests and the method are meant to be used

The financial method is The Complete Guide to AI Automation ROI. This playbook will not invent an FNOL-sector return, and it will not promise a twelve-week go-live. The 3.8x average first-year ROI across client engagements is an average, not a forecast or a commitment for any individual project. ROI is measured across client engagements against a baseline agreed before work starts. It is an average, not a forecast for any FNOL project, and is not used as a sector benchmark. Built to SOC 2 standards is the exact wording we use; it is not a certification of the reader’s system.

The illustrative firm is the same hypothetical mid-size property and casualty insurer as in the Insurance AI Playbook, the Enterprise AI Governance Framework, and the 2026 diagnostic: overall 15, Emerging, Governance the constraint at 1, with a next-step target of 24, Developing. Two claims pilots have been run; neither is in production with an operator. The honest first work is to put those two existing pilots on an inventory, with an owner, a sampling plan and a stop, and only then, if the tests pass, fund a bounded FNOL assist: extraction and completeness, with a person on anything that opens, pays, or denies. An unsupervised settlement or deny is not a first case. The target is a next level, not a timeline, and not a promise. A companion workbook, asymilink-claims-intake-fnol-playbook.xlsx, holds a family register, the fourteen tests, questions for counsel, a baseline sheet, and the same illustrative insurer. Do not wait to be Leading.

Six families of first-notice work

each with an honest first case, a case that is too wide, and a gate. Each item below is the shape of the map; the full wording, honest first cases and “too wide” warnings are in the PDF.

  1. F1

    Inventory of running claims systems (first)

  2. F2

    A bounded FNOL assist — extraction and completeness

  3. F3

    Routing and acknowledgement, with a person on the message

  4. F4

    A write into the claims system (later)

  5. F5

    An after-hours or volume assist that is still gated (later, and not the after-hours voice playbook)

  6. F6

    Hosting, decided before the case is funded

The PDF gives, for each family, an honest first case, a case that is too wide, and a defined gate. The summaries above are the shape of the map, not a substitute for that wording.

Fourteen design tests (excerpt)

Fourteen design tests are applied to every case. The answers will differ. The standard does not. The full wording is in the PDF and the companion workbook.

  1. T1–early

    a named inventory; a person on anything that opens, pays, denies, or sounds like coverage; counsel asked without a date taken from this document.

  2. Mid-tests

    a refusal to recommend an unsupervised settlement or a coverage decision at intake as a first case; a trail and a stop; hosting decided before the case is funded.

  3. Later tests

    a signed baseline on the ROI method; a write into the claims system as a later design, not a first case.

A completed test sheet is not a certificate, not a compliance score, and not a finding that a system is safe or aligned with a named regime.

Get the guide and workbook

Enter your name, work email and company. The files appear on this page immediately. A backup download link is also emailed when email delivery is available.

By requesting this resource you agree that AsymiLink Meta may contact you about it. See our Privacy Policy and Terms of Use.

Frequently asked questions

What is a good first FNOL case?

For a firm in the shape of the illustrative insurer, put the two existing claims pilots on an inventory, with an owner, a sampling plan and a stop. If the tests pass, a bounded FNOL assist — extraction and completeness, with a person on anything that opens, pays, or denies — is the honest claims case. A third claims pilot, an unsupervised settlement or deny, or a coverage decision at intake, is the wrong first case.

Are coverage, liability and settlement in-scope for the agent?

No. Intake, routing and acknowledgement are in-scope. Coverage, liability and settlement are a person’s decision. The human gate is architecture, not a prompt.

Is this a second copy of the Insurance AI Playbook?

No. That playbook remains the industry map, with the same first-case reading of the same insurer. This service playbook takes the FNOL family in depth, will not reprint that map, and will not give a different reading of the same firm.

Will this playbook invent a “cycle time” or “STP” figure, or promise a twelve-week go-live?

No. The financial method is the ROI guide, on a named process of yours, against a signed baseline. This playbook will not invent an FNOL-sector return, a “cycle time,” or an “STP” rate, and will not promise a twelve-week go-live.

What does “Built to SOC 2 standards” mean here?

It is the exact wording we use for how we build. It is not a certification of your system, and not a finding that a system is aligned with any named insurance rule.

How is the reported first-year ROI used?

The 3.8x average first-year ROI across client engagements is an average, measured against a baseline agreed before work starts. It is not a forecast for any individual project, and not an FNOL-sector benchmark.