Remote Interviewing with Our Simple 2 Connect Integration

Remote Interviewing with Our Simple 2 Connect Integration

Remote interviewing has become increasingly important during covid, as restrictions may mean you can’t meet people face to face. Everything from doctor’s consultations to high school classes is now being done online, and interviews are no exception. But remote interviewing also enables you to save travel costs for your investigators, and thus save a significant part of your investigation costs. So Polonious has added an integration with Simple 2 Connect to enable easy remote interviewing for our clients. If you’d like to see it in action, we have a demo video below.

Additionally, this integration enables you to record the interview within the software and upload directly to Polonious. This saves you time, and saves you the security risk of having interviews saved on external devices.

For users and interviewees, we also make it simpler to organise and connect to interviews – that’s why it’s called Simple 2 Connect! On Polonious’ end, all the user has to do is click the appointment button and either start call immediately, or enter the appointment details. To join the call, they then click the ‘Splashlight’ button, and are taken to the S2C system, with Polonious handling the login details.

For the user, they simply receive some text messages and an email with the terms and conditions, and a link to join the meeting. They can join via phone from the SMS, or via computer from the email, with no software download required.

Once the interview is completed, simply hang up the call and give the file transfer a moment, and the video will appear in Polonious’ action history. As the video is now attached to the case, it can also be re-watched in the document preview. As an option, you can also have an audio only copy generated when it’s uploaded, to send to transcription services.

If you would like to speak to someone from Polonious about how you can benefit from remote interviewing capabilities, you can do so here.

Remote Interviewing - Appointment window with details

Enter appointment details from the Polonious action entry screen. You can book a future appointment, or start a call now.

Remote Interviewing - Interviewee SMS messages

Interviewees receive a simple set of 3 text messages providing them with terms and conditions and letting them connect via a link – no software download required.

In this short remote interviewing demo we will create an immediate call with ‘Clancy Claimant’, played by co-CEO Alastair Steel. We’ll create the call from Polonious, then click through to Simple 2 Connect and start the call. ‘Clancy’ will connect and tell us a little about the experience on his end, and then we’ll close the call. When we go back to Polonious and refresh the page, the recording is there, ready for us to do whatever we need to do with it!

Book a Demo Now

Would you like to see how Polonious’ can help you with easy, online interviews?

Insurance Assessing Made Easy

Insurance Assessing Made Easy

Did you know that Polonious also does insurance assessing and quote building? We have a demonstration video below so you can see it in action.

We set this up for a large insurer, who has thousands of assessors using the system, and many of them in the field, using it on a mobile device. It can be used for any kind of insurance assessing – property, auto, marine, and so on.

As with all Polonious features, it is configurable and flexible across a wide variety of use cases, in addition to insurance assessing. We are currently implementing this feature for ourselves, to enable speedier quote building for new deployments and configurations. So don’t worry if you’re not in insurance assessing, if you have or want Polonious and you quote for any of your work, have a chat to us and we’ll show you how it works for your use case.

The key aspects of this feature are:

  • ‘Areas’ which allow you to break your quote down into things like kitchens and bathrooms for property, roofs and quarter panels for auto, etc.
  • ‘Components’ which allow you to add costed items to each area to quote for repairs. E.G. basins, roof tiles, and floorboards, or bumpers, headlights, and windows. Each item is costed and the total is calculated from the number of items. Each component entry can be individually approved or rejected, or you can request a report justifying the expense.
  • ‘Excess/contribution’ allows you to enter the customer’s excess amount and the total contribution they’re willing to make, so you can arrive at a net cost.
  • ‘Cost summary’ calculates the total costs of components and fees, minus the excess contribution and displays it on the screen, so you can check before generating the cost statement.
  • ‘Cost Statement’ allows you to generate a PDF of the whole page, including the areas, components, and summary, for providing to the customer or vendor as a statement of work.

Additionally, you can add notes to the case and send alerts to the vendor regarding the assessment.

If you would like to speak to someone from Polonious to organise a live demo, you can do so here.

Insurance Assessing - Easily add components with costs

Easily add components with costs

Insurance assessing - easily approve or reject components and costs
One click approval or rejection of components or fees, or you can ask for a report to justify expenditure.
Insurance assessing - easily calculate total costs and net costs (minus excess and insured contribution)
Automatically calculate total costs including both components and fees, as well as net costs minus excess and any agreed contribution from the insured.

Book a Demo Now

Would you like to see how Polonious’ insurance assessing module can help you?
Welcome to Polonious News

Welcome to Polonious News

On behalf of the team, I’m excited to announce the new Polonious company newsletter, Polonious News.

It’s been a tough 18 months for everyone, and the combination of changing workflows and business practices means keeping informed has never been more important than ever.

That’s why Polonious News will be a vital channel for all our customers, partners, and staff to keep in touch with the latest company developments; industry trends; and investigation best practices.

The content in Polonious News will not be all about us and will include objective advisory across a range of topics – from improving business workflows to combating fraud and building a winning investigations team.

As we begin a new financial year several significant changes are now in place for Australia’s insurance industry. The new general insurance code of practice changes includes a raft of specific mandates that will forever change the way claims are processed and investigations are conducted.

The code of practice is being closely watched and we have produced a new guide to help you quickly locate the 42 points of compliance in the new code that directly impact insurance investigations.

New regulatory changes do not need to mean more of a compliance burden for your business. At Polonious we have been working hard to integrate the new regulatory requirements into the investigation fraud investigation process, allowing organisations to meet their compliance requirements and streamline their operations.

The result of better investigation processes? In addition to reducing the fraud bill, end customers are dealt with more professionally and are generally happier, which is great for referrals.

In other developments, we’ve also been speaking with our customers and investigation industry leaders on how to improve the overall investigation process. During the coming months we will be sharing some interesting findings we have researched on this topic. With better insights by their side, all investigation teams can drive productivity improvements.

Despite the uncertainty 2020 and 2021 has brought us, it is an exciting time to be involved in insurance technology and process improvement and I invite all our customers to see how Polonious can do even more for their business. And in 2021 we also hope to showcase some of the great work our customers are doing without our technology.

From myself and the team we hope you get a lot out of Polonious News which will arrive in your inbox monthly.

Yours sincerely,

Alastair Steel, Co-CEO Polonious Systems

One system, many teams, an opportunity to reduce costs and improve outcomes.

One system, many teams, an opportunity to reduce costs and improve outcomes.

Investigations are carried out across various business units and teams in an organization – HR, Information Protection, Corporate Security, Cyber Security, Brand Protection, Physical Security, Insider Threat, Customer Services and Health & Safety to name a few. 

Most teams will have a method of documenting their investigations and tracking progress and outcomes. Depending on the maturity of the company this could range from spreadsheets and emails to large enterprise applications. This is extremely inefficient and costing companies in terms of time, money and strategic outcomes.  

By implementing a single system to carry out investigations, you can unite teams from across the company – sharing skills, knowledge, and best practices. 

It’s never an easy task to rationalize systems from different business units, but the business case to do so can be compelling and the benefits felt across the wider organization.  

Here are a few examples of benefits: 

IT Support – A single system to support, administer and assure. 

Split Costs – Licensing split across many business units. 

KPI/KRI – Single source of metrics. 

Automation – Reduce manual activity and increase throughput. 

Consistency – Even with different processes it’s easy to ensure a robust investigation takes place. 

At Polonious we often help to rationalize systems and build bridges across business units. Want to know more? Contact us at [email protected]

New View Layout Builder

New View Layout Builder

Our new View Layout Builder, which was introduced in Polonious version 20.1 got additional capabilities with the recent 20.2 release, which we are introducing in this blog post.

The embedded video showcases how to configure a couple of widgets in the new view layout builder. This is an introduction to the ‘What You See Is What You Get’ configuration functionality being rolled out wherever possible across the system.

We have a number of very cool widgets available which we explain in a full instructional video we have available on request. However, for now we want to demonstrate the process of configuration with two basic widgets.

An important note on the new case view builder is that you can create a different view per case type. So you can e.g. show more photos on a surveillance case, fewer photos but more data on a factual or forensic case, and so on.

We believe your team can take on the task of building their own case views into a powerful, at-a-glance summary of the information most relevant to any particular case type.

So how does this help your team?

  • Easier configuration of case views – drag and drop widgets.
  • More flexible case views – move any info, anwhere.
  • More specific case views – more relevant info on cases.

 

Drag and drop view builder

Drag and drop configuration.

New View Intro Case View Page

In addition to being easier to build, the new Polonious view is much more flexible, and much cleaner.

So, what did we just see?

In an 8 minute video we added the main case data. In real life, you’ll do more building but less talking, so it’s very quick to build a whole view.

Different widgets have slightly different configuration, but it all follows roughly the same process. The more detailed widgets add more complexity, but it is still very easy.

We believe you can do this task now with no IT involvement required. This is a big saving in doing time, turnaround time and internal costs.

So what did we just see in terms of Polonious case view configuration?

You can easily select the case data you need to display for any particular case type.

It’s easy to lay it out in a neat, informative way that looks good in the new Polonious view.

You got a glimpse of the array of widgets available – please get in touch if you’d like to know more.

What else can we do with this new capability? What are the other possibilities?

With this new approach, and with the underlying functionality built out, it’s easier to add new widgets to further improve what you can do with the new case view.

We’ve also made it easier to upload new CSS to change the underlying look and feel in terms of background colours, logos, etc.

We hope you enjoy our new 20.2 release. We really look forward to seeing what your team are able to put together with this new capability.

If you have any questions or improvement suggestions, we are very keen to hear from you. Thank you.

Transcript

Hello it’s Nicholas from Polonious here with a quick introductory video to our new case layout feature. So this feature allows you to move everything around the page and lay it out whatever way you want, and it’s a new ‘what you see is what you get’ drag and drop tool that will allows you to completely change the layout of the case. We do have an instructional video on that coming but it is a 30-45 minute long video so not really good for an introduction. It has all of the details on how to set it up so if you’d like that, please get in touch with us, but for now we’re just going to give you a quick introduction.

So here, as you can see, is the old case view if you’re familiar with it, so on this there’s a lot of things that are fixed, it’s not movable and so what we’re going to do is just take some of this information here so you know what we should be seeing and then go just configure a couple of what we call widgets on the new case view. We won’t put all of this information on here just enough to show you how it works and then if you would like to get a breakdown of more of the widgets or things like that, or how you can replicate this case view then please get in touch with us for the instructional video.

So the first thing I’m going to do is enable a case view here so we’re going to make it the layout view, which is the new view, and we don’t have anything in here yet. I’ve selected this one so if we refresh this case it should go to the new view now, but there’s nothing on here because we haven’t set anything up, but you can see what was supposed to be on there before. So just to give you an example of this we’re just going to drag across say two field lists that kind of replicate that data that was at the stop at the top of the case and then just a table with a little bit of data in that.

So what we’ll do here is on this field list we’re going to grab some basic case data like the case number, a couple of organization levels, maybe a description, notes and a status and that should do us in this one for now. We’re going to select that we want the labels on the left, so this is just the names of each field that will be next to the values that tell you what it is. We’ll grab the details now, they can be left as they are and they will display like this or you can change them – so most of this is okay except this one doesn’t look particularly user friendly so we will just call that case status – and here you can change the number of rows, font size, formatting to make the labels look different, this is just the labels for now, and then we can also name the whole field. So this is to make sense of it in this view you can just name it as that and leave it with no heading or you can give it a heading and actually make it surface on the case view as well. Then you can justify that heading similar to what you can do with the details here, and then lastly we’re going to give it a size.

So everything in the new view the sizes are in fractions and that’s because the new view is responsive as well, so we don’t want to say it’s x number of pixels because then if you move between a big screen and a small screen and a mobile device it’s going to end up looking really strange with a lot of blank space or spilling over and having to scroll. So here you just set it out in rows that represent you know a kind of a full screen width or a couple of screens in length and then you set out a fraction so they space themselves according to the size of the screen, and if you’re on something really small like a mobile they’ll line up and down so that you can scroll through and it works better on a mobile. So for here we’re only doing two widgets on this line so we’ll make it a half. We’ll grab this one and just call it dates and financials and we’ll just grab a couple of dates here, allocated and completed is good enough for an example, labels on the left again, details we’ll leave as they are, and  we’ll call this dates and financials and give it a heading, make it half again. So that’s your basic field list widget that lets you pick data and just basically display the data as is with the label on the left and the value on the right.

Underneath that we’re going to show you a table which is useful for surfacing things like people, entities, and assets. We’ve got specific widgets for those as well where they will display a card with more detail on it, but this is a useful view for summarizing people attached to a case and things like that. So it depends on how you want to view that information as to whether you use this or the specific widget. So we’re going to drag a couple of details across here, this is a new thing where you can combine the last and first name – they’re separate fields in the database but we can join them and we’ll just call it last name-first name – and that’s just handy for display here. We’ll call this people and give it a heading and then the size, we’ve got one on that row so we’ll just make it a full width. 

So then we have a number of other widgets under here which I won’t go into now, but I do explain more in the full video that we’ve got, and so we’ve got a number of graphs that you can show on the case, you know useful things like radar charts good for QA, time series is good for budgets and things like that we’ve got a media viewer so for example if you’ve got a surveillance case you may want to surface photos or an accident case you may want to surface accident photos, cctv, things like that so you can surface that on the front of the case now rather than needing to go into doc preview, but for now that’s enough for our little intro.

So we will click away here and go back to this view and just refresh and you can see this data’s come up now, we’ve got half width for these here and we’ve got a table there and then we can go you can see that it’s pretty much what you see is what you get so we’ve laid it out like this and we’ve got a full width to half widths we can also move things around and so you can see that it’s a very easy drag and drop repositioning through some of those details that I showed you before. You can also change things like font size font color, things like that.

It’s very easy to reposition everything around here and it allows you to put anything where you want it, so it is a lot more powerful than the old case view and it’s a lot more configurable. The other important feature of this is that you can set a different one per case type so for example if you’re a private investigation firm and you have some factual cases and some surveillance cases you may want to put those photographs on a surveillance case but they might not be as important on a factual. So you don’t have to surface those on a factual, you can have more of those data fields where you fill out information that you found. So as I said, we have a longer video available if you want to know how to do this, for now it’s just telling you that it exists and that it’s pretty cool so I hope you like it and please get in touch – thanks.

Polonious Integrations – Our Journey – part 3

Where we are now, where we’re going

Our REST APIs have enabled us to develop these rapidly, securely and cost-effectively.

Here are a few, and what we did to expand flexibility, most are completed, some current projects:

 

Fraud Detection Capabilities

GBG Instinct

We wrote an adaptor to use their XML Web services capabilities, their team wrote to our REST APIs.

 FRISS

We are writing a Spring Boot adaptor to take JSON about a claim and all of its details and create a case with all relevant details using our own REST APIs.

 

Shift Technologies

We wrote a Spring Boot adaptor to take JSON about a referred claim and all of its details and create a case with all relevant details using our own REST APIs.

 

Taylor Fry

Two-way integration with Taylor Fry’s Fraud analytics platform.

Case Information sources

CarFax – Vehicle History

We wrote a Spring Boot adaptor between requests in Polonious for Vehicle history and CarFax’s internal API. This returns a detailed car history as a PDF, textual information or both and adds them straight onto the case with a simple button click in Polonious.

 

Social Discovery Corporation

We wrote code to interact with SDC’s team to begin a Social Discovery. The generated report is loaded back onto to the case once complete. User just clicks a button to request a Social Search for a Person on a case.

 

TransUnion

We wrote a Spring Boot adaptor to connect to TransUnion’s search capabilities. We have integrated some of the more popular searches with a long term goal of covering the full range. These are configurable in the case view interface.

 

Clear Data

We are currently working on this integration.

 

Carpe Data

We wrote an integration to return social ‘hit’s from a person’s core information.
 

Whooster

Public and Private Data Sources. Real-time Current and Historical. A proof of concept has been completed.
 

Truepic

Truepic is the leading photo and video verification platform.

Video Interviewing

SimpleToConnect

We wrote code to talk to S2C’s REST APIs which means in the user interface we can provide video interviewing capabilities easily.

Claims Systems

Guidewire ClaimsCenter

We used the new DevConnect to talk ‘REST’ to and from the Guidewire Claims Center system. On a Claim, service requests can create cases in Polonious, all or some updates on the case can be returned to the Claims team via the DevConnect REST calls. Even documents and images can be shared, all seamlessly from both tools.

 

Duck Creek

We’re currently working on this one.

   

Accounting Systems

QuickBooks

We integrate with Quickbooks REST APIs. This is now at the User Interface development point. Once complete, a more seamless creation of invoices and reconcilation interface will be available.

 

Xero

We wrote REST APIs that help us integrate with Xero. This will use the same UI as the Quickbooks integration.

Link Analysis

I2 Analyst’s Notebook

We added GET capabilities around entities that i2 might need including cases, persons, addresses, organisations, assets and other entities. This allowed the i2 partner to develop a plugin using i2 plugin design tools in .NET. This integration is owned by the i2 partner.

 

Maltego – Plugin

Polonious UK wrote a Maltego plugin that talks to Polonious given information like case numbers, persons and ‘expands the graph’ in Maltego using our REST APIs

Customer Integrations

Major Australian Bank

REST APIs to integrated with core services to facilitate case creation and updates from fraud analytics tools.

 

Major NZ Insurer

REST APIs to integrate with their reporting systems written in Power BI. Customer did everything with minimal need from us other than the API documentation.

Also a bespoke Guidewire integration using JMule written by their team to a v1 version of our create case REST api.

 

Major US Insurer

Integration with their Claims platform via REST calls. Minimal involvement with our IT resources.

 Sales ForceTotally written by the Chinese IT team at a client site. This allows their sales reps to trigger a Brand Fraud case in Polonious when using a sales force mobile app in the field.
 Sumo LogicCurrently work in progress to deliver case outcomes back to sumo logic from triggered case.

Internal Polonious Integrations

AWS Amazon Cloud Automation

We wrote a comprehensive integration set that used our own REST calls to send and receive updates from automation of EC2/S3/VPC/RDS/IAM instance set up triggered from actions taken on cases in Polonious. Bizzare use-case but shows the capability well.

 

Twilio

Text Messaging integration

 

Google Authenticator

Mulit-factor Authentication Integration (work in progress)

  

 

Flexible Integration both ways – inbound and outbound

One of the core strengths of our case management system is that is is very flexible and adaptable to differing business needs. This is a great thing for our customers but a bit of a pain for the development team internally when adding features.

Every development sprint we do has to be predicated by the fact that we need to cover bases for all our customer needs now, and into the future.

Our REST APIs reflect this, and our future road map for them will take this a step further.

This final section is more for your IT teams to understand our approach and how it helps their efforts to integrate with our solution.

Create Case flexibility

Create Case is our most used API, it’s the gateway to initiating action inside Polonious for some trigger like Fraud detection or a referral from Claims.

This API has its own web interface to enable pretty much anything to be used as data to create a case.  The interface allows a user to configure a mapping of inbound fields by uploading an example JSON. This JSON needs to be  ‘flat’. ie the data has to be a single level of attributes. This actually covers off on 95% of our integration needs with the backup of additional REST services for the more complex cases where, for example, variable numbers of participants are involved.

Outbound REST Call flexibility

Our Polonious customers are now very familiar with the ability of Polonious to automate outbound integration tasks.

To achieve this, we often use a key transaction point in our application, the Case Note (or action, diary, update as some of our customers call it).

This means, you may want this integration to only happen at case inception, or at case review or case update, or possibly only at case close stages. Possibly at all of the above. Our Polonious Persons can configure this for you. No Polonious IT resources are usually needed.

How this works is fairly straight forward. For any type of case note, you can setup a REST call that can locate, collate and send any case data from that case (I mean any case data, including other diary entries, person, vehicle, company data from the case, any metrics gathered on the case either singular or as totals).

Our Polonious Configurers understand how to access the deep case data and can share many examples of how to use it with your team. The technique is pretty easy to use if you’ve used a templating/programming language before. This generally needs no input from our internal IT team reducing costs and speeding the process.

For complex integrations we use an adaptor

In many of the more complex needs, systems talk different protocols and need ‘cleansing’, selection or verification of data on the way to their penultimate system. To do this, we use microservice adaptors. These can be written by our teams at Polonious or your own IT teams. They can be written in any language your team is comfortable with. We have customers who have created these adaptors in languages other than Java such as python, c# and used them to

talk to/from all sorts of different protocols like webservices, sftp,and the like.

The end point for this payload can be another system you’ve designed that talks any of the major security protocols or it can be an ‘adaptor’ web server written in any language (we prefer Java but some customers use node.js, .net, python and others. That adaptor can then forward the data (possibly after adapting it) to your internal applications in a way they understand.

Using an adaptor provides the additional benefit that the integration source code can be maintained separately from the core systems at either end. This makes updating and writing automated tests for it far easier. It also makes it much easier to understand to a new developer which improves maintainability and change cost. Due to the versioned APIs we use, this adaptor will not require regular updates to keep up with API changes.

Finally, an adaptor is just that – it can adapt more easily to internal security changes and other needs. We can easily send you more information (just by changing the payload with a quick call to our Polonious Persons. The rest is easy (excuse the pun), just a small change to the adaptor, re-run any tests, and you’ve updated your security or business requirements. You can change underlying systems with reduced pressures of dependencies as those dependencies are easy to maintain separately from the core systems.

If you are a Polonious client, we have a number of great examples we can share with you of this from our Spring Boot collection. This makes it really easy to stand up a new adaptor as and when needed.

The future

I hope this series has been interesting, it’s a good reflection of how we handle integration needs quickly and securely for on-boarding and existing customers. These are the takeaways that I hope you have seen demonstrated:

  • Customer and product Integrations have improved markedly in the last 10 years in both speed and cost.
  • Polonious have developed a great API-first approach to ensure most of your needs ready to be served.
  • Most integration work at Polonious is done by the business-facing configuration teams, this saves time and money.
  • The list of Polonious integrations is comprehensive and growing rapidly.

We are expecting a number of changes in the future to our current processes to make them easier to use, more robust, more secure. Currently we’re working on Spring Cloud services and integration technologies. We expect more flexible, scalable, secure and highly resilient services to come from this work.

Additionally, as the Insurtech space evolves, as more and more providers of case information come forward with great offerings, we intend to approach and integrate with all new information vendors as they arrive. To list a few we’d love to integrate with: NICB, Claims data providers, ebay, listings and other information providers.

Every piece of information an investigations team might want to access should be available at minimal effort to the team involved. No special interfaces, seamless integration available as simple button clicks is the way of future. Information sources that require special re-typing exercises will likely suffer in this changing landscape.

The future of case-related information at speed is looking great, we hope you enjoy the journey as much as we are.

SIU Insights report 2021How do you compare to other SIUs?

Check out some interesting results from our SIU management survey. Submit below form to receive the download link and related updates going forward.

GICOP changes 2021Download the GICOP whitepaper and stay compliant.

Our whitepaper covers all aspects you need to know to stay compliant with the latest GICOP changes coming into effect in 2021. Submit below form to receive the download link and related updates going forward.