Skip to content

Our Clients · Transport operators

Run more service with the fleet you already have

Operators across Europe run Shotl to turn fixed routes into flexible ones — fewer empty kilometres, better contract KPIs, and riders who come back.

Book a demoSimulate your first service
A passenger with her phone waits as a Moventis Sarbus minibus pulls up, the driver visible behind the windscreen

Who does what

Your drivers, your contract, our platform

How the work splits when an operator runs the service.

Service name and brandYouYour client’s service name and trademarks, or your own.ShotlWhite-label app themed per deployment: landing page, logo and colours. One app per OS for all your zones.
Rider accountsYouYour client’s identity provider, so their riders’ accounts work.ShotlIntegrates sign-in with it; registration fields set to what you need.
Vehicles and driversYouYour fleet and your drivers.ShotlReads drivers, vehicles, stops and zones from your systems instead of keeping a second copy.
Onboard hardwareYouThe units already on your vehicles: CAN-bus or another OBU.ShotlSoftware ready to integrate with them. Shotl does not supply the hardware.
Network dataYouThe GTFS feed your client runs.ShotlCompatible with both, so the service sits inside your wider network.
Data and reportingYouReporting to the authority that contracted you.ShotlActivity data with full detail, plus a query API with KPIs and real-time vehicle positions.

How it works

What an operator deployment looks like

Every case on this page runs the same platform. A typical operator starts with a simulation on its own contract data, launches one zone, and tunes from the KPIs.

  1. 1 · Before launchFree simulation

    Simulate the zone on your own contract data, size the fleet and put numbers in front of the authority.

    • Draw the area, drop the stops, tell us the fleet
    • A micro-simulation built on the figures you give us
    • Graphs, KPIs, a fleet figure and a cost quote — walked through in a one-hour call
    Get a free simulation
  2. 2 · In serviceDemand responsive

    The end-to-end service: booking by app or phone, pooled routes, live operations.

    • Riders book by app, web or phone — an operator can book on their behalf
    • Ride now or schedule ahead, with a wheelchair field that follows the request
    • Vehicles tracked in real time for riders and the control room
    See demand-responsive transport
  3. 3 · Every quarterData and analytics

    Punctuality, pooling rate, kilometres and cost per trip — the KPIs your contract is measured on, live.

    • Activity data delivered with full analytical detail and mileage
    • A query API exposing service KPIs, bookings and real-time vehicle positions
    • Compatible with GTFS data, so it sits inside the network
    See data and analytics

Built to win a tender

What the authority’s evaluators check first

The requirements that come up in every public tender you bid for, and how the platform answers them.

RFP and technical resources
  • Your name on the serviceRun it under your own service name and trademarks, with your logo, colours and landing page.
  • One app for every zoneOne app per operating system covering all the zones you integrate, showing only your service.
  • Existing accounts sign inRider login through your own identity provider, with registration fields set to what you need.
  • In your riders’ languagesFully configurable per language — Salento was delivered in Italian and English.
  • Inside your networkCompatible with GTFS data, so it sits alongside your other lines.
  • Your data, on requestActivity data delivered with full detail, plus a query API with KPIs and real-time vehicle positions.
  • Hardware you already fitIntegrates with CAN-bus or another onboard unit. Shotl does not supply the hardware itself.
  • Screen-reader readyThe rider app works with VoiceOver on iOS and TalkBack on Android.
We chose Shotl because of the fact that they already had running operations in several cities in Europe. And we thought there would be learning from their operations, like the case in Barcelona, where the operation environment seemed very close to where we see transportation problems.
— Masashi Hisatomi, Executive Officer, Odakyu

See what flexible transport would change in your area

FAQ

Questions operators ask

How do we start?

With a free first simulation. Sketch the service area, drop the stops and tell us the passengers and the fleet. We simulate it and walk you through a document with graphs, KPIs and a cost quote in a one-hour call — no commitment attached.

Can the service run under our own name?

Yes. A white-label licence lets you run it under your own service name and trademarks. The app’s landing page, logo and colours are set per deployment, and one app per operating system covers every zone you integrate.

How do riders book?

By app, on the web, or by phone — a call-centre operator can book on the rider’s behalf, which keeps the service open to people who don’t use digital tools. Trips can be booked to ride now or scheduled ahead.

Can riders change or cancel a trip?

Yes, within the policies set for the service. The rules are configurable per deployment rather than fixed by the platform.

Does it work with our existing network?

It is compatible with GTFS data, so the service can sit alongside the rest of the network. Rider sign-in can also run through your own identity provider.

What data do we get?

Activity data with full analytical detail and mileage, plus a query API exposing service status, bookings, KPIs and real-time vehicle positions for your own systems.

Do we need to buy hardware?

No new hardware is required from Shotl. The software integrates with onboard units you already fit, such as CAN-bus or another OBU — Shotl does not supply the hardware itself.

Proof

Related case studies

All case studies

Win the next tender with proof, not promises

We'll walk you through operator deployments like yours — fleet size, service area and contract model included.

Book a demoSee all case studies