All-in-one SaaS for ground transport operators. Manage bookings, dispatch rides, track your fleet, settle finances, and grow revenue across OTA demand, partner demand, and operator-to-operator farm-out recovery.
199 $
Starting price/mo
5+
Revenue channels
24h
Go-live time
Operator Dashboard
Everything you need to manage your fleet
Don't rely on a single booking source. youtourer connects your fleet to direct customers, OTAs, and travel partners.
Customers book via your branded widget or the youtourer marketplace. You receive 100% of bookings from your own channels.
Connected OTAs (Booking.com, GetTransfer, etc.) send booking requests. You accept or auto-confirm based on your availability.
Hotels, agencies, and corporate clients create bookings through the partner portal. You fulfil and earn the operator share.
When capacity falls short, the platform orchestrates handoff to another operator — preserving the passenger promise without silent failure.
Receive overflow rides from other operators when their capacity is stretched. Accept via competitive bidding or standing offer. This is not a booking channel — it is a supply-side recovery mechanism.
The UI should make ownership and handoffs explicit. Operators run the fleet. The platform brokers demand, recovery, and trust across organizations.
Your widget, repeat customers, hotel desk calls, and manual bookings land in your operating queue first. youtourer runs the ops stack without stealing the ownership model.
Instant and planned rides are different operating products. Premium UX makes the expectation, timing, and escalation window explicit before the booking is accepted.
For airport arrivals, hotel departures, and urgent same-day rides where speed matters more than a long planning window.
Premium operator UX should never hide ownership, fulfillment responsibility, or recovery. These are the four flows every stakeholder must understand at a glance.
A hotel desk call, repeat guest, or branded widget booking lands in the operator queue first. The platform supplies workflow and controls, but the operator keeps the commercial promise.
Demand owner
Operator
Commercial owner
Operator brand and pricing promise
Dispatch owner
Operator operations team
Fulfillment owner
Operator fleet
Operator readiness board
A supply-side decision surface should make ownership, settlement, dispatch, and recovery explicit for every operator role before go-live.
Protect channel mix, margin, and booking promise without forcing teams into separate direct vs platform workflows.
Primary surface
Pricing, channel mix, commercial truth
Guardrail
The platform can broker demand, but commercial responsibility and pricing guardrails must remain explicit.
Must-watch signals
Every tool you need to run a transfer business — from a single booking to a 100-vehicle fleet.
Register vehicles by class, track inspection dates and insurance expiry. Assign drivers to vehicles. Dashboard shows real-time fleet status — available, on-ride, or offline.
Rides are dispatched to the best-match driver automatically — by location, vehicle class, rating, and availability. Manual assignment is always available as a fallback.
Set base fares by corridor, apply surge rules for peak demand, and configure zone-based pricing. The platform calculates the fare — you set the rules.
No setup fees. Free trial available on all plans. Scale up or down at any time.
Perfect for small fleets getting started
Up to 20 vehicles · 10 team members
Most operators are accepting bookings within 24 hours of signing up.
Create your operator account at admin.youtourer.com. Enter your company details, tax ID, and bank information for settlements.
Takes ~15 minutesRegister your vehicles by class. Onboard drivers with license, SRC, and background check documents. Set availability schedules.
Within 24 hoursSet base fares for your corridors, configure surge rules, and define zone pricing. The platform guides you through setup.
Guided setup wizardAccept your first booking. Auto-dispatch sends ride offers to your available drivers. Our operations team monitors your first week.
Active operator demand in these regions. More cities launching quarterly.
AYT ↔ Belek, Side, Alanya, Kemer, Kaleici
Very High demandIST ↔ Taksim, SAW ↔ Kadikoy, Sultanahmet
Very High demandADB ↔ Alsancak, Cesme, Kusadasi
High demandStarter plan has no setup fees. You can start with a lean fleet, scale as demand grows, and upgrade or downgrade at any time. All plans include the driver app, booking management, and settlement system.
Auto-dispatch is available and recommended — it matches rides to the best driver based on location, vehicle class, and rating. But you can always manually assign rides to specific drivers from the dashboard.
Settlements are calculated weekly. The platform automatically splits each fare into commission buckets (platform, driver, partner, OTA) based on the booking channel. You see a full breakdown in your dashboard and funds are transferred to your bank account.
Yes. Growth and Enterprise plans include full API access with 150+ endpoints. You can integrate bookings, fleet data, and financials with your existing back-office systems via REST API and webhooks.
We provide a video onboarding session for your drivers covering the app, ride flow, verification codes, and customer service standards. Your operations team also gets a separate admin training for the supplier portal.
Yes. Your operator account works across all youtourer-supported cities. Register vehicles per city, set corridor-specific pricing, and manage everything from a single dashboard.
Free Trial
Set up your workspace in 60 seconds. No credit card required.
Create your workspace
Set up your organization profile, invite your team, and configure your fleet — all in minutes.
Go live on the platform
Accept bookings via widget embed, direct portal entry, or partner API from day one.
Scale with intelligence
Cortex AI automatically optimizes dispatch, pricing, and settlement as your volume grows.
Already have an account? Sign in
Ride Now, partner, OTA, and marketplace demand is brokered by youtourer. The platform picks the best-fit operator while the chosen operator still controls L2 driver assignment.
When the first operator cannot fulfill, the system should recover without collapsing the passenger journey. Recovery is a visible operating mode, not hidden back-office chaos.
Platform principle
youtourer orchestrates demand, trust, and recovery. The operator still fulfills the ride with its own fleet standards, dispatch choices, and local operating judgment.
For fixed pickup times, return legs, executive travel, and planned hospitality flows where certainty and coordination matter more than immediacy.
Passenger promise
The guest should feel they booked with the operator directly, even when platform workflow and recovery controls are active in the background.
UI must make this explicit
Show that pricing rules, dispatch choice, and passenger commitment remain under operator control.
Recovery rule
If capacity tightens, recover inside the fleet first, then escalate to platform-guided farm-out intentionally.
youtourer sources the demand, selects the best-fit operator, and keeps the booking promise consistent. The chosen operator still executes with its own fleet and dispatcher surface.
Demand owner
youtourer platform
Commercial owner
youtourer booking promise
Dispatch owner
youtourer for operator selection, operator for L2 dispatch
Fulfillment owner
Selected operator fleet
Passenger promise
The rider should see one confident booking promise while the assigned operator still feels native inside its own fleet workflow.
UI must make this explicit
A planned pickup or return leg needs earlier certainty, better notes, and visible lead time. This is not just a slower Ride Now flow.
Demand owner
Channel-specific demand source
Commercial owner
Channel-specific commercial promise
Dispatch owner
Scheduled operator planning before live dispatch
Fulfillment owner
Scheduled operator fleet
Passenger promise
The passenger should understand that timing, notes, and return coordination are locked in earlier than a live Ride Now flow.
UI must make this explicit
When the original fleet cannot fulfill, the booking should keep its promise while accountability remains traceable. Recovery is part of the product, not an invisible back-office hack.
Demand owner
Original source stays canonical
Commercial owner
Original booking promise stays canonical
Dispatch owner
Platform-guided handoff, new operator for execution
Fulfillment owner
Winning recovery operator
Passenger promise
The passenger should feel continuity, while operators and finance teams still see the handoff and settlement responsibility clearly.
Overflow is an operating mode, not a hidden loss bucket. Escalate intentionally before the promise breaks.
Review commercial setupRun direct, partner, OTA, and platform-assigned rides in one queue while keeping L2 driver choice and exception handling local.
Primary surface
Auto-dispatch, manual override, farm-out handoff
Guardrail
No silent drop. Reassign, override, or farm-out before the passenger sees uncertainty.
Must-watch signals
Keep the audit trail of the handoff while preserving one confident rider journey.
Open dispatch surfaceCommercial splits, evidence, and payout readiness must remain visible even when the platform sources demand and another operator fulfills it.
Primary surface
Settlement, payout traceability, evidence chain
Guardrail
Every handoff must stay ledger-visible. Settlement truth cannot be reconstructed from chat or spreadsheets.
Must-watch signals
If fulfillment changes, settlement ownership and evidence must change in the same flow, not after the fact.
See settlement proofFleet quality is a live operating concern, not a launch checklist. Driver documents, safety, fatigue, and trust should stay continuously visible.
Primary surface
Driver onboarding, document expiry, trust alerts
Guardrail
Unsafe or expired supply should never be silently dispatchable just because demand is high.
Must-watch signals
When supply quality drops, block, reroute, or escalate instead of passing risk downstream to the rider.
Start operator trialSupply resilience simulation
Normal demand should still expose the next failure mode before it becomes rider-visible. A world-class surface makes the recovery path explicit even on quiet days.
Operators keep one commercial and dispatch picture across direct, partner, OTA, and platform-assigned demand.
The system should expose when the next 30 minutes of arrival demand will overflow the operator's owned fleet before service confidence collapses.
Owner
Dispatcher + owner
Trigger
Revenue breakdown by channel, driver, and route. Booking trends, cancellation rates, average fare, and utilization metrics. Export to CSV at any time.
Onboard drivers with document verification. Track license and SRC expiry with automatic alerts. View driver ratings, ride history, and earnings.
Automated weekly settlements across platform, OTA, partner, and operator shares. Driver payouts remain operator-internal, with audit-ready ledger transparency.
Drivers set their availability windows. Standing offers define corridor capacity by day and time. The system only dispatches to available drivers.
Built-in route optimization powered by OSRM. Drivers get turn-by-turn navigation inside the app — no need for external mapping apps.
SOS emergency button for drivers and riders. Ride verification codes. Fatigue monitoring via drive-time tracking. All rides GPS-logged.
For growing operators with multi-channel demand
Up to 100 vehicles · 50 team members
Unlimited scale with full platform access
Unlimited vehicles · unlimited team members
Free trial is available on all plans and trial length varies by package. No credit card required to start. Platform commission applies per booking on top of subscription.
DLM ↔ Fethiye, Oludeniz, Marmaris, Bodrum
“We switched from managing bookings in WhatsApp groups and spreadsheets to youtourer in a single day. Now our 15 drivers get ride offers automatically, settlements are calculated weekly, and I can see exactly which channels are driving revenue. The Growth plan paid for itself in the first week.”
Ahmet Y.
Fleet operator · Antalya · 15 vehicles · Growth plan
Make it obvious that the platform assigned the ride while the operator still owns L2 execution and driver choice.
Recovery rule
No silent drop: if the first operator cannot take it, reassignment or farm-out must preserve the passenger promise.
Show exact pickup time, meet-and-greet notes, return coordination, and the longer recovery window before acceptance.
Recovery rule
Exceptions must be surfaced earlier so operations can rebalance before pickup, not after the promise is already broken.
UI must make this explicit
Keep the handoff auditable for operators while the passenger still sees a confident, uninterrupted journey.
Recovery rule
Track who originated, who now fulfills, and how settlement responsibility changed without leaking chaos to the rider.
Arrival corridor demand exceeds committed vehicle supply for the next pickup window.
First move
Open explicit overflow routing: re-rank owned supply, then partner fallback, then commercial escalation.
Recovery proof
No hidden backlog, no silent drops, and one visible owner for the passenger promise.
Farm-out should stay auditable. Fulfillment can change fast, but commercial ownership, evidence, and settlement must change in the same motion.
Owner
Dispatch + finance
Trigger
Primary operator cannot safely fulfill the ride within the sold pickup promise.
First move
Switch fulfillment owner, preserve rider continuity, and persist settlement/evidence ownership immediately.
Recovery proof
Passenger sees continuity while finance still sees the exact handoff boundary.