Agentic First Notice of Loss

This solution helps an insurer take a vehicle collision claim from the first notice of loss to a complete claim submitted to its claim management system. Policyholders report the loss in Mobile Insurance. The Claims Conversation Agent collects the incident details, offers roadside assistance and a rental car, and asks for photos and documents. Back-office agents analyze the evidence, draft the damage report, and answer policy questions, and Insurance Sync Services synchronizes the sample data and simulates a crash alert.

Pre-requirements

To install the Agentic First Notice of Loss solution, you must first add the Trial AI Model TrialClaudeHaiku4_5 to your tenant. In ODC Portal, go to INTEGRATE > AI models, select Add AI model, open the Trial tab, select Claude Haiku 4.5, and select Confirm. The solution's four agents use this model by default, so it must be available before you can install the solution from Forge.

Trial models work only in the development stage and stop working when their usage limit is reached. After installation, you can configure the agents to use your preferred AI model. To check how the Claims Policy and Fraud Agent and the Claims Document and Evidence Agent perform with the model you choose, run the solution's agent evaluation datasets. The documentation site explains how.

Documentation

Full step-by-step documentation is in the documentation site. Download the zip, extract it, and open index.html in a browser. Start with the Getting Started group.

Getting Started

After you install from Forge, complete these steps so the application is ready to run. Details are in Getting Started in the documentation site.

Open the main application. Replace [your-tenant-host] with your tenant hostname. The login page opens.

Mobile Insurance: [your-tenant-host]/CloneofMobileInsurance

Copy the host from that URL (it ends in .app). In ODC Portal, open Solutions Common Services and set DevelopmentDomain to that hostname. Refresh the application. The login page now shows a demo-user button:

• Mobile Insurance: Log in as Matthew Shelton
• If the button is missing, wait a moment and refresh. The setting can take a short time to propagate.
• In ODC Portal, open Clone of Insurance Sync Services and run the SyncScheduler timer to import the sample data, first for Solutions Common Services and then for Claims Services. Then log in to Mobile Insurance as Matthew Shelton and open the chat. The Claims Conversation Agent greets you and invites you to ask about your policy or report an incident.

Before you use the solution beyond development, change each Claims agent from the trial model TrialClaudeHaiku4_5 to an AI model of your own, and publish the agent. For details, refer to Getting Started step 4 and to Agent evaluations in the Claims Agents section of the documentation site.

When those steps are done, you can try the application.

Test First Notice of Loss Flow

The Claims Flow section of the documentation site describes each step of a First Notice of Loss claim. To try one, log in to Mobile Insurance as Matthew Shelton, open the chat, and report a vehicle collision. The Claims Conversation Agent checks that everyone is safe, looks up the policy, and captures the incident details. It then offers roadside assistance and a rental car, and asks for photos of the damage and the scene and for supporting documents. The conversation ends with the Claim Summary card, which shows the damage report drafted by the Claims Damage Report Agent. Submit the claim from that card.

Make it your own

The Getting Started page also has Make it your own, the list to review when you adapt the solution and before you go to production. Each module's section in the documentation site lists its best practices and its configuration and customization notes. The notes cover the settings, hardwired values, default values, and customization points of each module.

Typical customization points include:

• Agents: prompts, guardrails, tools, and AI models for the conversation, evidence, damage report, and policy agents
• Claims process: the claim statuses in Claims Services and the behavioral rule the Claims Conversation Agent follows at each one. The data model already defines the decisioning, adjuster review, and closing phases, if you want to cover them before the claim reaches your claim management system
• Coverage: the GetCoveragesFromPolicyDoc setting, which chooses between the policy coverages synchronized from your core system and the policy document read by the Claims Policy and Fraud Agent
• Integrations: replace the sample claim management, car rental, and roadside providers in the Integration Wrappers with your own systems
• Data sync: wire the retrieval actions to your core system while Insurance Sync Services keeps checkpoints and run records
• Crash detection: replace the simulated crash alert with an actual crash detection service, such as Apple Crash Detection
• Apps: the Mobile Insurance experience, without moving business rules into the UI

Before you go to production, also review the evaluation switch AgentEval_Enabled and the demo conveniences: sample users, sample coordinates, and the mock tow provider. Review the Google Maps API key. Use "Make it your own" together with the architecture and layer sections in the documentation site when you customize.