Compliance-first
Voice AI for FNOL & Claims Intake.
Meet Fern, your AI voice agent for first notice of loss and claims intake. Capture incident details, identify missing information and prepare a structured handoff, within reviewed state requirements and your claims SOP.
-
Shorter cycle timeFirst notice is taken at any hour, so adjusters start on a complete file sooner.
-
Fewer touches per claimPolicy, loss details and evidence come in one conversation, with no callbacks or re-keying.
-
Higher first-contact resolutionCallers finish the first call with a logged report and a clear next step.
Built for P&C carriers · TPAs · Claims operations
From first hello to a structured handoff.
Fern runs the intake conversation end to end. Anything that needs judgment goes to your people.
- 1Identify intentUsing the approved intake script.
- 2Verify identityThrough your configured process.
- 3Capture incident detailsConfirms facts, dates, location and missing evidence.
- 4AcknowledgeApproved receipt and next steps.
- 5Check completenessValidates supported document fields; follows up missing items under approved rules.
- 6Prepare handoffStructured claim form and handoff record with the active rule version.
- Intent
- New claim · Auto
- Identity
- Verified
- Incident
- Rear-end collision · Mar 3, 5:40 pm · Sacramento, CA
- Acknowledged
- Receipt and next steps sent
- Documents
- Photos received · Police report Follow-up sent
- Completeness
- 11 of 12 required fields
- Rule version
- CA intake rules v3.2
Built around applicable state requirements and your claims SOPs.
Monitor both rule sets, map affected intake steps and draft updates. Your claims team reviews and activates them. Nothing changes until you approve it.
State requirements
Applicable external rules for the jurisdiction and workflow
- Source trackedCalifornia claims notice ruleAcknowledge a claim notice within 15 calendar daysSource + version kept
- Proposed intake stepRecord the notice date and create an "acknowledge by" taskNot live yet
- Compliance leadRevised ApprovedEarlier draft Archived
- In every intakeNotice date loggedAcknowledgement task createdReview record kept
Your claims SOPs
Your own approved intake process
- SOP updatedMotor intake procedure, v4Damage photos are required for every collision reportSource + version kept
- Proposed intake stepIf photos are missing, text an upload link and follow up the next dayNot live yet
- Claims managerPhoto step ApprovedVersion 3 Archived
- In every intakePhotos requested by textFollow-up scheduledReview record kept
Fern supports intake and handoff. Coverage, liability and settlement decisions stay with authorized claims personnel. Illustrative example; not legal advice or a certification of compliance.
Email claims intake pilot for a California-based insurance company
Better intake feeds better extraction. Better extraction feeds better triage.
A three-week pilot for a California-based insurance company. Dyna.ai reads each incoming claim notice, sends it to the right line of business, checks nothing is missing and files a draft claim in Guidewire ClaimCenter. A person approves every claim.
- Notice arrivesShared claims inbox
- Agent parsesReads the notice and OCRs attachments
- Classifies & validatesClaim type and policy check
- Checks & draftsCompleteness check, then a draft FNOL with documents
- Human approvesReviews the draft; the claimant gets an automatic acknowledgement
A proposed pilot plan, not a completed deployment or verified results. Client name withheld.
Clear scope.
Clear expectations.
Start with one useful workflow and the decisions your team needs to retain.
Does Fern decide whether a claim is covered?
No. Coverage, liability, acceptance and settlement remain with authorized claims personnel.
Can Fern work with our claims system?
Your system, required fields and read or write actions are assessed for the proposed workflow. Integration scope is confirmed separately.
Can Fern follow up on missing documents?
Follow-up and document steps depend on the operating scope, contact conditions and configured integrations.
What will the POC evaluate?
A defined intake workflow, including intake cycle time, touches, first-contact task completion, information quality and exception handling.
Smoother claims with fewer touches. Start with one claims workflow.
Apply for a Fern POC built around your intake goals, reviewed rules and human handoff.
Want to hear Fern first? Try a live voice demo