Skip to content

Operator Introduction

How the service sits inside destination operations: ownership, daily workflow, exceptions and reporting.

Written for
Centre management and operations teams
Reading time
5 min
Access
Open

Daily operating rhythm

The intended rhythm is exception-led. Rather than checking the estate, the operations team works from a short list: docks approaching capacity, areas short of units, units flagged for service.

Most days require no intervention beyond that list. The platform exists to make the exceptions visible early enough to act on them calmly.

Ownership

Every deployment agrees who owns redistribution, cleaning, first-line service and escalation. There is no fixed split — a destination with an established facilities team will divide this differently to one buying a fully managed service.

Reporting

Reporting is aggregate: sessions, utilisation, dock pressure by location and time, and service events. It is designed to answer operational questions, not to profile shoppers.

Next step

See it against your floor plan.

A demo puts the fleet, dock network and console in the context of your own destination.