Hesper AI integrations
Hesper works beside the claims system you already run. No rip-and-replace, no second place for adjusters to work, and no decision taken out of your team's hands.
In short
Hesper AI runs beside your claims system of record, not instead of it. The core system keeps the claim, the reserves, the payments and the audit trail. Hesper reads the claim and its documents, runs its agents across coverage, investigation, settlement and recovery, then writes cited findings, evidence and drafts back onto the file. Your team keeps every decision.
How Hesper sits beside a claims system of record
A core claims system is built to record and govern a claim: who did what, when, and under what authority. It is very good at that. What it does not do is the work that produces those records - reading the documents, chasing the missing ones, querying databases, reconciling a recorded statement against a repair estimate. That work is still done by hand, one file at a time.
Hesper takes that layer. Its agents read the claim and every document attached to it, run coverage, investigation, valuation and recovery checks in parallel, and write the result back onto the claim as notes, documents and activities. The adjuster opens a file that is already assembled and cited, and then makes the call. Clean claims move through with the checks documented; claims with something wrong in them arrive with the problem already identified and evidenced.
- The claim, its exposures and its history
- Reserves, payments and financial transactions
- The authority matrix and who approved what
- The system-of-record audit trail
- The legwork behind the file, done in parallel
- Cited evidence and a reconstructed timeline
- Drafted coverage positions, responses and demands
- An activity naming the recommended next action
- No payment is released by an agent
- No claim is denied or closed by an agent
- No reserve is changed on an agent's own authority
- No decision leaves your adjusters and supervisors
Claims systems Hesper works beside
One page per system: what stays in the core system, how Hesper reads the claim file, what it writes back, and what an integration actually involves. Each page is dated, and we say plainly where we do and do not hold a vendor partnership.
What an integration actually involves
We will not put a go-live date on a web page. The schedule is set by how your claims system is deployed, how change is released into it, how long your security and data reviews take, and how wide a first slice you want. The sequence, though, is the same everywhere.
- 01
Scope
One line of business, one trigger, and a written definition of which claims are in scope and which never leave your environment.
- 02
Access
A connection to a non-production environment, with the claim fields and document types agreed in writing before anything is read.
- 03
Calibration
Hesper runs against closed claims your team already knows the answer to, and you compare its output with what actually happened.
- 04
Write-back
Findings, evidence packages and drafts begin landing on live claims as notes, documents and activities. Read-only first if you prefer.
- 05
Widen
More triggers, more lines of business, more of the claims lifecycle, at whatever pace your claims leadership sets.
Throughout, nothing is auto-paid and nothing is auto-denied. Hesper produces evidence, findings and drafts and opens an activity naming the recommended next action. Coverage positions, reserves, settlement authority, referral and denial stay with your people, under your existing authority matrix, recorded in your system of record.
Frequently asked questions
Which claims systems does Hesper work with?
Hesper integrates with the claims system of record rather than replacing it, and the pattern is the same whether that system is Guidewire, Duck Creek, Sapiens, Majesco or something built in house: read the claim and its documents, run the agents, write findings and drafts back onto the file. Pages for individual systems are published here as they are written. If yours is not listed yet, bring it to a demo and we will scope against what you actually run.
Does Hesper replace our claims administration system?
No, and it is not designed to. Replacing a core claims system is a multi-year programme. Adding claims automation beside one is a scoped integration against interfaces your system already exposes, and it can be narrowed or switched off without unwinding anything. The claim, the reserves, the payments and the audit trail stay where they are.
What access does Hesper actually need?
Read access to the claim record and the documents attached to it for the claims in scope, an agreed field and document set, and somewhere to write the output back as notes, documents and activities. A non-production environment for calibration makes the first phase much faster. Pull, push and scheduled batch exchange all work.
What if our claims system is home-grown or has no modern API?
Batch and file-based exchange are enough. The requirement is a reliable way for Hesper to receive the claim and its documents, and a place to put the output back where an adjuster will see it. Carriers on older systems often start with a scheduled queue of claims rather than an event-driven trigger.
Can Hesper pay, deny or close a claim automatically?
No. Hesper does not release payments, change reserves on its own, deny claims or close files. It produces evidence, findings and drafts, and it opens an activity naming the recommended next action. A person with the right authority makes every decision, and that decision is recorded in your system of record.
Is our claim data used to train models?
No. Claim data moves over encrypted connections and is encrypted at rest. Hesper is SOC 2 Type I attested and GDPR-ready. Claim data and Hesper's output are retained for the subscription term unless you instruct otherwise, and every agent action is logged with its sources, its reasoning and a timestamp.
Bring your architecture to a demo
30 minutes on your own claim types and your own claims system: what Hesper reads off the file, what it writes back, and what stays your team's call.
Book a demo