Claims Integrations

Verisk, maker of XactAnalysis and Xactimate Alacrity Solutions

Claims integrations connect Cloudflow services with external claims or job systems. Cloudflow supports XactAnalysis (Xactimate) and Alacrity (Alacnet).

Supported Pattern

Claims providers can pull services, push services, or sync a specific service depending on the provider. Services created from a claims provider can be found on the Services page with the Integrations filter.

Xactimate-Oriented Flow

The service creation API already includes optional claims-sync handling for Xactimate-style structural assignment. When enabled, the request must include a date of loss and either a claim number or service identifier.

XactAnalysis

Open Integrations and choose XactAnalysis to connect and configure it.

Importing Assignments

  • Dataset mappings route each XactAnalysis dataset to a Cloudflow parent customer and a starting status. Once you add a mapping, datasets without one are not imported.
  • A legacy default parent customer and initial status apply only while no dataset mappings exist.
  • Job type mappings match XactAnalysis job types to Cloudflow service types. A Default service type is used when an assignment has no job type.
  • Initial status by service type lets a service type start in a different status than the default.
  • Each assignment has one document in Cloudflow. When a delivered copy arrives it replaces the earlier queued copy rather than creating a second one.
  • Individual customers are matched on email address alone. A customer change you make by hand is kept.

Updates Sent Back to XactAnalysis

  • Status action mappings trigger one or more XactAnalysis actions, such as QA approved or Client approved, when a service enters a mapped status.
  • QA approved and Client approved are treated as complete only when XactAnalysis confirms them. A successful request is not enough, so Cloudflow keeps retrying until the confirmation arrives or the service leaves that status.
  • Outbound Files controls which photos and documents are sent, and each file type can upload immediately or wait until the service reaches a chosen status.
  • Outbound Assignments rules let Cloudflow create XactAnalysis assignments for services that belong to a parent customer.

Inbound Status Changes

Status changes made in XactAnalysis are recorded on the linked service as they arrive. They do not create notes by default.

Alacrity

Open Integrations and choose Alacrity to enter your credentials and settings.

  • Auto acknowledge assignments accepts pending assignments before Cloudflow imports them. When it is off, an acknowledgement indicator shows on services that still need a response, and you can accept or decline from there.
  • Acknowledging is one-way. If an assignment was already acknowledged in Alacrity, Cloudflow treats it as done.
  • Auto mark customer contacted records Customer Contacted using the time the assignment was imported. It only applies after the assignment has been acknowledged and is not applied when a contact date already exists.
  • Trade name mappings assign service types and parent customers from Alacrity trade names. Set a Default status and Default service type for imports that do not match a mapping.
  • Sync schedule controls how often updates are exchanged. Run sync exchanges notes, schedules, and updates immediately.
  • Recent acknowledgements and Sync history show recent activity.
  • Alacrity imports do not trigger the older initial-status automations.

Operational Guidance

Use claims sync when Cloudflow is the operational workspace but another system owns parts of claims intake, assignment, or activity.


Did this page help you?