The XactAnalysis integration enables claim adjusters to seamlessly request, manage, and receive claim estimations directly within BriteCore. This integration supports both manual and automatic workflows, using the BriteCore integration platform to connect with XactAnalysis for real-time file sharing, estimation status updates, and assignment processing.
Key features include:
- A dedicated Estimations tab in claims.
- Automatic note logging for request and cancellation events.
- File syncing between XactAnalysis and BriteCore.
- Status tracking of inspections and field activity.
User Experience
Access the Estimations Tab
The Estimations tab is only visible when the XactAnalysis integration is installed and configured, and the claim’s associated policy type supports XactAnalysis.
Request an Estimation
Automatically
If your organization is integrated with XactAnalysis for claim estimation, BriteCore can enable automation:
- The request claim estimation flow is triggered after the adjuster assignment.
- This flow will only activate if:
- The XactAnalysis vendor is installed and configured.
- The policy type linked to the claim is configured to support estimation.
- The peril associated with the XactAnalysis integration is added to the claim.
If all conditions are met, the system will initiate an initial claim estimation request automatically.
Note: Please submit a support ticket to enable the XactAnalysis workflow and specify the applicable policy type and associated perils.
Manually
- On the Estimations tab, select Request Estimation.
- In the pop-up dialog box, select whether you are requesting a Supplemental or Initial request.
- An Initial request should be used for the first estimation of damages on a claim. A Supplemental request should be used when additional damages are discovered after the initial estimate has been completed or if corrections are needed. Selecting the correct type ensures the request is properly categorized and processed by the adjuster.
Note: After you request an estimation, the following system note is added: Claim Estimation requested by [User].
- An Initial request should be used for the first estimation of damages on a claim. A Supplemental request should be used when additional damages are discovered after the initial estimate has been completed or if corrections are needed. Selecting the correct type ensures the request is properly categorized and processed by the adjuster.
Cancel an Estimation
In some cases, an estimation request may need to be canceled—for example, if the scope of the damage changes significantly after the initial request, if a duplicate request was made by mistake, or if the claim is withdrawn or denied before the estimate is completed. Canceling unnecessary estimation requests helps maintain clean workflows and avoid confusion in the adjuster’s queue.
On the Estimations tab, select the open estimation you want to cancel, and then select Cancel Estimation.
Note: After you cancel an estimation, the following system note is added: Claim Estimation canceled by [User].
View Estimation Files
- On the Estimations tab, select View Files.
- On the Attachments tab, go to Root Folder / Claim Estimations / [Assignment ID] to view the files.
Get Automatic Updates from XactAnalysis
- When a status event (e.g., inspection date) is received:
- The related field in BriteCore is updated
- XactAnalysis status appears in the Estimations tab
- Estimation files (XML, PDFs, images) are auto-uploaded into the claim’s attachment folder once the field adjuster selects QA approved on the files the adjuster selects within XactAnalysis.
Configuration
Prerequisites
- Sign a separate contract with XactAnalysis.
- Get authentication credentials from Verisk.
Setup
To configure the XactAnalysis integration in BriteCore, follow these steps:
- In BriteCore, navigate to Settings > Vendor Integrations.
- Install the XactAnalysis integration:
- If the Install button for XactAnalysis is not enabled, please contact the BriteCore support team.
- Select Install for XactAnalysis.
- Follow the prompts in the pop-up wizard.
- Select New Authentication.
- Enter the XactAnalysis username and password, and then select Create.
- Confirm Vendor Visibility by copying and pasting both URLs as instructed.
- Select Finish.
- Navigate to the Installed Integrations screen, and then select Select Policy Types to configure the policy types that will utilize the XactAnalysis integration.
- Note: Submit a support ticket for BriteCore Cloud to enable the automated workflow. In the ticket, provide the associated perils and triggering events in which you’d like the initial estimation request to be sent over.
- Once the integration is configured, each user who will need access to XactAnalysis will need to have their individual contact record set up. Proceed to the Activate Contact Record section of this document.
Contact Record Activation
To route the estimation request to the appropriate adjuster in XactAnalysis, you should enter the adjuster’s XactAnalysis credentials under their contact record. This ensures that whichever adjuster is assigned to the claim will receive the estimation request directly in their XactAnalysis queue when triggered.
For contact roles, Claims Adjusters:
- Additional Xact-specific fields appear in the Contacts module.
- The following fields support routing to the correct assignment queue:
- Carrier ID
- Recipient XN Address
- Profile Code
File Delivery and Retry Handling
BriteCore manages the secure transfer of files and updates between systems. If a file or status update fails to send, BriteCore will automatically retry the delivery at increasing time intervals to avoid disruption.
- Retry attempts are spaced out progressively (e.g., after 1 minute, then 2 minutes, 4 minutes, etc., up to approximately 8.5 hours).
- If all retry attempts are unsuccessful, the system automatically sends an alert to the BriteCore Team to review and resolve the issue.
Carrier Queue Priority
When sending to XactAnalysis, the system determines assignment by:
- 1st: Adjuster
- 2nd: Supervisor
- 3rd: Primary Carrier
Note: If an assignment based on the sequence above is not successful, the integration fails with a validation error.