If you're working with IAG on insurance repairs, you'll want to have an Opus integration with your Crunchwork platform. The Opus integration pulls in any allocated claims that your company receives, and periodically updates between Crunchwork and Opus to maintain the most current status. Read on more to learn about how to manage the integration.
For you to get started with Opus and Crunchwork, you must:
Create a new user that can be shared exclusively with Codafication. This user will login to Opus and perform actions as part of the integration, using RPA. We can use existing credentials for the integration if the client wants, however creating a new user is a suggestion to help distinguish between actions completed by a real user, compared to the integration.
An email address which should receive integration notifications.
Common Interactions with Opus
Here's just a few common interactions between Crunchwork and OPUS that help provide value to you:
Pulling jobs from OPUS directly into a core job management system
Automating customer contact flows based on OPUS-events
Query for impending breaches of KPIs
Uploading/downloading file attachments
KPIs Automation:
Set builder reference (AR)
Initial contact time (AR)
Site attend date (AR)
Status updates (CR)
Estimated end date (CR)
What happens when I get a new claim in Opus?
Crunchwork creates a new project with the below information. Most of this information will be added to to Pulse in grey text that can't be adjusted in the Project information panel at the top of the page.
Project type: IAG
Start date
Date of loss
Policyholder name and contact information - this record is also created as a new "contact" within Crunchwork.
Policy number
Building policy inception
Claim number
Claim type- this is known in Opus as "Incident Type"
Building policy value
Job Syncing to Opus
We sync the job types “IAG Make Safe; IAG Assessment; IAG Completion and IAG Tender” into Opus. The job field configuration on these jobs must not be changed, as they are required to sync back to Opus successfully.
It is an Opus requirement that all the fields must be populated within the job before submission can be made.
Opus doesn’t create separate Make Safe jobs the way we do (or the way any other insurer does); they have a “Make Safe” section included within their Assessment allocation. This syncs to the fields within the Assessment job under ‘Emergency Repairs’ and ‘Make Safe Scope of Work’.
Assessment Jobs
There is a task titled “Submit to insurer” that controls the submission of the Pulse job fields back to the relating job type in Opus.
This means that the user needs to ensure that all fields on the assessment job are satisfactory, such as “Assessment attendance date”, etc , and then complete the task. The “Submit to Insurer” task triggers after the “Book Assessor” task is completed.
You must login to Opus to complete the invoicing.
Completion Jobs
Users must utilize the “Status/progress” and “repair dates” components on their IAG Completion jobs to send timestamped updates on sending repair documents like the scope of works to the customer, or waiting on excess payment or maintenance by the customer.
Updating the Pulse job status does not connect to Opus.
Users will need to refer to the document syncing section below for sending to Opus the PDF copies of variation quotes and excess invoices to Opus.
Document Syncing to Opus
The Scope of Works PDF, Quote PDF and Builders Assessment PDF publish to Opus once the report/quote is published in Crunchwork within the relevant app. For example, Builders Assessment Reports are submitted to Opus once the user clicks “Publish” in Report Writer. These are not attached to any tasks or workflows.
The below document uploads occur after the user clicks “Publish” - these are part of our Opus integration.
OPUS Document Type | Crunchwork Record Type |
REPAIRER_S_REPORT | Builders Assessment (Report Writer) |
QUOTE | Quote PDF (Quote Tool) |
SCOPE_OF_WORKS | Scope of Works PDF (Quote Tool) |
Other documents, eg Specialist Reports.
For other documents, the user must externally attach to Crunchwork (i.e. a roof report from a trade), when first attaching the document to Crunchwork, you select “Publish Externally = Yes”.
If a document is already attached to Crunchwork, and ‘Publish Externally = No” was initially selected, you cannot edit the document and change it to “Publish Externally = Yes”. You have to re-attach the document, choosing ‘Publish Externally = Yes” when doing so.
Differences between Opus and Pulse
There are some small differences in the language used between Crunchwork and Opus. Here's a quick guide:
Claim types and their codes
OPUS | Crunchwork |
CA | Earthquake and Tsunami |
CO | Impact |
DA | Accidental Damage |
FE | Fire |
FL | Flood |
FS | Explosion |
GL | Other |
HB | Other |
LR | Other |
OT | Other |
ST | Storm - Wind |
TH | Theft or Burglary |
Documents
The only automated documents we have at the moment related to automations are
OPUS | Crunchwork |
REPAIRER_S_REPORT | ABC Assessment (Report Writer) |
QUOTE | Quote PDF (Quote Tool) |
SCOPE_OF_WORKS | Scope of Works PDF (Quote Tool) |
For a user to sync a document back into Opus, they must use the “Publish externally” checkbox found when editing attachments against a Pulse job.
For the attachments to be found here, the user must first “Publish” the document. Upon publishing, Crunchwork will copy the PDF from the file and place it back in the attachments.
Works Job Status Mapping in Crunchwork:
Opus:
Crunchwork:
Think we missed anything? Let us know by sending a message to support@codafication.com
For the full web site, click here.