Design partners

How a Pilot Works

A pilot replays your closed tickets offline. It needs no access to your live systems and no change to your workflow, and you see where the agent was right and where it was wrong.

Step 01

A 30 minute call

We agree on the scope and on how your data is handled. We can sign an NDA or a data processing agreement first.

Step 02

A small sample

You send two or three closed tickets with their data, in the formats you already have. We confirm that we can read them.

Step 03

The replay

You send 50 to 100 closed tickets. The agent diagnoses each one using only what your engineers could see when the ticket was opened. It never sees your resolution.

Step 04

The results call

For each ticket you see the agent's diagnosis next to your engineers' resolution, where it would have avoided a technician visit, and where it was wrong.

What we ask for

Try to include a mix of causes, and tickets where a technician visit didn't fix the problem.

Start with ten tickets

If 50 to 100 tickets is too much for now, start with ten. Choose difficult ones, or ones where a visit didn't fix the problem. Ten are enough to show whether the full pilot is worth it.

Your data

You anonymize the data before it leaves your network. Names, vessels and identifiers are replaced with consistent pseudonyms, and the technical values stay as they are. We use the data only for the pilot and delete it afterwards. The agent only reads. It never connects to your network, your terminals or your NMS.

Ready to try it?

Write to us and we'll send the full data request, with the file formats and the anonymization details.