Custom workflow automation for personal injury firms: match incoming records to matters, update the request log and check what is still outstanding.
See the workflow
You have the signed authorization, but the records still haven’t arrived. Your team checks the request log, calls the provider again and updates the case file. Multiply that by the providers on every open matter.
What belongs to one job
Here’s how the proposed workflow could fit together. These are process illustrations, not finished software or real client records.
Match incoming emails and records to the matter, provider and authorization your team has checked. Keep the source documents linked to the request.
Records matched to the matter
Original documents stay linked
Compare received files with the requested date range and document list. Flag unclear matches or missing pages for your team; prepare a follow-up only where something is outstanding.
Received records checked
Only outstanding items need follow-up
Enter the agreed status and link the received documents in your existing case system through a connection we assess during setup. Verify the update; your team confirms completeness before closing the request.
Case system updated
Your team confirms completeness
Your firm approves every outgoing message and decides whether an authorization is valid and a response is complete. This pilot does not provide legal or medical advice, assess injuries or submit filings.
Show us an anonymised example of a recurring job and the tools your team uses. On the audit call, we choose one workflow with a clear start and finish.
We build the agreed workflow around your WhatsApp, email, Slack and business systems: bringing in information, checking it and updating the right records. We agree scope, price and access in writing first.
We run through cases with your team and check the result in the destination system. Unclear cases go to a person. Your team approves every outgoing message before it is sent.
Runnrr is new. We’re looking for firms willing to test one real workflow with us and tell us what works and what needs to change.
80% off
Pay 20% of the normal price for the agreed pilot scope. Your written quote shows both prices, what is included and any third-party costs. We agree the scope and timing with you.
Read the pilot agreement outlineFor firms handling sensitive client records, we also offer workflows with local AI inference. We assess the model, hardware and access needed to run the AI processing on your own machine or server.
We test the setup with your workflow and agree where data is processed before connecting live records. Your WhatsApp, email and business systems still have their own storage and processing arrangements.
Talk to Dmitrijs about local processingYour agreed sources
Messages and documents you allow the workflow to use
AI processing on your hardware
A model selected and tested for the task
Work completed in your tools
Agreed access, approvals and result checks
Dmitrijs Vitjazevs · Founder of Runnrr
I’ve been helping companies move their work forward with digital products for more than ten years. After Corgee, I worked with Eneba and Easygenerator on new products and process automation. At Easygenerator, that included helping companies such as PepsiCo and Danone.
Earlier in my career, I worked as a paralegal at Shearman & Sterling. That experience informs how I approach document-heavy work. Runnrr does not provide legal advice; your firm keeps professional judgment and approval.
Now I help small and medium-sized businesses automate work in the tools they already use. We start with a small scope, written data terms and results your team can check. The companies above are part of my previous experience, not Runnrr customer references.
We can scope local AI inference for the agreed workflow. We assess the model and hardware, then test the setup before using live data. Connected services such as WhatsApp, email and your business systems keep their own processing and storage arrangements; we document those separately. This is a custom setup assessed for your firm, not a standard feature included with every pilot.
That depends on the tools and workflow we agree. Before connecting live data, we document the systems, hosting locations, providers, retention and deletion arrangements in your pilot’s data terms. We do not promise that all processing stays on your device or in one country.
We agree the named people and service providers who need access before setup. Access is limited to the agreed workflow. Start the conversation with an anonymised example; do not send client records through the enquiry form.
We agree which system changes need approval and how incomplete work or exceptions return to your team. Your team reviews and approves every outgoing message. Those controls are defined before we connect live data.
The founding-client pilot costs 20% of the normal price for the same agreed scope. Your written quote shows both prices, what is included and any third-party costs. There is no published fixed fee or standard duration; further work needs a separate agreement.
No. Runnrr is new. These are workflows we propose to configure and test with founding clients, not a catalogue of ready-made industry integrations. We assess the workflow and your tools before agreeing what to build.
Only after your firm has assessed the workflow and the written data arrangements. We agree access permissions, providers and any confidentiality or data-processing terms before using live records. Your firm checks the requirements that apply to its practice and location; this page is not a compliance certification or a guarantee of legal privilege.
runnrr
WhatsApp