SLVRCLD | Capture

"Garbage in, garbage out," or so the saying goes. That is why SLVRCLD | Capture, the first phase of our solution, focusses on helping to correctly identify the lost, damaged or stolen items. Once identified, our product dataset enhances the product with a wide variety of structured attributes. It also does so using a format that can easily be read and understood by software – allowing downstream processes, both inside SLVRCLD's product suite as well as outside, to use and react to this information in an automated and dynamic way.

Who captures the item?

This depends on where you are in your digitization journey as well as the specific channel your customer is using. We provide several options.

Claims agent

This is currently the de facto way in which items are received from claimants (telephonically, via email or as text on a website) in a human readable, but otherwise unusable format. We provide a simple way for the agent to capture this information in a usable format, either through our Customer Web Portal or as a direct integration into your system.

Claimant on self help portal

Items are identified by the claimant at the claims stage, in a usable format. This can be done via SLVRCLD Snappy.Claims or through an integrated into your website, application or chatbot FNOL process.

Claimant via app or chatbot

Items are identified by the claimant at the claims stage, either inside the insurer's mobile application or through a chatbot FNOL process.

Catalogue

Capturing a claimants complete (or partial) collection of items, in a usable format, usually at policy inception.

If claims process in real-time, why have a catalogue?

SLVRCLD's catalogue functionality, part of SLVRCLD | Capture, is a great way to gather a snap-shot of your customer's possessions. This catalogue not only speeds up future claims, but when used in conjunction with SLVRCLD | Replace and SLVRCLD | Quantification, it also provides you with an exact valuation of their entire portfolio, updated on a weekly basis. This not only helps you mitigate the risk of having clients that are over or under insured, but also allows you to more accurately model for changes and fluxuations in the marketplace.

If you would like to know more, please reach out to us.

How do we capture the data?

The goal is to identify the claimed and match it up to one of our hundreds of thousands of items, both current and discontinued. But there is no one-size-fits-all solution, so we provide several options (with more on the way).

Make and model

Most common item identification method. Using the provided make and model, along with select specifications (such as storage capacity, screen size). This resembles the experience of an eCommerce site.

Barcode

Mostly used as a quick way to build a catelogue, since the barcode is usually not available after an incident.

IMEI

The International Mobile Equipment Identity (IMEI) number is a unique number associated with each mobile-phone-network capable device; including smartphones, SIM-capable tablets, etc.

Roadmap

What's next?

We believe item identification should be fast, simple and accurate. To this end we are constantly evaluating new and innovative ways to capture product data, both technically (in the form of serial numbers, visual recognition, etc), but also behaviorally by looking at ways to organise and categorise data in a way that makes sense to the claimant - especially after a loss, where the original item is no longer available.

Once identified, you can more onto SLVRCLD | Replace, which will help you identify whether the product is still active in the market or recommend a replacement if it is not. Alternatively you can proceed directly to SLVRCLD | Quantification to get a price, from your specific pannel of suppliers and in real-time.