× Midas Analytics
01 / 18
SATISLOH × Midas Analytics
Service Optimization · Two Use Cases

Give your service team
its time back.

Two focused AI tools, built from what Brice raised. One answers the repetitive questions that flood in after every install. The other makes sure no existing customer is ever forgotten — so follow-ups happen and upsell moments don't slip.

2 use cases web-based · no SAP integration built for Brice's team 01 Jul 2026
Michele De Filippo
Prepared by Michele De Filippo, PhD
AI Lead · Midas Analytics
What we heard from Brice

Two things quietly eat your team's time.

Your team already carries every install and every support call — that part works. From our conversation, Brice — the main user of both tools — pointed to two repetitive drains on that strong operation:

After every install, the questions pour in.
Customers ask the same basic things about how the machine works. The volume is the problem — repetitive questions pull skilled people off the work that actually needs them.
Between sales, follow-ups slip.
Some customers reach out for support or new kits. Others go silent — often a sign the machine is under-used. Either way, regular check-ins get overlooked, and upsell moments pass by.
This is my understanding — correct me where I'm wrong.
What these two tools are for

Free your team from the repetitive — and make sure no customer is forgotten.

Neither tool replaces your people. Each one takes the low-value, easy-to-drop work off their plate — so the skilled hands are free for the complex, high-value cases where they matter most.

At a glance

Two tools. Two problems. Both web-based.

Use Case 01

Customer AI Servicing

After install, customers get a link to a chatbot that answers their questions — reading only that machine's manual. It handles the basic, repetitive ones for you.
Removes the flood of repetitive inbound questions
Use Case 02

Bi-Weekly Customer Report

Brice uploads a SAP export into a web app that builds a full status & delta report — what changed since last time — on every existing customer, and turns it into clear action points for the next meeting.
Removes the risk of a dropped follow-up
Use Case 01 · Customer AI Servicing for FAQs
01

An AI that answers the manual, so your team doesn't have to.

The problem
After installations, customers repeatedly ask basic questions about how their machine works. The sheer volume is time-consuming, and most answers are already in the manual.
The idea
A servicing chatbot the customer reaches by URL. It reads the manual for the exact machine or part they bought — and answers the bulk of inquiries, especially the basic, repetitive ones.
How it works · step through it

From "just installed" to "already answered."

01
Private link
02
Pick the machine
03
Ask in plain language
04
Answered from the manual
05
Your team, for what's left
Step 1 / 5
Private link
The moment a machine is installed, the customer receives a private link to their servicing assistant — no login to hunt for, no portal to learn.
See it working

The customer asks. The manual answers.

servicing.satisloh.com · your machine
Machine or part: Lens generator AR coating machine Edger / polisher Coating consumables kit
The AR coater is showing error E-204 after the last cycle. What does it mean, and how do I clear it?
press → for the answer
Servicing AI · reading the AR coating machine manual
Illustrative example — the error code, section and steps shown are fictional placeholders. In the real tool the AI answers only from your actual machine manual, and hands over to a human when it should.
Why this works

Accurate because it's narrow.

Scoped to one manual
The AI only ever sees the manual for the machine the customer selected. No mixing across products — answers stay accurate and on-product.
Handles the bulk of inquiries
Especially the basic, repetitive ones — the exact volume that was eating your team's time.
Available any hour, any time zone
Customers get an answer the moment they're stuck — no waiting for your working hours.
Clean hand-off to a human
When something is genuinely complex, it escalates — so your team spends its time only on the cases that need them.
Use Case 02 · Bi-Weekly Report for Existing Customers
02

A standing report that makes sure nothing slips.

The problem
Regular follow-ups with existing customers get overlooked. Some reach out for kits or support; others go silent — a worrying sign of under-use. Upsell opportunities pass unnoticed.
The idea
A web app Brice feeds with a SAP export. It generates a full customer status report on a bi-weekly cadence, turning raw data into clear action points for each customer.
How it works · step through it

One spreadsheet in. A meeting-ready report out.

01
Export from SAP
02
Upload it
03
Time-stamped
04
Status + delta report
05
Clear action points
Step 1 / 5
Export from SAP
Brice pulls the customer data he already has in SAP as a simple spreadsheet — no integration to build, no IT project to wait on.
See it working

Every customer, one screen, one clear next step.

customer-report · Midas web app
Customer status & delta report Data uploaded · 01 Jul 2026, 09:14 · vs. report of 17 Jun
Customers tracked
48
Need follow-up
12
Gone quiet
5
Upsell signals
7
CustomerKitSince last contactvs. last reportStatusSuggested action
Meyer OptikAdvanced3 days— steadyActiveOn track — no action needed
Optique RhôneBasic34 days▼ orders slowingQuietCheck-in call — consumables reorder likely due
Helvetia LensPreventive61 days▼ no orders this periodAt-riskSilent 9 weeks — book a machine health check
Nova VisionAdvanced12 days▲ usage upActiveUpsell: coating add-on to the advanced kit
Vista OtticaBasic48 days▼ quiet since installAt-riskUnder-use signal — offer onboarding refresher
Illustrative example · fictional customers & data — your real SAP export lands here, refreshed on every upload.
Why this works

The value is consistency.

Nothing is forgotten
Every customer gets a clear next step, every cycle. Follow-ups stop depending on who remembers what.
Silence gets caught early
A customer who's gone quiet is flagged before under-use becomes a lost account — the delta report makes the drop-off visible.
Every check-in is a sales opening
Consistent follow-ups surface reorders and kit upgrades — better service turns directly into more opportunities.
A ready-made meeting agenda
The action points from one report become the starting point for the next — the review runs itself.
Trust & security

Your data stays yours.

Both tools touch sensitive material — your manuals and your customer data. They're built so that data is protected by design and never leaves your control.

You upload — we never reach into SAP
The report app takes a file you export and upload. No live connection into your systems, nothing written back.
Encrypted & access-scoped
Encrypted in transit and at rest, in a region you approve, with access limited to two named Midas people.
NDA first, your policy throughout
An NDA before any data reaches us — aligned to your own infosec policy at kickoff.
Midas is ISO 27001-certified
ISO/IEC 27001:2022 · view PDF
The build plan

Day 56: both tools live — the repetitive handled, and no customer forgotten.

Workstream
W0W1W2W3W4W5W6W7W8
Week 0 · scoping & prep
Scope
UC#1 · Index the manuals
Ingest & scope per machine
UC#1 · Chat app, test & launch
Chat + selector → launch
UC#2 · Upload + data model
Upload flow + map SAP fields
UC#2 · Status + delta report, launch
Status & delta → action points → launch
~Week 6 — UC#1 servicing chatbot live ~Week 8 — UC#2 bi-weekly report live
What we'll need from you, to start

A short list to get moving.

An NDA
We need to understand your service operation properly in order to help — the NDA lets us in.
The machine & part manuals
For the chatbot — the more manuals you share, the wider the coverage. We start with a few and grow.
A sample SAP export
One real (or anonymised) extract, so the report is shaped around the data you actually have.
A few hours of Brice & the team
To walk us through how you work today — so both tools fit you, not the reverse.
What you're investing in

One build. Two working tools.

~8-week fixed-fee build
A fixed fee
for both tools, confirmed on our call.
Scoped as one build — the servicing chatbot and the bi-weekly report app, delivered and launched.
Servicing chatbot (UC#1)included
Bi-weekly report app (UC#2)included
Hosting & runscoped separately

Ongoing hosting, support and any later expansion are scoped once the build is agreed — not pre-committed here.

What's included
  • A customer servicing chatbot, scoped per machine manual, reached by private link
  • A bi-weekly report web app — upload, status & delta report, action points
  • Both launched with your real inputs — manuals and a live SAP export
  • Testing against real questions your team has already answered
  • Built on secure, access-scoped infrastructure in a region you approve

You own the tools and the data they hold; terms are set in the SOW.

Get started

Three steps to kickoff.

Step 01

Green light

A short call to walk through this plan and shape the scope of both tools together.

Step 02

NDA & agreement

We circulate the NDA and a simple statement of work. You sign — about a week.

Step 03

Kickoff & Week 0

You hand over the manuals and a sample export — and the build starts.

Thank you.

Free your team from the repetitive — and make sure no customer is ever forgotten.

midasanalytics.ai
←→ navigate · space reveal