Airport transfers for hotel guests: own vehicles, a partner or the guest's own arrangement

A hotel airport transfer is the pre-arranged ride between the airport and the hotel. A hotel can run it with its own vehicles, contract a licensed transfer company, or leave it to the guest. The choice turns on control, cost and who carries the risk when a flight is late and no driver is waiting.

A guest lands at 01:40, walks the arrivals hall twice and finds no one holding a sign with their name. The hotel did not drive the car. The hotel still gets the review. This article compares the three ways to run a hotel airport transfer, lists what the guest needs before landing, sets out a waiting rule for delayed flights, and walks through the documents to check in a transfer partner's file.

What are the three ways to run a hotel airport transfer?#

There are three: your own vehicles, a contracted transfer company, or the guest's own arrangement. They differ less in price per trip than in who carries the risk when something goes wrong at the curb.

Own vehicles give full control of the meeting: your driver, your sign, your script at the door. You also own the idle hours, the driver roster, the licensing and the insurance. A contracted partner buys you capacity by the trip, but you still own the guest's experience, so the contract must fix the waiting rule, the escalation phone number and who pays for a missed pickup. The guest's own arrangement, a taxi, a ride app or public transport, costs you nothing and controls nothing; the guest still judges the hotel by the instructions you sent before they landed.

Compare the three on the cost of a failure, not on the cost of a ride. An unclaimed guest at 02:00 with no one answering the partner's phone is the number that matters.

A shuttle that runs on a fixed timetable is a fourth shape of the same decision, and it changes the guest's expectation: a wait is normal on a shuttle and unacceptable on a private car. Whatever the model, name one person in the hotel who owns transfers and one number the guest can call, and put both in writing.

What does the guest need to know before landing?#

The guest needs four things in one message: where exactly to go, who to look for, what to do if that person is not there, and what it will cost. Anything missing becomes a phone call from the arrivals hall.

Name the terminal and describe the meeting point in words a first-time visitor can follow, not only "our driver will be waiting". Spell the name on the sign exactly as the booking reads, and say what the sign looks like, so the guest is not scanning forty identical boards. Give the driver's mobile number and the messaging app the hotel actually monitors, plus a second number for the front desk.

Add a fallback sentence: wait here, call this number, do not take another car. It is the line that prevents the most expensive kind of confusion. Match the vehicle to the party, including luggage count, oversized bags, a stroller and child seats requested in advance rather than discovered at the curb. Send the message 24 to 48 hours before arrival and again on the day; the second copy is the one people read. State the price and how it is paid in the same message, so the driver and the front desk are not negotiating different numbers. The full pre-arrival sequence, including where the transfer message fits among the others, is covered in hotel pre-arrival emails: what to send guests and when.

Who decides to wait when a flight is delayed?#

The hotel decides, in advance, and the decision must be written into the contract with the driver or the partner. A driver standing in a hall at 03:00 with no rule to follow will improvise, and improvisation is what guests remember.

Track the flight number, not the guest's estimate of their arrival time; the airline's own status is the only version both sides can agree on. Fix two numbers before the season starts: how long the car waits after landing at no extra charge, and who authorizes a longer wait. Separate the two decisions: whether to keep waiting, and whether to release the car and send the guest another way. The second is often cheaper and almost always kinder.

Tell the guest before landing, not after. A message saying the driver is waiting, or that a taxi is arranged and will be settled by the hotel, removes the worst part of a delay. Record the decision and its time, because the cost question arrives the next morning with the partner's invoice. On a shuttle, publish the departure times and the rule for a late flight; a fixed timetable that leaves without the guest is a complaint, not a policy.

Should the transfer be included, charged to the bill or paid to the driver?#

Choose one method per arrival type and say it in the confirmation. The method matters less than the consistency, because a guest who expected one thing and is asked for another at the curb will describe it as a hidden charge.

Included in the rate is the simplest promise for the guest and the hardest to price for you; if it is not written in the confirmation, it becomes an argument at the desk. Charged to the guest's bill means the guest signs, the amount goes onto the folio, and the partner is settled later against an agreed rate and a written cancellation rule. Paid to the driver means cash handling, receipts and the recurring risk that the guest believed the ride was included.

Whichever you choose, the guest must know before landing what they will pay, to whom, and what happens if they cancel or the flight moves. Do not publish a price you cannot hold for the season; if the price depends on the partner's rate, say that the front desk confirms it in writing. Take the tax and document questions to your accountant: which document is issued for a transfer charged to the bill depends on the hotel's own registration, and the rules were not verified for this article.

What should you check before signing with a transfer partner?#

Check the authorisation certificate first, then the vehicle, then the insurance, then the escalation contact. A partner who cannot produce the certificate quickly is telling you something.

The Road Transport Regulation (Official Gazette 8 January 2018, No. 30295; consolidated text to 16 May 2026, No. 33255) (opens in a new tab) requires anyone carrying out transport within its scope to obtain from the Ministry of Transport and Infrastructure the authorisation certificate (yetki belgesi) that fits the activity (Article 5). For commercial passenger transport, the certificate types include A1 (car, domestic, scheduled or non-scheduled), A2 (car, international, non-scheduled), B2 (bus, domestic and/or international, commercial non-scheduled), D2 (bus, domestic, commercial non-scheduled) and D4 (bus, within one province whatever the distance and between cities up to 100 km).

The regulation treats a car as a vehicle with at most 9 seats including the driver, and a bus as one built for more, so a minibus and a car are not the same thing on paper. Cars may sit on B2 and D2 certificates only under Article 24(2)(m): since 16 May 2026 the car must be owned by the certificate holder, no more than 8 years old, and the certificate must list at least 8 owned buses. Cars registered under the earlier rule may stay in use until they are removed from the certificate (Provisional Article 2(14)).

A1, A2, B2 and D2 holders must enter the vehicle plate, staff and passenger details into the Ministry's U-ETDS system at least one hour before an ad hoc, group or shuttle trip starts (Article 40(3)). An amendment of 1 October 2025 (No. 33034) added two hours for trips starting at an airport, but on 5 February 2026 the Council of State's 8th Chamber stayed that airport phrase (case 2025/5788) on an application by TÜRSAB, so unless the stay is lifted the one-hour deadline also applies to airport trips. Ask which party enters the U-ETDS record for each trip and keep the answer in the contract; a gap here is the partner's problem and your guest's delay. Confirm anything beyond the regulation's own text, including insurance levels and local practice, with the Ministry and your legal adviser rather than with the partner's salesperson.

What happens when the pickup goes wrong?#

The hotel runs a fixed routine, in order, and the first call goes to the guest rather than to the partner. The guest is standing in a hall; the partner is a phone call you can make while someone else is already solving the problem.

Confirm the driver's arrival before the flight lands, so a no-show is known before the guest is in the hall. Call the guest first with a named alternative: a taxi the hotel will settle, or a hotel car already on the way. Never leave the guest choosing between waiting and paying.

Log the time of each step: when the driver was due, when the guest was called, when the alternative arrived. The cost conversation with the partner needs those times. Settle the money question the same day, and tell the guest what they will and will not be charged before they reach the desk. Treat the conversation at the desk as a complaint with a known routine, not as an explanation of the partner's failure; see hotel guest complaints at the front desk: a recovery routine. Feed the case back into the contract: a missed pickup that repeats is a clause problem, not a driver problem. How the arrival itself is handled after the rescue is covered in welcoming hotel guests: the first ten minutes from the door to the room.

Where does the transfer belong in the confirmation and the pre-arrival messages?#

The confirmation says whether a transfer is included and how to request one; the pre-arrival message says where to go and who to call. Splitting the two keeps each message short enough to be read.

In the confirmation: whether a transfer is included, how to request one, the deadline for requests, and what happens if the flight number changes. In the pre-arrival message: the meeting point, the sign, the driver's number, the fallback instruction and the price. Keep one owner of the wording: two templates written by two departments produce two different promises, and the guest brings the wrong one to the desk.

The guest app is where this belongs next. Each hotel gets its own guest app, installed from the browser with no app store, and offers are made before arrival and during the stay. At AI Otel, third-party extras such as transfers, tours and local experiences are designed to sit next to the hotel's own offers in that app; this part is architected rather than built, so today the request is still handled by people and confirmed in writing.

What to do next#

Pick one transfer model for each arrival type, write the three sentences the guest receives before landing, and audit one partner's certificate this month. The transfer is the first service a guest experiences, so the model matters less than the fact that someone in the hotel owns it, answers the phone and can name the next step. If you want to see where transfers are planned to sit in the guest journey, you can request a briefing.