Automated Applied Epic Loss Run Follow Up
Every Monday, WebRun opens Applied Epic, finds policies renewing soon that are missing current loss runs, drafts a follow up request to the carrier or MGA in Outlook, left unsent for your team to review and send, and tracks each request's status in a Google Sheet.
How do I follow up on loss run requests before a renewal?
Every Monday, WebRun opens Applied Epic and finds policies renewing soon that are missing a current loss run, then drafts a follow up request to the carrier or MGA in Outlook, left unsent for your team to review and send. It tracks every request from sent to received in a Google Sheet, so a missing loss run never quietly holds up a renewal.
- Missing loss runs surface a full renewal cycle out, not the week before
- Every request is tracked from sent to received
- No renewal gets marketed to carriers without current loss history
Built for commercial insurance brokerages · producers · account managers · renewal marketing teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.appliedsystems.comin a real browser with your saved login - no setup, no API keys. -
1
Applied Epic - find renewals missing loss runs
WebRun checks upcoming renewals in Applied Epic for a current loss run. - Open Applied Epic and filter renewals inside your marketing window
- Check each policy's attachments for loss runs current within the last 90 days
- Flag any renewal with no current loss run on file
Done when Every renewal missing a current loss run has been flagged.
-
2
Outlook - draft the carrier request
WebRun drafts a loss run follow up request in Outlook. - Draft a follow up request to the carrier or MGA for each missing loss run
- Reference the policy number and the period needed
- Save it as a draft and leave it unsent for your team to review and send
Done when Each missing loss run has a follow up request drafted and unsent in Outlook.
-
3
Google Sheets - track requested and received
WebRun tracks each loss run request from requested to received. - Log each loss run request with the carrier, policy, and date requested
- Mark it received once a current loss run is attached in Applied Epic
- Keep a running tracker so nothing stays outstanding into the renewal
Done when Every loss run request is tracked from requested to received.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email carriers or MGAs on its own?
No. WebRun drafts the loss run request in Outlook and leaves it unsent. Your team reviews and sends it, nothing goes out to a carrier automatically.
How does it know a loss run is missing?
It checks each renewing policy's attachments in Applied Epic for a loss run dated within the last 90 days, and flags any renewal without one.
How does it know a loss run has been received?
It checks Applied Epic each run for a newly attached, current loss run, and marks the tracker received automatically once it finds one.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.