Protrix is a product of Sesto Group B.V.Sign in
Protrix
Book a demoTalk to sales
Platform

One mission, from request to invoice.

Protrix is organised around the mission, not around modules. Everything below happens to the same record, so the field, the customer and the finance side are never reconciling three versions of the same job.

Stage 01
Request
Stage 02
Plan & dispatch
Stage 03
Execute & track
Stage 04
Approve & invoice
01Request

The job arrives structured, not as a phone call.

Customers submit escort requests directly: route, vehicle, cargo profile, schedule and contact on site. Recurring corridors come in as a saved route code with its agreed price already attached.

INTAKE
Route with pickup, waypoints and delivery; date, time window and expected duration; vehicle and trailer; cargo sensitivity.
ROUTES
Saved corridors carry their agreed pricing and standing requirements, re-triggered from the route code in seconds.
QUOTE
Operator prices the request; the quote generates a PDF and waits on customer approval before anything is dispatched.
Request intake & saved routes
02Plan & dispatch

Own detail or subcontractor, decided on one board.

Approved missions go to the dispatch board. Assign guards, vehicles and trailers from your own registers, or offer the leg out to a vetted subcontractor who accepts and staffs it themselves.

FLEET
Guards, vehicles, trailers and drivers held per organisation, with availability visible at the moment of assignment.
OFFER
Dispatch to a subcontractor organisation; they accept, assign their own detail, and report into the same mission record.
BRIEF
The assigned detail receives the mission on their phone with route, stops, contacts and standing instructions.
Dispatch board
03Execute & track

The field reports itself. The control room sees it happen.

Guards run the mission natively from the app; every status change, stop, photo and alarm lands on the mission timeline and the live map at the same moment. Nobody phones in an update.

Live map, mission in progress
Guard app
Guard using a phone beside an escort vehicle at a stop

Mission timeline

Every event in order, with actor, time and position, the record you produce when a claim or a query arrives weeks later.

Command center

Incidents and alarms triaged in one screen, each already carrying its mission, detail and last known position.

Messaging, auto-translated

Threads scoped to the mission, translated inline, so language is not a reason an instruction was missed.

04Approve & invoice

Completion, sign-off and billing on the same record.

A finished mission gets a digital sign-off. The accepted quote becomes an itemised invoice per leg, and the subcontractor payout is calculated against the same lines. No re-entry, no month-end reconstruction.

SIGN-OFF
Digital completion confirmation against the mission, with the timeline attached as evidence.
INVOICE
Itemised per leg, with escort hours, waiting time, additional vehicles and the agreed corridor rate.
PAYOUT
Subcontractor amounts derived from the legs they actually ran, visible to both sides.
Invoice breakdown
05Surfaces & languages
Surface 01

Operator console

Dispatch, live map, command center, fleet, quotes and invoicing.

Surface 02

Guard mobile app

Mission execution, status, GPS, evidence, stop logs, panic.

Surface 03

Customer portal

Request submission, quote approval, own-transport visibility, sign-off.

Surface 04

Subcontractor portal

Offered work, acceptance, own detail assignment, payouts per leg.

Eight languages in the product UI

Each party works in their own language, including the guard on the roadside and the customer approving a quote.

ENNLDEFRESITPLCS

Walk one of your own missions through it.

Bring a real corridor and a real invoice dispute. That is the fastest way to see whether this fits how you operate.

Book a demoSolutions by role