Follow up with the insurer and update the file
The latest insurer response and next action saved with the claim, with reminders stopped when answered.
Talk to salesWhat starts the work
A claim is awaiting an insurer response or a new status message arrives.
- Claim reference
- Latest insurer correspondence
- Approved follow-up schedule
Work in your tools
Read the current claim status before following up
Prepare the insurer enquiry with the correct reference
Match the response to the claim
Save the verified update and next response owner
| What your team does today | What comes back |
|---|---|
| Check an inbox, find the claim reference, chase the insurer and manually update the broker system. | The latest insurer response and next action saved with the claim, with reminders stopped when answered. |
Built around the tools you use
Agree how you will measure the result
Compare staff handling time, completed requests and exceptions before and after setup. The written scope defines which requests count and what a completed result means.
Calculated from your inputs. Include review and exception handling. Validate the target during your pilot.

Start with one recurring job. We agree the result, connect your tools and test the workflow with your team.
Questions before you start
Which software can this use?
Runnrr checks your exact software, version, permissions and available actions before agreeing the workflow. Connections, data access, retention and approval rules are confirmed and tested during setup.
What counts as completed work?
The latest insurer response and next action saved with the claim, with reminders stopped when answered.
What needs a person?
Your broker handles disputes, settlement advice and decisions about coverage.
What happens when something fails?
An ambiguous reply, disputed deadline or unsuccessful save stays open for review.
Does this require the Mac app?
The Runnrr Mac app requires macOS 14 or later and checks connected sources while it is running. A managed workflow is scoped separately: required software, hosting and operating hours are agreed and tested before live use.
What does setup and operation cost?
US$299 covers one-time setup for one agreed workflow. Ongoing operation and support are quoted separately, along with any call, messaging, AI or other provider charges. Runnrr confirms recurring costs and usage limits in writing before you commit. If the workflow is not running within two weeks or does not deliver the result agreed in writing, Runnrr refunds the US$299 setup fee.
Who handles ongoing support?
Dmitrijs Vitjazevs is your contact for setup and workflow questions at dv@runnrr.io. The written quote sets out ongoing maintenance, support hours, response arrangements and how to end the service. Your team names the person who handles exceptions and professional decisions.
Work your team can hand over
Follow up with the insurer and update the file
The latest insurer response and next action saved with the claim, with reminders stopped when answered.
Talk to sales
