Instead of Salesforce Insurance Claims Management
Stop renting your Salesforce claims desk. Own it.
We bring your Salesforce claim records into a desk built around your handlers, evidence and service dates. Your insurer keeps decisions and financial operations.
Digital Insurance lists US$180,000 per organisation per year as an add-on and is included in Financial Services Cloud Max. Additional claims usage is US$50,000 per 50K credits.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
A claims desk and an insurance platform are different buying decisions
Compare the work you need against your current Salesforce package. The published platform price is not the price of this smaller administrative desk.
The insurance platform price
Digital Insurance lists US$180,000 per organisation per year as an add-on. It is included in Financial Services Cloud Max editions; check your edition before comparing costs.
Additional claims usage
Salesforce lists US$50,000 per block of 50K Claims Management credits. This is a usage block, not a claims-only annual subscription.
Intake and claim parties
The paid claims product includes guided intake, peril-specific attributes and claim-party records. The owned desk starts with the claim record, its handler and the evidence still needed.
Insurance decisions and financial operations
Salesforce includes adjudication rules, financial summaries and payment tracking. Keep these approved insurer functions in place while you move the administrative desk.
The Digital Insurance dependency
Claims Management usage requires Digital Insurance and cannot be purchased independently. Confirm what your existing package includes before changing any contract.
Your records and your next step
A Salesforce claim report can be exported for mapping. The first test is whether your claim numbers, handlers and source statuses reconcile, before planning a wider switch.
The owned desk
The claim, the missing evidence and the next follow-up
Daily diary
Know which claim needs a person today
Bring ownership and service follow-ups into the same daily review.
- check Read open claims by handler and age
- check See overdue acknowledgements and progress updates
- check Surface missing owners and unconfirmed service scope
- check Join the service diary with the evidence still missing
Evidence
Chase a specific record from a specific party
Every request has a description, a responsible party and a due date.
- check Find overdue assessor reports and claimant records
- check Record when evidence arrived and where it is held
- check See which third parties are holding up several claims
- check Draft an evidence request in your business name
Review
Keep the file review tied to the current record
A handler and a separate reviewer check the administrative file before closure.
- check See files with no outstanding evidence requests
- check Require a reviewer different from the handler
- check Flag records changed since their last review
- check Record closure against an external insurer resolution
Your process
Own the questions your claims desk asks
Start with tested records and shape the service process around your team.
- check Compare claim age by type and handler
- check Find late acknowledgements alongside the relevant dates
- check Produce private claim packs and service histories
- check Add your own fields, checks and read-only views
Make it yours
Design your own Salesforce Insurance Claims Management replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Insurance Claims Management. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Salesforce Insurance Claims Management data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Claims Desk for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Claims Desk for Claude Code
Connected to your own database
Which claims need attention today?
number | owner | evidence_overdue | ack_due | update_due | review_current CL-1001 | Mere | 2 | 2026-09-15 | 2026-10-16 | false CL-1002 | Mere | 0 | 2026-10-09 | 2026-10-19 | false CL-1004 | | 0 | 2026-10-16 | 2026-10-22 | false
Ask it anything
Questions Salesforce Insurance Claims Management cannot answer
Every one of these is a real question the demo answers today. Yours will be different, and that is the point.
Switching
How to switch from Salesforce Insurance Claims Management
A move involves exporting the claim records you need, mapping them to the new desk, checking the import and running both systems side by side before you switch.
- 1
Set the scope
Agree what is in scope before you export. Claims Desk is an administrative desk for claim headers, evidence requests, service dates and file reviews, not a replacement for policy administration, coverage decisions, reserves or payments. List the records and history you need to move, and confirm which systems will continue to handle work outside the claims desk.
- 2
Export your records
Export the claim headers you want to bring across, including claim number, claimant reference, policy reference, dates, type, summary, owner and source status. Export in a format your account allows, usually CSV or Excel, and check with Salesforce Insurance Claims Management about the available options. Attachments, communications, evidence requests and financial records need separate mapping and reconciliation if you choose to bring them.
- 3
Load a test run
Use a test run before loading records into your working database. The base imports mapped Salesforce claim headers, so check that your exported columns match the fields being imported. Once the test run looks right, load the records. Claims start open for reconciliation, even when Salesforce marked them closed, so do not treat the imported status as a confirmed final state.
- 4
Review flags and reconcile
Check what the test and import report, then compare a representative set of records with Salesforce. Resolve mismatched fields and missing information before relying on the new desk. Check service dates with the handler using the correct business-day calendar, and confirm whether service-code rules apply. Missing dates and unknown scope are surfaced, but the checks do not certify compliance.
- 5
Run both, then switch
Keep Salesforce Insurance Claims Management and Claims Desk available side by side for a short period. Compare active claim records and updates, and make sure your team knows which system to update during the overlap. When you have reconciled the records and agreed the new desk is ready, switch off Salesforce Insurance Claims Management. Keep policy and financial work in the systems approved for those responsibilities.
Where the real effort goes
The real work is usually mapping your own fields and service rules, then deciding how much history to bring. Claim headers are supported by the base import, while attachments, communications, evidence requests and financial records need separate mapping and reconciliation. When you have Enterprise DNA customise and run the desk, they handle the export mapping, added fields and service rules.
Not ready for a call?
Get your Salesforce Insurance Claims Management switch plan by email
We will send you the step-by-step plan for moving your business off Salesforce Insurance Claims Management, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Salesforce Insurance Claims Management switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your claims desk
Open source
Do it yourself
Free, open source
- 1 Clone the repo and install the dependencies
- 2 Run npm test and npm run demo on fictional data
- 3 Open it in Claude Code, Codex, OpenCode or Cursor
- 4 Export a Salesforce Claim report, map the headers and test the import
Built around your business
We customise it
One setup fee, then a retainer
- check Your claim types, fields and handler-confirmed service rules
- check Your Salesforce records mapped and reconciled
- check A web front end or different technology where your team needs it
- check Your document storage and team access agreed before use
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and operated through Omni by Enterprise DNA
- check Connected to your approved claims administration process
- check Backups, maintenance and agreed record checks handled for you
- check Your diary and evidence process updated as the business changes
Questions
Instead of Salesforce Insurance Claims Management, answered
Does this replace all of Salesforce Digital Insurance? expand_more
The free base covers claim headers, evidence requests, service dates and administrative file reviews. Your insurer keeps responsibility for policy administration, coverage decisions, reserves and payments. We agree the desk scope and connections before building your version.
What is the actual Salesforce price being compared? expand_more
The current pricing page lists Digital Insurance at US$180,000 per organisation annually as an add-on, with inclusion in Financial Services Cloud Max. Extra claims usage is US$50,000 per 50K credits and requires Digital Insurance. Confirm your edition, included usage and contract with Salesforce. This is not a claim that every claims team pays that amount.
How much of our existing history comes across? expand_more
The free version imports mapped Salesforce claim headers, including claim number, claimant reference, policy reference, dates, type, summary, owner and source status. Attachments, communications, evidence requests and financial records need separate mapping and reconciliation. We inspect a representative export before agreeing the migration.
Will it handle our service obligations and team access? expand_more
It checks recorded acknowledgement and progress dates, missing handlers and unconfirmed service-code scope. Your handler confirms applicability and dates using the correct calendar. These checks do not certify compliance. Team permissions, private storage and any claimant-facing experience are scoped into your custom version.
What do we pay Enterprise DNA? expand_more
The base is free and open source. You pay for your own hosting and assistant subscription when running it yourself. For a version customised and run for your business, there is one setup fee, then a retainer. Sam scopes that around your records, connections and operating needs.
Start with the claims work your team actually does
Spend 30 minutes with Sam reviewing your current bill, one representative claim and the evidence chase behind it. We agree which desk work belongs in your own system and how it fits around the insurance systems you retain.
Claims Desk for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Salesforce Insurance Claims Management?
Get your version built