Who approves
Set by your agency. Loss runs are often reviewed before they go out.
Workflows / Loss runs
Loss runs
Loss run requests tracked from the ask to the document arriving, with the chase clock running while you wait on the carrier.
- 01Recognize and match
- 02Route and time it
- 03Mark what you are waiting on
- 04Chase on schedule
- 05File and send on
What arrivesNew request
A customer or underwriter asking for loss runs, or a loss run arriving from a carrier by email.
Routed, timed and tracked until it is done
[ Step by step ]
How Shlix handles loss runs.
The same order every time, recorded on the task as it runs. Anything unclear stops for a person instead of being guessed.
- From the request
- From your AMS
- Done and on record
Recognize and match
The request, the customer and the policies it covers.
Route and time it
To the right person, with a longer due time than a certificate, since carriers take days.
Mark what you are waiting on
Usually the carrier. The clock pauses while you wait and a follow-up is scheduled.
Chase on schedule
A follow-up every three business days by default; after the agreed chases the task is raised to the owner.
File and send on
When the document arrives it is kept on the task, a person checks it, and it goes to the requester.
[ Control ]
Who signs off, and what stays on record.
What is recorded
Each request, chase, document received and who sent it on, with times.
Requesting loss runs from carrier portals automatically is not available. Your team makes the request; Shlix keeps the schedule.
Does Shlix summarize the loss run?+
No. It keeps the document with the task and times the work. Reading and summarizing it stays with your team.
[ Read next ]
[ Other workflows ]