Marrakech

Peak season in Marrakech: booking transfers on time, the hotel's method

In peak season, a transfer is secured well in advance: capacity agreed with the transport company, an order deadline, a complete request and a fallback plan. Here is a hotel's working calendar, with template messages.

4x4 by a camp in the Agafay desert at sunset

This article is about the calendar: what to fix, and when. For the general method of handling requests, see instead [our guide to organizing a hotel's transfers](/en/hotels). For a peak tied to a specific conference, a dedicated article exists on events in Marrakech.

Why peak season changes the way you book

Off-season, a transport company can absorb a last-minute request. In peak season, the same vehicles and the same drivers are called on by every property at the same time slots. Three things change:

  • **The margin disappears.** A request changed the day before has no obvious spare vehicle.
  • **Time slots concentrate.** Flights often land at the same hours: two of your guests may need a driver at the same time.
  • **Mistakes cost more.** A driver sent to the wrong place cannot be replaced within a few minutes.

No numerical rule says "book this far ahead." The right lead time is your own: it depends on your volume, your transport companies and your guests. The method below helps you find it and write it down.

The steps, from pre-season to arrival day

  1. **Identify your own busy weeks.** Go back over last year's bookings and mark the periods when your transfers were tight or declined. Don't rely on an impression: note the dates.
  2. **Open the discussion with each transport company before those weeks.** Ask how many vehicles of each category it can reserve for you on those dates, and until when it guarantees that capacity.
  3. **Set an order deadline.** Agree on a cut-off date beyond which it no longer commits without checking. Write it down, and apply it to your own team.
  4. **Pass the request on as soon as the stay is confirmed.** Don't wait until the day before: the request goes out when the stay is confirmed, even if the flight time is missing (mark it "to be completed").
  5. **Complete, then reconfirm.** When the guest provides their flight, update the request and have the transport company confirm in writing.
  6. **Reconfirm before arrival.** A final exchange checks the time, the number of travelers, the luggage and the meeting point.
  7. **Keep a fallback plan.** Identify a second transport company in advance, with its terms, before you need it.

What gets fixed, and when

A hotel's peak-season working calendar (deadlines to be agreed with your transport companies)
MomentWhat the hotel doesWhat the transport company confirms
Before the seasonLists its busy weeks, shares its likely volumes, asks for peak-season termsCapacity per vehicle category, guarantee deadline, change rules
When the stay is confirmedSends a request with the known information and flags what is missingAcknowledgment and acceptance, or a quick refusal so the hotel can turn elsewhere
When the flight is knownCompletes the request: flight, time, travelers, luggage, meeting pointSuitable vehicle, then the driver assigned as soon as one is chosen
Before arrivalReconfirms and informs the guest of the meeting point and the driverDriver, vehicle, license plate and departure time to reach the meeting point
Day of arrivalMonitors sensitive arrivals, keeps a reachable contactReports any delay or problem as soon as it is known

Securing the request: what it must contain

A vague request is declined more often in peak season, because the transport company cannot size the vehicle. It must contain: the flight, the time, the number of travelers, the luggage and the meeting point. If a piece of information is missing, say so explicitly rather than guessing. The detailed list of questions to ask the guest is in [our checklist of information before a transfer](/en/blog).

For the last leg of the trip to a riad, assume nothing: only the riad confirms the drop-off location. Don't infer it from the type of vehicle or from the street. Have the riad validate this point before passing it on to the driver.

Template messages

To send to the transport company before the season

"Hello, we are preparing our peak season. For the following dates: [list], could you tell us how many vehicles you are reserving for us per category, until what date this capacity is guaranteed, and how you handle a change after that date? Please reply in writing."

To send when the stay is confirmed

"New request: arrival on [date], flight [number or "to be completed"], [number] travelers, [number] bags, meeting point [validated description]. Please confirm availability of [category] or tell us immediately if it is not possible."

Reconfirmation before arrival

"For the arrival on [date, time]: can you confirm the vehicle, the driver, the departure time for the meeting point and the number to call? Reply expected before [agreed time]."

Common mistakes in peak season

  • **Waiting for the flight to order.** The flight comes late; the request must go out earlier, marked "to be completed."
  • **Relying on a single transport company with no fallback.** A last-minute refusal leaves you with no option.
  • **Accepting a verbal "we'll see."** Without a written reply, you don't know whether the vehicle exists.
  • **Changing without a trace.** A time changed through an isolated message is a lost ride. See our article on [keeping track of a ride's changes](/en/blog/keep-track-of-ride-changes-who-changed-what).
  • **Letting a single colleague hold the information.** A day off or a shift handover is enough to lose it.
  • **Promising the guest a drop-off point not confirmed by the riad.**

Hotel checklist before peak season

  • Busy weeks identified from your past bookings.
  • Capacity in writing with each transport company, with its guarantee deadline.
  • Internal order deadline known to the front desk and the concierge.
  • Second transport company identified, terms requested.
  • Request template and reconfirmation template shared with the whole team.
  • Meeting points validated for each type of arrival, and riad drop-off confirmed by the riad.
  • Reachable contact defined for peak days, with a backup.
  • Written change rule: who can change, through which channel, with which confirmation.

On the transport company side, the organization is symmetrical: see the page [dedicated to transport companies](/en/transport-companies) and the description of [how it works overall](/en/how-it-works) to see how a request travels between the parties.

With WAYLISS

  • The property enters a structured request: flight, time, travelers, luggage and meeting point.
  • Several team members (front desk, concierge) can follow the same requests.
  • Each ride keeps a viewable history: request, assignment and steps.
  • The transport company assigns the driver and vehicle; the property sees the driver’s first name, the vehicle and the plate.

Learn more: Guest transfer management for hotels, riads and concierge services

Frequently asked questions

How far in advance should you book in peak season?

There is no universal lead time that we can state. Ask each transport company until what date it guarantees your capacity, write it down, and send your requests as soon as the stay is confirmed rather than the day before.

Can you send a request without a flight number?

Yes, provided you mark it "to be completed" and update it as soon as the guest provides their flight. This lets the transport company reserve capacity early.

Do you need a second transport company?

It is prudent. Identify it before the season, ask for its terms and test it on a simple arrival, so you don't discover it on the day of a refusal.

What should you do if the transport company declines a request?

Ask for a quick, written refusal, then switch to your fallback transport company with the same complete request. Inform the guest only once the assignment is confirmed.

Who confirms that the vehicle can reach the riad?

The riad itself. Don't infer it from the vehicle or the neighborhood: have the riad validate the drop-off location before you communicate it.