Add-ons: switch on only what you use

The core platform works out of the box. Add-ons are enabled per company and turned off when you no longer need them — with no effect on anyone else’s data and no hidden items.

Request a trial Pricing

What you can switch on

Each add-on solves one job. You enable it only if you actually use it.

Scheduled rides

The passenger picks the departure time, the system creates the schedule and sends a reminder. The console shows every future ride.

Passenger wallet

Balance, top-up and paying for a ride from the wallet. The company sees every entry and can refund an amount.

Coupons and promotions

Codes with a discount or a fixed amount, with an expiry and a limit. The discount is applied when the ride ends.

Corporate accounts

Companies pay for their people’s rides; each has its own account, rules and report.

PBX telephony

Phone orders enter the same queue as app orders; the ride shows who called and how long the call lasted.

Back-to-back rides

The driver accepts the next ride while the passenger is still in the car, with the waiting limit you set.

API access

REST API, keys with scopes and signed webhooks for your systems.

App store launch help

We guide you through publishing the apps in the App Store and Google Play, under your own accounts.

How they are enabled

We enable an add-on per company, on request or through the console. Billing follows the contract, and the console always shows what is on.

What is always included

The passenger and driver apps, the company console, dispatch, prices, zones, settlement, invoices and reports work without any add-on.

What add-ons do not do

An add-on does not change who is responsible or change your data. A disabled add-on simply stops being available; returning to the previous state is agreed in the contract.

FAQ

Do add-ons need a separate contract?

Billing and activation are agreed in the contract; the console shows what is currently on.

Can I turn an add-on off later?

Yes. We agree activation and deactivation, and the terms are part of the contract.

Is the wallet the same as card payment?

No. A card is a way to pay for a ride; the wallet is the passenger’s balance with you.

Does PBX work with every phone system?

Telephony connects through the PBX webhook; we check the specific system before enabling it.

Can the API be used without the add-on?

No. The public ride-tracking routes work, but the business API needs addon.api_access.

How do I know what is enabled?

In the company console, on the modules overview. It shows what is core and what is an add-on.

Get a demo

See it with your own numbers

Half an hour, your zones and your prices. We open a company and show you this part of the system — from the order to the invoice.

Request a trial Pricing

Tell us what you need — we show the add-on on your own data.

info@driveos.eu