Origami Risk · Integration layer (API, SFTP or custom)

Automate assignment routing with Origami Risk and VIP

When a new claim or exposure needs a field inspection, appraisal or other vendor work, the assignment is often created by hand from the claims system and sent by email or phone, so start times vary and the claim record does not show who has the work. Carriers running Origami Risk (claims & risk management) often handle assignment routing outside the claim system, which means exporting claim details, vendor assignments and invoice and expense data by hand and reconciling it later.

How VIP solves it

A new or updated claim in the connected system starts the assignment workflow in VIP, and assignment status is kept against the claim so everyone works from the same record. Origami Risk connects through VIP's integration layer (API, SFTP or custom). A carrier on Origami Risk would send claim details and vendor assignments into VIP and receive invoice and expense data back; the exact method and field mapping are scoped with your team.

What moves between Origami Risk and VIP

Outcomes

Request this integration

Origami Risk connects through VIP's integration layer (API, SFTP or custom). Tell us about your Origami Risk setup and we'll scope the connection for assignment routing.

Questions and answers

How does Origami Risk work with VIP for assignment routing?

Origami Risk connects through VIP's integration layer (API, SFTP or custom). The exact connection is scoped with your team.

What data moves between Origami Risk and VIP?

Claim details; Vendor assignments; Invoice and expense data.

Who is assignment routing with Origami Risk for?

Assignment routing is built for carrier teams using Origami Risk, at the claims operations stage of the claim.

Origami Risk integrationAssignment routing workflow

More Origami Risk workflows