Transfeero automation glossary
Plain-English definitions of the terms behind ride automation and fleet operations on Transfeero.
Ride automation
Software that monitors a ride platform's feed and accepts matching rides automatically, so a driver or operator doesn't have to watch and tap manually. On Transfeero, this means catching the offers that match your rules the instant they appear.
Auto-acceptance
The act of a bot accepting (claiming) a ride on your behalf when it passes your filters. Good auto-acceptance is rules-based — it only takes rides worth your time, not every offer.
Transfeero fleet manager
A person or system responsible for accepting and dispatching rides across one or more Transfeero partner accounts for a transfer company. Fleet-automation software replaces the manual monitoring a fleet manager would otherwise do by hand.
Catch rate
The share of matching rides a driver or bot actually wins out of those it tried to accept. A higher catch rate means fewer good rides lost to faster drivers — largely a function of reaction speed and how reliably sessions stay connected.
€/km (price per km)
A ride's payout divided by its distance in kilometres — the core profitability metric for transfer work. Setting a minimum €/km floor filters out long, low-paying jobs. Try the free €/km calculator to find your break-even.
Session management
Keeping a driver's authenticated login to the platform alive over time. For automation, reliable session management — staying connected 24/7 and reconnecting automatically — is what actually determines whether the bot keeps catching rides, especially across multiple accounts.
Golden (event) filter
A priority filter for special-event surges — a big match or concert — that takes precedence over your normal rules and can run even during your usual days off, so you capture peak demand.
Turnaround gap
The minimum time you need between two rides for the same vehicle (to finish one job and reach the next). Automation respects this gap so the same car is never double-booked back-to-back.
Multi-account isolation
Running several platform accounts so that each has its own sealed session, rules, and logs, with no shared state and no cross-account access — the safe way to automate a fleet rather than a single login.