Expand Flexibility and Control with New Claim, Workflow, and Vendor Tools
The March release brings a powerful set of updates designed to simplify claims handling, improve user workflows, and unlock new capabilities across the Snapsheet claims management platform.
With enhancements ranging from claim customization and workflow logic to vendor integration and data visibility, this release helps claims management experts streamline day-to-day operations while staying adaptable to evolving needs.
Here’s what’s new:
- Custom Loss Types now fully live and configurable through the new Claim Customization page
- Email status tracking enhancements enabled globally—no setup required
- Expanded workflow conditions, including date logic and “has value” text field operators
- Vendor Task API upgrades now return documents, notes, and property data
- SSO login updates for improved identity provider alignment
- Bulk task creation and persistent filters in Work Queues for faster claim navigation
- Data Warehouse additions to support deeper reporting and upcoming features
- Flexible user license imports with broader date format support
Whether you’re building smarter workflows, scaling vendor collaboration, or fine-tuning reporting, Snapsheet’s latest updates give you the tools to manage your claims with confidence.
Scroll down to explore the full March release notes and see how these enhancements can power your team’s success.
March 2025 Release Notes
API Updates
Social Security Numbers and Tax IDs added to Get Policy Webhook - Enhancement
The Get Policy Webhook can now capture Social Security numbers (SSN) for people and Tax IDs for businesses. Successful calls with the API will include this information in the people and businesses arrays, respectively.
If this information is included in the carrier’s policy administration system and mapped to Snapsheet Cloud, these fields will be included with other claim party details after claim creation.
Assignment Management Updates
User licenses integrated with Auto-assignment - Enhancement
In our November 2024 release, we introduced a beta enhancement to Auto-Assignment, allowing users to require that claims be assigned only to assignees with active licenses in specified jurisdictions.
This feature is now out of beta and generally available in all customer environments. Additionally, we have further enhanced this feature to also check for active licenses when assigning exposures.
This functionality requires several features to be enabled in your Snapsheet Claims environment to be utilized, including User Licenses. For more information, please reach out to your Snapsheet contact.
Claims Management Updates
Reason Codes for Closed Claims Available to All Customers - NEW FEATURE
To enable this feature, please send a request to your Snapsheet contact.
In our December 2024 preview, we introduced new functionality that would allow Snapsheet Claims to prompt users to provide a reason that explains why they’re closing a claim. This functionality is now generally available to all customers.
When this feature is enabled, users will be prompted to provide a reason for closing claims.
This data will be stored and help carriers analyze trends in claim denials and identifyopportunities for process improvement. The Claim View will also display the closure reason atthe top of the Claim Details and Claim Summary sections of the Claim View.
Additionally, organizations can now customize claim closure reasons via the new Claim Closed Reason Codes section on the Claim Customization page. This allows users to create custom reasons or modify the default list provided with the feature.
Finally, claim closed reason codes are also fully supported by the Claims APIs as of our February 5 release.
Coverage Codes For Claim Risk Investigation Requests Updated - Enhancement
ISO ClaimSearch requires specific coverage codes for property-related exposures to accurately analyze financial data. Using an incorrect coverage code may result in unexpected outcomes. To enhance risk detection accuracy, Snapsheet Claims will now assign one of the following property loss coverage codes to these exposures based on their type whenever payment information is provided with a risk investigation request:
- BLDG
- OT
- C
- UseOccupancy
This change applies only to claim risk investigation contributions for property claims where exposures have payments. If an exposure does not have payments, the coverages mapped in the Investigation Admin configurations will be contributed and processed without issue.
Communications Updates
Communication Template Keyword "Policy Account Name" Renamed - Enhancement
The "Policy Account Name" keyword in communication templates has been renamed to "Account Name" to better reflect its updated functionality.
Previously, this keyword populated the account name in communications only if the claim had an account name selected and the user’s environment had a policy integration enabled. Now, the "Account Name" keyword will populate as long as an account is selected on the claim, regardless of whether a policy integration is enabled.
Please note that only the keyword option’s name has been changed. When selected, the keyword will still show a variable name of {{ policy_account }} in the template’s body.
Database and Schema Updates
Claim IDs Added to Several Tables A new claim_id column has been added to the following data warehouse tables:
- Custom Fields
- custom_field_claims_enumeration_values
- custom_field_exposures
- custom_field_exposures_enumeration_values
- custom_field_injured_people_enumeration_values
- custom_field_injured_people
- custom_field_properties_enumeration_values
- custom_field_properties
- custom_field_vehicles
- custom_field_vehicles_enumeration_values
- Financials
- payees
- snap_and_sign_mfas
- snap_and_sign_signatures
- Injuries
- injury_costs
- injury_evaluations
- injury_medical_assessments
- injury_treatments
This change will facilitate joining these tables to the claims table.
Records that existed prior to this update will show no values in the new claim_id column. We’re planning to backfill those records with historical data in a future release.
Created and Updated Dates Added to Several Tables - Enhancement
New created_at and updated_at columns have been added to the following data warehouse tables:
- financial_payment_details
- medicares
- policies
- properties
- property_details
- providers
- vehicle_passenger_details
This change will facilitate tracking when records are created or updated.
Created and Updated Dates in Tags Table Updated - Enhancement
Previously, the created_at and updated_at columns in the tags table reflected the timestamps from the tag_definitions table. This meant that records in the tags table showed when the tag’s definition was created or updated.
Now, these columns in the tags table reflect when the tag was initially added to its associated tag target, providing more accurate tracking of tag usage.
Metrics Updates
Claim Type Filter Added to Several Dashboards - Enhancement
Users can now filter the following dashboards by claim type:
- Claims & Exposures
- Claims & Exposures Raw Data
- Operational Reporting
Vendor Management Updates
Pagination Added to Vendor Assignment Documents - Enhancement
Previously, the Documents card under an exposure’s Vendor Assignments tab displayed all documents attached to the assignment.
Now, the Documents card displays up to 50 documents at a time. Users can choose how many documents to display at a time. When the total number of documents exceeds the selected display limit, users can use pagination controls to navigate through the list. This change was made to improve usability when managing large volumes of vendor assignment documents.
Workflows Updates
Claim Loss Type Updated Event Added - Enhancement
A new event name—Claim Loss Type Updated—is now available in Workflows. With it, users with administrative permissions can now create automations that trigger when a claim’s loss type is changed.
Custom Fields Integration Available in All Environments - Enhancement
In January 2025, we released an enhancement that integrated Custom Fields and Workflows, allowing users to make their custom fields accessible in their workflows. At the time, customers had to request the feature be enabled in their Snapsheet Cloud environment.
Now, that enhancement will automatically be enabled in any customer environment that’s using the Custom Fields feature.
