INTEGRATIONS · SYMBILITY
Symbility, from the Assignment to the Notes That Go Back
When the assignment arrives in one system and the file notes are written in another, somebody ends up typing the same claim twice.
VCA Software works with Symbility, where the field estimate is written. Assigned claims appear under unassigned claims in VCA ClaimsCore, where your team reviews and imports them, and file notes and activities go back to Symbility from the claim's Actions menu, for users whose profile carries a Symbility User ID.
ILLUSTRATION · ONE CLAIM, WORKED IN CLAIMSCORE
ASSIGNED FROM
Symbility
Where the field estimate is written, by the person standing in the loss
Claims come in on assignment, and file notes and activities go back to it
VCA CLAIMSCORE
The Claim of Record
- The Assigned ClaimIMPORTED
- The Reserve
- The Correspondence
- Payments on the Claim
WORKED FROM THE CLAIM
- Desk Review
- File Review and Quality
- The Client-Facing Lead
- Payment
Clients see their own claims too, through ClientPortal, an add-on
IN THE CLAIM
An estimate is rarely written once
Every version is a document that can be forwarded, saved to a desktop, and quoted back at you in a meeting by somebody holding an older one. With Symbility connected to ClaimsCore, the assigned claim is imported into ClaimsCore, and the claim is where your team keeps the notes and decisions that follow.
ONE CLAIM, THREE VERSIONS OF THE ESTIMATE
- The First EstimateWritten in the field, where the loss is, by the person standing in it.
- The SupplementThe contractor opens a wall and finds more. A second document now exists.
- The RevisionDesk review sends it back with questions. A third comes in.
- The PaymentSomebody pays against one of the three. An audit will ask which one it was.
WHAT MOVES
The Claim In, the Notes Back
Assigned claims come in from Symbility, and file notes and activities go back from the claim. Each user whose notes go back needs a Symbility User ID on their VCA profile.
- Out: File Notes and Activities, to Symbility. From the claim's Actions menu, for users with a Symbility User ID.
- In: the assigned claim, from Symbility, imported from unassigned claims.
- Without it: notes are retyped into a second system, and one claim has two records.
| What | Which Way | Where It Lands |
|---|---|---|
| The Assigned Claim | Into VCA ClaimsCore | Under unassigned claims, where your team reviews it and imports it. |
| File Notes and Activities | Back to Symbility | Sent from the claim's Actions menu, for users whose VCA profile carries a Symbility User ID. |
| The Claim Record | Kept in VCA ClaimsCore | The claim of record: notes, reserves, correspondence and the history of who did what. |
WHO FEELS IT
The People Who Work the Claim
A field estimator is fine either way. The cost of a loose document lands on the desk behind them. VCA was built from the claim up, by an adjuster, for the people who work the claim, and these three feel it first.
- The Desk ExaminerWorks the imported claim in ClaimsCore, next to the reserve and the correspondence, instead of in a second system.
- File Review and QualityAudits what the claim says, not what an inbox holds, with the history of who did what on the claim.
- The Client-Facing LeadAnswers a client's question from the claim itself. The call runs shorter than one that starts with a search for an attachment.
OFF THE DESK
The Same Claim, Typed Twice
The gain is quiet and daily: the claim comes in once, and the notes written on it go back without being retyped.
- Keying an assigned claim in by hand before the work can start.
- Retyping file notes into Symbility after they are written on the claim.
- Opening a second platform to answer a question about a claim.
- Reconstructing after the fact what the claim said on the day a decision was made.
The XactAnalysis connection · Claims software for IA firms · All integrations
THE BOUNDARY
One Claim, Two Systems
The estimate is written in the field, where that work belongs. The claim of record is kept in ClaimsCore, and that is where desk review, file review and the client-facing lead work from.
Here is a test worth running in any claims software evaluation: take an assigned claim from arrival to its first file note, and count how many times anyone typed the same thing into a second system.
Start the Connectivity ConversationHow Implementation Runs →
WHAT TO BRING TO THE CONNECTIVITY CONVERSATION
One real Symbility assignment: how it reaches your team today, who keys it in, and where the file notes end up.
Questions About Symbility and the Claim
How do Symbility claims get into VCA ClaimsCore?
Assigned claims appear under unassigned claims in VCA ClaimsCore. Your team reviews each one there and imports it, and from then on it is worked as a claim in ClaimsCore.
What goes back to Symbility?
File notes and activities, sent from the claim's Actions menu. Each user whose notes go back needs a Symbility User ID on their VCA profile, and it works for claims that were imported from Symbility. What your operation needs from the connection is confirmed in discovery, the first step of every VCA implementation.
How is the connection set up?
It starts with discovery, like every VCA implementation. In ClaimsCore, the integration is switched on with your Symbility account details, and each user who sends notes back gets a Symbility User ID on their profile.
Our carrier clients do not all route estimates the same way. Is that a problem?
It is a common shape, particularly for firms handling work for several carriers. Claims come into VCA ClaimsCore from both XactAnalysis and Symbility on assignment, and once a claim is in, your team works it in ClaimsCore either way.
Can our clients see documents on the claim?
With ClientPortal, an add-on, your clients get a branded login to the claims that concern them, read from the same claim your team works. Each document on the claim carries a Show On Portal flag, so your team decides whether a given document is shown. Without ClientPortal, the client-facing lead answers from the claim.
Why does this matter for a claim audit?
Because an audit asks what was known, when, and by whom. A claim worked in two systems answers that twice, and not always the same way. A claim worked in ClaimsCore keeps the notes, the reserve movements and the correspondence on one record, with the history of who did what.
Bring us a claim where the promise was hard to keep
Bring a Symbility assignment, and walk it from arrival to the first file note that goes back. Discovery starts there, before anything is configured.
Request a Demo
