Salesforce Integration
Sync claims data, contacts, and documents between Regure and Salesforce. Salesforce manages customer relationships, sales pipeline, and service cases. Regure manages claims operations and documents.
Salesforce for customer relationships. Regure for claims operations.
Salesforce is the world's leading CRM platform for managing customer relationships, sales pipelines, and service operations. Insurance agencies, MGAs, and direct carriers use Salesforce to track leads, manage client accounts, run service operations, and analyze customer data across the entire lifecycle.
But Salesforce wasn't designed for insurance claims operations — document automation, FNOL workflows, adjuster collaboration, or regulatory compliance for claims files. Most insurers using Salesforce track basic claim information in Cases or custom Claim objects, but claims documents, workflows, and team collaboration happen in separate systems.
Regure provides API-ready integration with Salesforce to sync claim data, contacts, and documents between systems. Contacts and accounts sync from Salesforce to Regure for automatic policy and claimant matching. Claim records, activities, and documents sync from Regure back to Salesforce so your sales and service teams have complete customer visibility — policies, claims, and all interactions in one CRM view.
Your operations team uses Regure for claims processing with specialized insurance workflows and document automation. Your sales and service teams use Salesforce with complete claim history visible in account records. One source of truth for the customer relationship.
What syncs between Regure and Salesforce
Salesforce remains your source of truth for customer relationships and sales. Regure becomes your source of truth for claims operations.
From Salesforce to Regure
- Contacts (name, email, phone, address, contact preferences)
- Accounts (company name, account owner, account tier, industry)
- Opportunities (policies in pipeline, renewal opportunities, cross-sell prospects)
- Custom fields (account segmentation, service level agreements, communication preferences)
- Account hierarchy (parent-child relationships for complex commercial accounts)
When a claim is reported to Regure, the system searches Salesforce for matching contacts and accounts based on email, phone, or policy number. Contact details pre-populate the claim record automatically. Account owner and service level information from Salesforce can trigger claim assignment rules in Regure (e.g., platinum accounts route to senior adjusters).
From Regure to Salesforce
- Claim records (as Salesforce Cases or custom Claim objects)
- Claim activities (FNOL received, documents submitted, status changes, settlement issued)
- Document attachments (FNOL forms, photos, estimates, settlement letters)
- Notes and communications (adjuster notes, claimant messages, internal updates)
- Claim metrics (cycle time, settlement amount, reserves, litigation status)
As claims progress in Regure, activities log to Salesforce account timelines automatically. Customer service reps see complete claim history when reviewing accounts. All claim documents attach to Salesforce records so your team has a unified file view. Claim data flows into Salesforce reports and dashboards for executive visibility.
How to connect Regure to Salesforce
Regure's implementation team configures the Salesforce Connected App. Your Salesforce admin provides credentials and approves object mappings.
Connected App Authentication
Your Salesforce administrator creates a Connected App in Salesforce with API access permissions. Regure authenticates via OAuth 2.0 with token refresh for continuous access. No Salesforce code changes or custom development required. Works with all Salesforce editions (not limited to Financial Services Cloud).
Object Mapping
Map Regure claims to Salesforce objects. Most deployments use Cases for claims or create a custom Claim object. Map claim fields to Salesforce fields (claim number, status, loss date, settlement amount). Contact and Account mappings link Regure claims to existing Salesforce customer records.
Field Mapping & Sync Frequency
Configure which fields sync between systems and how often. Real-time sync via webhooks ensures instant updates when claim status changes. Scheduled sync (hourly or daily) works for batch updates. Control sync direction per field (one-way or bi-directional). Custom Salesforce fields are fully supported.
Testing & Go-Live
Test in Salesforce sandbox environment. Create test claims in Regure, verify claim records appear in Salesforce with correct data, confirm activities log to account timelines. Validate document attachments sync to Salesforce files. Production rollout after UAT approval. Monitor sync health via Regure dashboard.
How insurance organizations use Regure with Salesforce
Three common deployment patterns for agencies, MGAs, and carriers using Salesforce.
Unified Customer View
Service teams see complete claim history when reviewing Salesforce account records. Claims data syncs to Salesforce automatically — no manual updates required. When a customer calls asking about claim status, service reps see real-time updates in Salesforce without logging into Regure.
Account managers reviewing customer accounts for renewal see all historical claims with settlement amounts, cycle times, and claim types. This claims data informs renewal pricing and account strategy. Service issues that originated from claims (complaints, escalations) connect to the source claim record for complete context.
Service Team Access
Customer service reps handle inquiries about claim status, document requests, and payment timing — all from Salesforce. Claim activities log to Salesforce in real-time so service reps see the latest updates. Reps can view claim documents attached to Salesforce records without accessing Regure.
Service cases in Salesforce link to related claims automatically. When a customer opens a service case about a delayed payment, the case links to the source claim record. Service managers see trends (e.g., high complaint volume for specific claim types) and route escalations to claims leadership.
Reporting and BI
Claim data flows into Salesforce reports and dashboards for executive visibility. Build reports on claim volume by account, average cycle time by claim type, settlement amounts by geography, or litigation rates by line of business. All using native Salesforce reporting tools.
Einstein Analytics (Tableau CRM) can analyze claim data alongside sales and service data for unified customer insights. Identify accounts with high claim frequency for retention efforts. Correlate claim experience with customer lifetime value. Export claim data to external BI tools via Salesforce APIs.
Common questions about the Salesforce integration
Do we need Salesforce Financial Services Cloud?
No. The Regure integration works with any Salesforce edition — Sales Cloud, Service Cloud, or Financial Services Cloud. If you're using Financial Services Cloud, Regure can map claims to the native Policy and Claim objects. If you're using standard Salesforce, map claims to Cases or create a custom Claim object. Field mapping is fully configurable.
Can we use custom Salesforce objects for claims?
Yes. Map Regure claims to Salesforce Cases (standard object) or create a custom Claim object with fields specific to your business. Many customers create custom Claim objects to track insurance-specific fields (reserves, subrogation status, litigation flags) that don't fit the Case object structure. Custom objects and custom fields are fully supported.
How often does data sync between Regure and Salesforce?
You control sync frequency. Real-time sync via webhooks ensures instant updates when claim status changes in Regure or contact details change in Salesforce. Scheduled sync runs on a set interval (every hour, every 4 hours, daily) for batch updates. Most deployments use real-time sync for claim status and scheduled sync for contact data.
What happens if there's a sync conflict?
Regure is the source of truth for claim data (status, documents, settlement amount). Salesforce is the source of truth for customer data (contact details, account information). Conflicts are rare because each system owns different data. If a field is editable in both systems, you configure conflict resolution rules during setup (Salesforce wins, Regure wins, or manual review required).
Learn more about Regure and Salesforce
Solutions for Agencies
See how insurance agencies use Regure with Salesforce for claims automation and unified customer views across sales and service teams.
Claims Automation
Deep dive into Regure's FNOL automation, document processing, and workflow orchestration capabilities that sync to Salesforce.
Secure Collaboration
Learn how Regure's collaboration features (messaging, file sharing, portals) integrate with Salesforce for complete audit trails.
Related Integrations
Five things Salesforce FSC was never built to do
Salesforce FSC handles Client relationship management, Opportunity tracking, Policy renewals and does it well. These are the workflows that fall outside that scope — the ones that end up in inboxes and spreadsheets beside it. Regure runs them against the same book, or runs the whole operation where you would rather not keep two systems.
AI Subrogation Detection Agent
The gap. Adjusters handling high claim volumes miss subrogation opportunities because manual review of every police report, incident narrative, and medical record for third-party fault indicators is impossible at scale. Industry estimates suggest 10-15% of subrogation opportunities are not pursued due to identification failures.
What Regure does. Regure's AI reads every incoming claim document — police reports, FNOL narratives, witness statements, and incident photos — and flags subrogation indicators automatically. The agent identifies third-party involvement, potential product liability, and Workers' Comp employer negligence, routing identified opportunities to the subrogation unit with supporting evidence.
ReadsPolice reportFNOL narrativeMedical examination reportContractor inspection reportWitness statementsAI Fraud Triage Agent
The gap. Claims fraud costs the US insurance industry $80B annually. SIU teams cannot review every claim — manual referral rates of 1-3% mean the majority of fraudulent claims are paid without investigation. Document-level fraud signals (staged accident indicators, provider billing anomalies, claim inflation patterns) are invisible without AI analysis.
What Regure does. Regure analyzes every claim document against a fraud signal library: medical provider billing history, accident scenario consistency, claimant claim frequency, contractor pricing benchmarks, and document metadata anomalies. Claims exceeding configurable risk thresholds are automatically routed to SIU with an evidence package.
ReadsCMS-1500UB-04Police reportContractor invoiceFNOLIME reportCompliance Automation
The gap. Core insurance platforms generate transaction records but not the structured evidence that regulators require. FCA Consumer Duty evidence, DORA ICT incident logs, SAMA Cyber Framework controls, and US state market conduct examination responses require additional compilation effort that falls on compliance teams.
What Regure does. Regure sits between the core system's transaction data and the regulator's evidence requirements. Every document processed and decision made is automatically logged with cryptographic tamper-evidence. Regure generates structured evidence packages — FCA Consumer Duty outcome reports, DORA incident response logs, state examination responses — from operational data, eliminating manual compilation.
ReadsClaims decision recordsCustomer communication logsFNOL to settlement timelinePricing justification documentsRegulatory correspondenceRenewal Intelligence
The gap. Renewal teams in core systems see transaction history but lack the unstructured signal in claim narratives, broker communications, and loss survey reports that predict renewal outcomes. At-risk accounts are identified too late — typically at the 30-day mark when competitors have already presented alternatives.
What Regure does. Regure enriches core system renewal data with signals extracted from document workflows: claim frequency patterns, broker communication sentiment, loss control recommendation compliance, and market submission activity. Accounts with early deterioration signals are flagged 90+ days out for proactive retention actions.
ReadsLoss run reportsLoss control surveyRenewal applicationBroker correspondenceClaims development reportsClaims Leakage Prevention
The gap. Claims leakage — overpayment, coverage misapplication, missed recoveries, and process failures — costs insurers 4-10% of total claims spend. Core systems track payments but can't identify where and why leakage occurs across the document-heavy claims process.
What Regure does. Regure monitors every document touchpoint in the claims lifecycle against carrier-specific leakage indicators: contractor invoice vs. benchmark pricing, medical billing code consistency, reserve adequacy vs. document evidence, settlement authority adherence, and subrogation opportunity compliance. Leakage alerts are surfaced in real-time to supervisors.
ReadsContractor invoiceProperty damage estimateMedical bills (CMS-1500, UB-04)Reserve documentationSettlement authorization
How the connection to Salesforce Financial Services Cloud is actually configured is decided in implementation against the version you run — see how configuration works. For the document machinery underneath all five, see document processing.
Ready to sync claims data with Salesforce?
Book a demo with your Salesforce environment. We'll show you the Connected App setup, object mapping, and real-time sync in action.