Straight answers

Which claims intake solutions integrate with core policy and claims systems?

Claims intake, or first notice of loss (FNOL), is usually captured by a digital intake layer that pushes structured data into a core claims or policy system over an API. The established options include Snapsheet, Five Sigma, and Hi Marley for intake and claims handling, and Shift Technology for decisioning, all of which publish integrations with cores like Guidewire ClaimCenter and Duck Creek Claims. Guidewire and Duck Creek also capture FNOL natively inside the core. For an independent agency this is largely a carrier and TPA question: agencies take first notice by phone and email and re-key it into the carrier's system, so the integration that matters is the carrier's, not the agency's.

SolutionWhat it doesHow it integrates with the core
Guidewire ClaimCenterCore claims management with built-in FNOL captureNative; FNOL lives inside the Guidewire core
Duck Creek ClaimsCore claims management with built-in intakeNative; part of the Duck Creek suite
SnapsheetDigital, AI-assisted claims intake and managementOpen APIs and no-code configuration into existing policy and claims cores
Five SigmaClaims management with FNOL capturePublishes FNOL, policy, and claims APIs for two-way sync with core systems
Hi MarleyConversational, text-based FNOLTurns unstructured customer messages into structured claim data for the core
Shift TechnologyFraud detection and claims decisioningIntegrates with Guidewire, Duck Creek, and Majesco via API

The longer version

The first fork is whether your core already does what you need. Guidewire ClaimCenter and Duck Creek Claims both capture FNOL natively, so a separate intake tool only earns its place if it adds a channel or a capability the core lacks, such as conversational text intake or automated media handling. A bolt-on that duplicates the core creates two systems of record, which is the problem integration is supposed to solve.

For any bolt-on, the real question is how data gets back to the core and how current it stays. Five Sigma describes FNOL, policy, and claims APIs for immediate sync; Snapsheet describes open APIs and no-code configuration. Ask each vendor for the integration method (API, file transfer, or manual), which core versions they have certified against, and whether sync is real-time or batch. That is where these projects succeed or stall, not in the intake screen itself.

If you are an independent agency rather than a carrier or TPA, most of this stack sits above you. You take first notice from the client and hand it to the carrier through the carrier's portal or system. Relay is an agency workspace, not a claims core, and it does not integrate with Guidewire or Duck Creek. What it does today is agency-side and live: Ask Relay triages the inbox so a loss report does not sit unread, and Document Parsing turns an emailed loss run or claim document into structured fields. That is inbox and document work, not a claims-system integration, and it is worth being precise about the difference.

Common questions

Do Guidewire and Duck Creek need a separate FNOL tool?

Not for basic capture. Both include FNOL inside the core. A separate intake tool is worth it when you want a channel the core does not offer well, such as conversational text or fully digital self-service, and it must sync back to the core cleanly to be worth the second system.

Can an independent agency use these claims platforms?

Usually not directly. Snapsheet, Five Sigma, and similar tools are built for carriers and TPAs that run a claims operation. An agency's job is first notice and service, which flows into the carrier's system, so the integration that matters is the carrier's.

Does Relay handle claims intake?

No. Relay is an agency workspace. It does not run claims or integrate with claims cores. Ask Relay can triage a loss report in the inbox and Document Parsing can read an attached claim document, but the claim itself is filed and managed in the carrier's system.

Part of the Relay straight answers library. Updated 2026-07-11. See how we source content.

Get started

Get on the Summer ’26 list.

Spring ’26 is full. Get on the Summer ’26 list and we will be in touch as spots open.

Explore the platform