Request a demo

After Sales

Service for machines and equipment

Whoever is on the job works with the experience of your best people

Ask the way you'd ask a senior colleague. The answer comes from the manual or from a ticket already solved

Ticket#4821
MachinePX-40 press
TechnicianNew hire, 8 months

"Press is down, the display shows E-217. The customer has a batch shipping tomorrow."

Received via WhatsApp · photo of the display attached

Code recognized from the photo. Found 3 similar service jobs already solved on this model.

E-217 means pressure out of range on circuit B. In similar cases the cause was connector X14 on sensor SP-2, check that before recalibrating

Sources PX-40 manual ·ch. 7 ·p. 112 Ticket #3310 ·solved
  • Machine made safe, circuit B depressurized
  • Connector X14: corroded → cleaned and tightened
  • Pressure at rest: 182 bar (range 175–190)
  • Full test cycle

Generated service report Downtime due to E-217. Cause: corroded connector X14 on sensor SP-2. Cleaned and tightened, pressure verified at 182 bar, test cycle passed. Duration 48 min.

Approve and close Once your expert has reviewed it, the solution is available to the team
Illustrative scenario, with a made-up machine, codes and documents. Not a technical procedure to follow.

The problem

Your company's knowledge is already there, but it's scattered

It's in manuals, tickets, chats and the heads of a few people. First we bring it into one verified knowledge base: your golden dataset

  1. Experts get interrupted by the same questions

    Hours on the phone, while the hard cases wait

    −50% of experts' time spent helping colleagues

  2. New hires depend on their colleagues

    When the information can't be found, it's trial and error

    −80% of new hires' time spent finding information

  3. Experience walks out the door with people

    When someone retires, years of solutions go with them

    10 min to prepare up to 1,000 closed tickets for your expert's approval, instead of 10 days

Data and feedback collected from our AI-Know After Sales customers. In the pilot, we measure them on your own work

How it works

Four steps, from the call to the service report

It helps you at every stage of the service job

  1. The ticket comes in

    From the app, email or WhatsApp, already linked to the machine and the customer

  2. It guides the diagnosis

    The technician types, talks or sends a photo. The answer suggests the steps, with the source

  3. It supports the job

    It suggests the checklist for that machine and that problem

  4. It drafts the service report

    It gathers what was done and asks for what's missing. The technician approves

Want to see it on one of your own service problems? Request a demo

The answer changes with the experience of whoever asks

Two lines for the expert, step by step for someone just starting

Technician's question

"Error E-217 on the PX-40, where do I start?"

Let's start with safety, then isolate the most likely cause.

  1. Stop the machine and depressurize circuit B. So you can work on the sensor with no residual pressure.
  2. Locate sensor SP-2, on the hydraulic unit, operator side. I'll show you the diagram of the unit.
  3. Check whether connector X14 is corroded or loose. That was the cause in the 3 similar cases on this model.
  4. Only if the connector is fine, move on to calibration.
PX-40 manual ·ch. 7 ·pp. 108–⁠112

Illustrative example, with a made-up machine and codes

How it learns

A service job solved today helps the whole team tomorrow

Only once your expert says yes. AI‑Know doesn't learn on its own

  1. The technician closes the ticket and approves the service report

  2. AI-Know removes private data and rewrites it clearly

  3. Your expert corrects it, approves it or rejects it

    Approval
  4. The knowledge base keeps it tracked and easy to update

  5. The whole team and your partners find it with the source and the latest version

What it doesn't do, in plain words

  • It doesn't search the internet for answers
    It uses your company's knowledge, with the source
  • It doesn't decide for the technician
    It suggests the steps. Whoever is on the job decides
  • It doesn't replace safety procedures
    It takes you to the right place in the manual

For service managers

You always know where the answer comes from

  1. Where does this answer come from?

    Every answer shows the source: manual, page or ticket. The technician checks it before starting the job

  2. Who checked it?

    The technician checks the service report, your expert checks new solutions. Nothing gets in without approval

  3. Is it the latest version?

    Yes. Every solution is tracked and everyone sees the latest version

One answer, with its full trail

  1. AnswerCheck connector X14 on sensor SP-2
  2. SourcePX-40 manual · ch. 7 · p. 112
  3. Approved byThe technical manager, after 3 similar service jobs
  4. VersionThe most recent, updated after the last service job

Illustrative example, with a made-up machine and codes

Frequently asked questions

If yours isn't here, bring it to the demo

What if we don't have service software?

AI-Know can handle that too. Tickets, service jobs, checklists, scheduling and the equipment map are part of the platform.

What does the service manager see?

First, the service dashboards: open tickets, response times promised to customers, workloads and average times by technician, area or type of problem. Then the map of your customers' equipment, showing problems and service jobs in progress. In scheduling, the AI suggests which service jobs to combine in the same trip and which route to take, but the scheduler decides.

Do we have to change our software?

No. Your ERP, CRM and ticketing system stay where they are. AI-Know reads what's already there (manuals, tickets, chats, training videos, meeting minutes, service history) and brings the answers to where your technicians work: app, web, WhatsApp and email. They can also ask by voice or with a photo.

What if the AI gets it wrong?

Every answer shows the source, so the technician can check it before starting the job. The technician approves the service report, your expert approves new solutions. Nothing gets into the knowledge base without approval.

How long does it take to get started?

Setup takes a few days, enough time to connect your software and load your manuals and service history. If you'd rather start with a measured trial, the pilot project runs 6–8 weeks (to be confirmed).

Where does our data end up? Our IT team will ask.

We cover it right away, in the demo. We show you where the data is stored, who can see it and how your software is connected. If your IT team already has a list of questions, bring it and we'll answer your IT team directly.

How does the subscription work?

There are regular users, for people who use it every day, and occasional users, for people who use it now and then.

See a full service job, from ticket to service report

Bring a real problem: we'll show you how it handles it

Request a demo Demo and pilot: how to get started →
  • 20 minutes
  • No confidential documents needed
  • Then you decide whether to go further