Automated Applied Epic Claims Status Updates
Every Monday, WebRun opens Applied Epic, reads each open claim's status, adjuster, and last activity date, drafts a plain-language status update in Outlook for the client, left unsent for your team to review and send, and logs which updates went out to a Google Sheet.
How do I keep clients updated on their open claims?
Every Monday, WebRun opens Applied Epic and reads each open claim's status, adjuster, and last activity date. It drafts a plain-language update per client in Outlook, left unsent for your team to review and send, and logs which claims were updated to a Google Sheet, so no client is left wondering what happened to their claim.
- Clients hear about their open claim every week, not only at renewal
- Each update reflects the latest adjuster activity in Applied Epic
- No client gets updated twice or misses a week
Built for commercial insurance brokerages · claims handlers · account managers · agency service 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 - read open claim status
appliedsystems.com
WebRun reads open claim status in Applied Epic. - Open Applied Epic and pull the claims tab for every open claim across clients
- Capture each claim's status, adjuster, carrier, and last activity date
- Skip any claim already updated to the client this week
Done when Every open claim has been captured with its status and last activity date.
-
2
Outlook - draft the client update
microsoft.com
WebRun drafts a client claim status update in Outlook. - Draft a plain-language status update for each client with an open claim
- Explain what has happened since the last update and what comes next
- Save it as a draft and leave it unsent for your team to review and send
Done when Each open claim has a client update drafted and unsent in Outlook.
-
3
Google Sheets - log what was sent
google.com
WebRun logs which claim updates were drafted and sent. - Log which claims got a drafted update and which are still pending review
- Note the claim number, adjuster, and date of the draft
- Keep a running record so no client goes without an update two weeks running
Done when Every drafted update is logged so none is missed next week.
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 send claim updates to clients without review?
No. WebRun drafts each update in Outlook and leaves it unsent. Your team checks the details against the adjuster's latest notes before sending, nothing reaches a client automatically.
Will it contact the carrier or adjuster on its own?
No. It only reads claim status already logged in Applied Epic. Calling the adjuster, negotiating, or updating the claim record stays with your team.
How does it avoid updating a client twice in one week?
It checks the Google Sheets log before drafting, so a claim already updated this week is skipped until the next run.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.