Case study · Operations platform · In production

MedFlow: one system for cases, providers and money.

A medical assistance company ran its operation across mailboxes and spreadsheets. We built the platform it now runs on — where the AI reads every incoming email and PDF, turns a request into a case, pulls the numbers off a hospital invoice and drafts the reply, and a person approves each step before anything goes out.

Open it live

One patient, start to finish

The guided story: a patient with chest pain in Phuket, from the first e-mail to the guarantee of payment. Names and figures changed for client privacy.

How we made it

From the first conversation to the running product.

A medical assistance company ran its operation across mailboxes and spreadsheets. We built the platform it now runs on — where the AI reads every incoming email and PDF, turns a request into a case, pulls the numbers off a hospital invoice and drafts the reply, and a person approves each step before anything goes out.

Case study · Operations platform · In production

We sat with the people doing the work and wrote down how it runs today, and where it hurts.

Illustration drawn from the finished screen, so you can see the stages the project went through.

Try it here

Click through the same case yourself

The real screens, one step at a time — use the arrows or swipe. No sign-in.

1 of 20

Every mailbox, sorted by subject

Mail is grouped by what it is about — new cases, existing cases, providers, finance — not by the address it reached.

Swipe, or use the arrows — on the screen or on your keyboard

Want the real thing?

The problem

The truth was spread across inboxes.

Requests for help arrive by email from insurers and partners around the clock. Each one becomes a case with providers, guarantees of payment, invoices and payments in several currencies — and every step used to depend on someone remembering to copy it somewhere.

Read the whole story

The platform reads the mail, proposes the case, tracks every guarantee and invoice, and keeps finance honest. Language models are optional and only ever draft: every message that leaves is approved by a person, with a mandatory copy and signature.

Type
Operations platform
Status
In production
Stack
PHP · SQLite · in-house IMAP/SMTP
Hosting
Shared hosting, by design

What we built

From one e-mail to a guaranteed hospital visit

Pick one to see it

The e-mail

The e-mail arrives, already sorted

An insurer writes about a client with chest pain in Phuket. MedFlow files it as a new case request and says why — no one reads the whole inbox to find it.

Try the approval flow

The model prepares. A person approves.

We automate the conversations and paperwork that eat your team’s day: WhatsApp and customer service, inboxes, replies, payments and documents. Routine answers go out on their own, inside rules you set; money, promises and exceptions wait for a person, with the source of every suggestion on screen. Try it:

Shared mailbox · 5 newNames and figures are illustrative

  1. claims@northsea-insure.exampleNew case: Mr R. Olsen, Phuket — policy NS-55120
  2. billing@cityhospital.exampleInvoice INV-20417 (PDF attached)
  3. ops@alpine-assist.exampleAny update on MFA-002380?
  4. news@medtravel-weekly.exampleThis week in travel health
  5. j.weber@lakeside-clinic.exampleIntroduction

Sorted, with the reason for eachWaiting for a person

  • New case: Mr R. Olsen, Phuket — policy NS-55120New case request95%↳ Names a patient, a place and a policy numberCase proposal prepared
  • Invoice INV-20417 (PDF attached)Provider invoice97%↳ Known provider, PDF with an invoice numberQueued for invoice reading
  • Any update on MFA-002380?Status question93%↳ Quotes an open case referenceReply drafted — see “Draft a reply”
  • This week in travel healthNewsletter99%↳ Bulk sender with an unsubscribe headerArchived
  • Introduction52%↳ No case, no invoice, sender not on fileLeft for a person
Fill in the gaps to continue

The showroom

A showroom that cannot leak

The showroom runs the production code with a thin layer on top. Each visitor gets their own database copied from a clean template, outbound connections are refused by default, and sending files the message in a Sent folder instead of reaching anyone.

Read the whole story

We can open a live session for your team on request.

See it running on your own cases.

We will walk your team through it, then shape it around how your operation works.

Start a project

Add your company and what you need (optional)
What do you need?