Skip to content

Faster service

Remote service for machine builders. Know the fault before anyone travels.

A fault, a limit crossed, a value out of its normal range: whatever rule fires on a customer's machine, their operator or machine head gets it on WhatsApp, in your name. Your service team sees every alarm on the alarm dashboard: what happened, when, and how often, with your remedy beside it.

Book a free visit Follow one alarm

In the example below, MX-200 #07 was running again in 6 minutes, and nobody travelled.

One alarm, start to finish

From alarm to running in six minutes.

  1. 14:32

    The alarm

    MX-200 #07 at Sunrise Manufacturing raises Alarm 280, air pressure low, and stops. Flowtics Edge catches it at the machine in under a second.

  2. 14:32

    Everyone who needs it hears

    The operator and the machine head on site get a WhatsApp alert from your service number. Your service engineer gets it too, because you assigned them to this customer. Your MD isn't disturbed.

  3. 14:34

    The screen

    Your engineer opens the alarm: the shift, the last 15 minutes of data and the remedy your own team wrote for Alarm 280.

  4. 14:38

    Fixed by phone

    The operator calls. Your engineer already knows the fault and walks them through it. Running again in 6 minutes, and nobody travelled.

Who hears what

The right person, on the channel they read.

Your admin sets, for each person, which alarms and which channel. Your customer's admin does the same for their own team.

PersonReceivesChannel
Customer's operator or machine headAlarms and rules on their own machines: faults, limits, values out of range. Set by their own adminWhatsApp App
Service engineerAlarms on the customers you assign them toWhatsApp
Service headCritical alarms, and anything not acknowledged in 15 minWhatsApp SMS
Spares teamMaintenance due, by running hoursEmail
MDA daily summary of the whole installed baseEmail
  • Sent in your name.Alerts go out from your WhatsApp Business number and your email, so your customer sees your company, not ours.
  • Nothing gets missed.If an alarm isn't acknowledged in time, it goes up to the next person.

If nobody answers

  1. 0 minOperator or machine headWhatsApp, the moment the alarm or rule fires. Your engineer too, if assigned
  2. 15 minService headNot acknowledged? It goes up, by WhatsApp and SMS
  3. Next dayMDA daily summary of the whole installed base, by email

Diagnose from your desk

Everything your engineer needs, on one screen.

Every alarm from every customer lands on your alarm dashboard. Open any one and your engineer sees what the machine saw: no "what does the display say?" phone calls.

Alarm detail · MX-200 #07
  • 01Live data around the momentThe readings around the alarm, from 1 minute to 1 hour, on a chart.
  • 02The alarm historyHow often it has happened on this machine, and on every machine of this model.
  • 03Your team's remedyThe fix your best engineer wrote for this alarm, step by step.
  • 04One tap to callThe call list for this machine: operator, maintenance, your service head.
  • 05Change a setting, with permissionWhere write-back is switched on for your role, adjust a setpoint from your desk. Every command is logged.

Remedies

Your best engineer, on every call.

Your team writes the fix for each alarm once, per machine model. Every engineer and every operator sees it the moment that alarm fires, and it gets better every time someone improves it.

  • Written once

    Per alarm, per machine model. Every machine of that model gets it.

  • Seen by everyone

    Your engineers, and the customer’s operators, in the app and on the alarm screen.

  • Better every time

    When someone finds a better fix, they update it, and the next call is shorter.

Remedy

Flowtics AI analyst

Ask why. About one machine, or all of them.

Ask in plain language, in any language. The answer comes from your own machine data, with numbers and a recommendation. It reads and recommends; it never controls the machine.

For your service team
Why did MX-200 #07 lose 40 minutes on Tuesday?
From your machine data41 minutes of downtime, all in shift B. Three stops on Alarm 280 · air pressure low make up 27 minutes, and one job change took 14.
Alarm 28027 min
Job change14 min
Recommendation: check the air regulator at station 2 before the next shift.
For your design team
Which alarms keep coming back on the MX-500, across all customers?
From your machine dataMain drive temperature high is the top repeat alarm, at 6 customers, mostly in the afternoon when the shop floor is hottest.
Drive temp41× · 6 sites
Hyd. oil28× · 4 sites
Air press.12× · 3 sites
Recommendation: review the drive cabinet fan rating, for service visits now and for the next design revision.

Sample questions and answers. Your machine data is never used to train AI models.

Book a free visit

See what your own machines can already tell you.

Half a day at your works and an honest written answer. No cost, no obligation.

Book the free visit Request pricing

What happens on the visit

  1. 01
    We come to your works

    Half a day. We look at two or three of your machines and their PLCs.

  2. 02
    We check what Flowtics can read

    Which readings, alarms and counters it can pick up, and what they would show you.

  3. 03
    You get a written report

    With your own numbers. Then you decide: stop there, or start a pilot.

  • No cost
  • No obligation
  • No technical preparation