Why Runink? Library
Industries
Logistics & Supply Chain Insurance Banking & Financial Services Telecom Marketing
Pricing Company
Book your Consultation
Appearance
English English Français Français Español Español Português Português

Runink FACE: Fulfilment Autonomous Claims Engine

Every overcharge, claim and stale order, drafted for one approval.

FACE reads the invoices, orders, carrier records and claim files you already keep. It finds what you are owed and what broke, and drafts the next step. A named person approves it.

Send one month of invoices See prices

Runs on your servers, your cloud account or Runink's shared machines. No outside AI service.

Drawn example of a drafted claim. The names and records are illustrative.

Your operation already wrote down what went wrong.

Today

  • A disputed invoice takes most of a morning, so only the big ones get done.
  • A small claim costs more to build than it returns, so it expires.
  • Scanned pages and spreadsheets are typed into another system by hand.
  • The same report is rebuilt every Monday from the same exports.

With Runink FACE

  • Every invoice is read against the records behind it and your rates.
  • Each claim file is assembled and drafted while the window is open.
  • Spreadsheets are read with their formulas, and scanned pages are transcribed.
  • A question set up once runs on your schedule, with a record of what it read.

What it takes off the desk

  • Catch it

    Overcharges nobody challenges

    Every invoice read against the receipt, the weight and your rates, and the dispute assembled with each record.

    Freight audit · Finance

  • File it

    Claims that run out of time

    The claim, the policy, the reserve and the records gathered, and the action drafted inside the window.

    Claims desk

  • Stop retyping

    Paperwork typed in twice

    Spreadsheets read with their formulas. Scanned pages transcribed on FACE's own machines, and an unusable page says so.

    Operations

  • Schedule it

    The Monday report, rebuilt by hand

    Set the question up once. It runs when you choose and keeps a record of what it read.

    Analysts

  • Check it

    Carrier checks in a spreadsheet

    Web research run from FACE's own machines, with the pages it read attached to the finding.

    Procurement · Compliance

  • Re-run it

    The consultant hired twice

    Forecasts and what-if studies run again on your own records, with the method stated.

    Planning

Inside FACE: Ask, Options, Why, Actionable Twins

One menu down the left of the screen, in the order you use it. Ask a question and get the answer first, see what you could do about it on Options, see why on Why, and approve the action on Actionable Twins.

Ask and Briefs

Ask in plain words. The answer comes first.

Ask a question, or start from a suggested one. You choose which sources it reads, and the answer leads, with the records behind it a click away.

  • Sources Databases, business software, logistics systems, files, web pages and live feeds from trackers, RFID tags and sensors, added once in Settings and picked per question.
  • Briefs Set a question up once and it runs when you choose, or when your data changes, for the person it is for. A brief reads all your sources unless you pick some.

Options and Why

What you could do, and why FACE thinks so.

Nothing here changes your systems. Options lists what you could do about the answer, side by side; Why shows the rules and documents it rests on.

  • Options The what-ifs built from your run: a lane a week late, a supplier dropped, a different reserve, each with the reasoning you can argue with.
  • Why The rules you already work to, written down once, checked against every record and held up against the policy documents that are their source.

Actionable Twins

The decisions waiting on you, and where they are.

A twin is a live copy of something real, such as a site, an asset or an order, kept current from your own records. Each one that needs a decision becomes a card.

  • Lanes What is waiting for you, what is in flight and what came back. A person approves or rejects each card.
  • Map The same twins at their real locations, routes in the proposed stop order, and live layers from anything that reports a position.
  • Follow-ups Chasing a supplier or carrier by text or voice about a decision, opened from the same page.

The drafted action waits. Approving is what sends it.

Every section ends in the same place: one proposed action, with the rule and the records attached, in front of a named person.

  • Why it fired, on which records Open any finding and read the rule, the records under it and the reasoning that joined them.
  • The reply says what ran After approval, the reply names which parts ran. A step that could not run is named, with its reason.
  • Could not check is an answer Where a check could not run, the result says unable to assess. It never reads as compliant.
  • The decision stays with a person FACE assembles a claims or underwriting file and drafts the action. An adjuster decides, on the file in front of them.

It runs on your machines

For many freight and claims teams, customer files, customs papers and claim records cannot go to somebody else's servers. FACE is built for that.

  • Your servers or your cloud On the Dedicated and Enterprise licences, the work runs on machines you control. Lite runs on Runink’s shared machines.
  • No outside AI service The language model runs where FACE runs. On every licence, nothing is sent to an outside model provider.
  • Open-web research with no account attached When web research is on, FACE searches from its own machines through a public search page and reads the pages itself.
  • A record of every decision Who approved, when and what they changed is kept with each action, ready when an auditor asks.

Trust and compliance

Start with one month of invoices

The fastest way to know if this fits is your own records. We put no figure on this page; your month will show you yours.

  1. You send one month Freight invoices or claims, and the rate sheet they should match.
  2. We read it in FACE Every invoice against its rate and its records. Nothing goes to an outside AI service.
  3. We walk it with you Half an hour with whoever owns the problem: what was found, the drafted actions and their causes.
Send one month of invoices

Questions

The product

Is FACE the same thing as Runink PULSE?

No. They are separate products, each sold on its own. FACE is for freight, fulfilment, claims and the compliance work around them. PULSE is for marketing teams.

Does FACE decide, or do we?

You do. FACE drafts an action with the rule and the records attached, and a named person approves or rejects it.

Do we have to replace our WMS, ERP or claims system?

No. FACE reads from the systems you already run, such as SAP, Dynamics 365, Salesforce, HubSpot, ServiceNow, Guidewire, SharePoint, your spreadsheets and your file storage. It is not a system of record.

Your data

Can we run it on our own servers, with no outside AI service?

Yes. On the Dedicated and Enterprise licences FACE runs on your own servers or in your own cloud account. Lite runs on Runink’s shared machines. On every licence, nothing goes to an outside model provider.

What happens when it cannot check something?

It says so. The result is unable to assess, and the wording makes clear that this is not a finding that the thing is compliant.

Buying

Is there anything we can put in someone's hands today?

Yes. An Android build of FACE, with the actions waiting on a decision and the approve or reject, is on the downloads page.

What does it cost?

You pay per person who uses it. Prices, including the success fee on recovered claims, are on the pricing page.

runink.org