Module

Booking platform

Every request, whether typed by a rider or taken by a coordinator, becomes the same trip. Rules for zones, eligibility and notice periods live here.

ISO 27001 ISO 9001 ISO 14001 TISAX Level 2 ISO/IEC 27017 ISO/IEC 27018
Call-centre headset, laptop map and smartphone connected to a van
ISO 27001 operations
White-label passenger and driver apps
Live assignment and pooling
European software vendor
Overview

How the platform is used

Booking is where published policy becomes a trip. If the website, the app and the phone desk create different records, dispatch spends the morning reconciling them.

maas.maker uses one trip object. A coordinator can complete a booking for someone who never installs an app. A rider can still self-serve. Cut-off times, walking distance to a virtual stop and eligibility flags are configuration, not custom code for every service.

Payments, concessions and third-party wallets are integration topics. The booking module records the fare rule; it does not invent a local fare act.

Booking platform

Every request, whether typed by a rider or taken by a coordinator, becomes the same trip. Rules for zones, eligibility and notice periods live here.

Same trip, any channel

Web, app and telephone bookings share identifiers, so a change on one channel updates the others.

Service rules

Notice periods, booking horizons and geographic fences are set per service product.

Call-centre headset, laptop map and smartphone connected to a van

Confirmations

Riders receive a window, not a silent acceptance. Changes generate a new notice.

On-behalf booking

Call-centre and social-care staff can book without impersonating a consumer account badly.

Call-centre headset, laptop map and smartphone connected to a van
Operations

How the platform is used

Booking is where published policy becomes a trip. If the website, the app and the phone desk create different records, dispatch spends the morning reconciling them.

maas.maker uses one trip object. A coordinator can complete a booking for someone who never installs an app. A rider can still self-serve. Cut-off times, walking distance to a virtual stop and eligibility flags are configuration, not custom code for every service.

Request a demo
Implementation

How a tenant goes live

Scope

We walk through service type, fleet, booking channels and the reports you already have to file.

Configure

Branding, stops, hours, vehicle classes and assignment rules land in one tenant.

Train

Dispatchers, drivers and coordinators practise on the live board before opening hours.

Go live

The first operating weeks are coached. Exceptions, not the happy path, are the real product.

What you actually buy

Modules you can combine. One tenant.

Start with booking, dispatch and the driver app. Add passenger apps, pooling rules, feeds and exports when the service needs them.

Explore the modules
See the platform in a working demo

A configured walkthrough, not a marketing video only. We look at your service type and fleet.

Questions teams ask

White-label software for booking, dispatching and reporting demand-responsive transport. It is not a consumer ride-hail brand.

No. Customers run the service with their own fleet or contracted carriers.

USD is the list-price base. You can switch the calculator to Australian dollars, New Zealand dollars or euro. Final contract currency is confirmed in a proposal.

Yes. Book a conversation and we walk through a configured tenant for your service type.

Contact

Plan a working demo

Share fleet size, service type and the outcome you need. We reply with a working demo path, not a generic brochure.

+43 50 556

maasmaker@anexia.com

Monday to Friday, 09:00–17:00 CET

Request a demo